Access State
Access state controls whether an operator can use the QTM OS system. It is set by the admin layer and is separate from authentication.
Being logged in does not automatically mean full access. Authentication verifies identity. Access state controls what that identity is permitted to do.
Access state values
| State | Meaning |
|---|---|
active | Full access to workspace and desk |
limited | Restricted access — some features unavailable |
suspended | Blocked from protected routes |
pending_activation | Approved but not yet activated |
pending_review | Application exists, no entitlement yet |
Who sets access state
Access state is set by the admin layer. Operators cannot set their own access state. The access state change is performed through the Admin Governance Desk.
Effect on the operator desk
A suspended or limited operator’s desk is blocked or restricted. Even if the operator is authenticated, they cannot access the work execution flow if their access state prevents it.
| Access state | Desk visibility |
|---|---|
active | Full desk and job queue visible |
limited | Desk may be restricted depending on configuration |
suspended | Protected routes blocked |
pending_activation | Workspace may not be accessible yet |
pending_review | No workspace access |
Why a job might not appear in the Desk
If an operator can authenticate but sees no jobs:
- Access state may be
limitedorsuspended - The job has not yet been created from an approved task (Create Job action not yet taken)
- The job was assigned to a different operator
Relationship to billing
Access state changes can be triggered by billing events. An operator on a billing grace period may move from active to limited. Suspension can result from failed payment recovery.
Guardrails
- Preserve the distinction between planned, partial, and live.
- Authentication ≠ access state. Do not conflate them.
- Access state is set by admin, not by the operator.