Sessions & roles
The session lifecycle, how a candidate joins, and what each organization role is allowed to do.
4 min read
Lifecycle
A session moves through scheduled → live → ended and never backwards. It can be created in the portal or through the API; either way it is joinable as soon as it is scheduled, and it captures nothing until it is live.
| State | What is true |
|---|---|
scheduled | The session exists and can be joined. Nothing is being captured. |
live | The agent registered, consent was recorded, and monitoring is running — with the indicator visible to the candidate. |
ended | Capture has stopped. Evidence may still be finishing its upload; the session page shows each piece as it lands. |
Joining
A join link is minted per participant and per role, so it can be revoked without disturbing the others. There are 3 join roles: candidate, companion, viewer — the candidate on the desktop app, an optional paired phone providing the side view, and a viewer watching live in the portal.
Organization roles
| Role | Can |
|---|---|
owner | Everything, including the organization's plan, retention and deleting the organization. |
admin | Members, API keys, integrations and policy — everything except ownership transfer. |
interviewer | Schedule and run sessions, and review the sessions they can see. |
reviewer | Read sessions, evidence and reports, and leave notes. No configuration. |
The full list of roles as the system stores them is owner, admin, interviewer, reviewer.