Understanding Sessions
What a session is, how its status is determined, and what the possible outcomes are
A session is a single, unique instance of a journey completed by one user. Every time someone opens a journey link and goes through the verification steps, a new session is created.
Session lifecycle
A session goes through several states during its lifetime:
| State | Description |
|---|---|
| Created | The session has been generated but the user hasn't opened the link yet |
| Sent | The session link has been sent to the user (via email, SMS, or shared manually) |
| Started | The user has opened the link and begun the journey |
| Processing | The user has completed all steps and the AI is analysing the submitted documents |
| Completed | The AI has finished analysing and a verdict has been assigned |
| Expired | The session link expired before the user completed the journey |
| Abandoned | The user started but did not finish the journey |
Session verdict
Once all documents and checks in a session have been processed, the AI assigns an overall verdict. This verdict determines the colour indicator you see in the back office.
Possible verdicts
| Verdict | Colour | Meaning |
|---|---|---|
| AI Approved | π’ Green | All documents and checks passed β the session is fully verified |
| To Review | π‘ Yellow | One or more documents could not be fully verified and need manual review |
| AI Rejected | π΄ Red | One or more documents failed verification |
| User Approved | π’ Green | An analyst manually approved the session |
| User Rejected | π΄ Red | An analyst manually rejected the session |
How the verdict is calculated
The overall session verdict is determined by the worst-case outcome across all documents and checks in the session. The rule is simple:
- If any document is rejected β the session is rejected (red)
- If no document is rejected, but one or more need review β the session is to review (yellow)
- If every document is approved β the session is approved (green)
More precisely, the system evaluates every analysis node (identity document check, biometrics, document collection, etc.) and applies this priority:
user_rejected > ai_rejected > verify > user_approved > ai_approved
- If any node has
user_rejectedβ session = User Rejected - Else if any node has
ai_rejectedβ session = AI Rejected - Else if any node has
verifyβ session = To review - Else if all nodes are
user_approvedβ session = User Approved - Else if all nodes are
ai_approvedβ session = AI Approved - Otherwise β To review
In short: one red result makes the whole session red. Everything must be green for the session to be green. Anything in between is yellow.
End node override
The journey designer allows you to configure the End node with a forced result. When set, the end node overrides the calculated verdict:
| End node setting | Forced verdict |
|---|---|
| Automatic | No override β the verdict is calculated from the checks (default) |
| Compliant | Forces the session to AI Approved regardless of individual results |
| Non-compliant | Forces the session to AI Rejected regardless of individual results |
| To review | Forces the session to To review regardless of individual results |
Individual document statuses
Each document or check within a session has its own status, determined by the AI controls that ran on it:
| Status | Meaning | How it's determined |
|---|---|---|
| AI Approved | All AI controls passed | Every control returned true |
| To review | The AI could not make a definitive determination | One or more controls returned null (inconclusive), but none returned false |
| AI Rejected | One or more AI controls failed | At least one control returned false |
| Pending | The document is still being processed | Analysis has not completed yet |
| Collected | The document was collected but not analysed | Used for document collection steps that don't run AI checks |
| Error | An error occurred during processing | The analysis could not be completed |
After the AI assigns a status, an analyst can override it manually:
| Status | Meaning |
|---|---|
| User Approved | An analyst reviewed the document and approved it |
| User Rejected | An analyst reviewed the document and rejected it |
Multiple documents per node
When a journey step allows multiple submissions (e.g. the user retries after a poor photo), the system keeps all submissions and picks the one with the highest priority status for that node:
user_rejected > user_approved > ai_approved > ai_rejected > verify
This means a manual decision (user approved/rejected) always takes precedence over the AI verdict.
Viewing session results
Session results are visible in the back office under Analysis β By session. Click on any session to see:
- The overall verdict and colour indicator
- The status of each node (document check, biometrics, etc.)
- The extracted data and AI controls for each document
- The audit trail of all actions taken
See Journey Sessions for how to create, share, and review sessions from the back office.
Updated 1 day ago
