Sessions
Control how long access stays active.
The local console uses a server-side session with inactivity and maximum lifetimes. Sensitive workspace changes require a recent identity check.
Console time limits
- Inactivity30 minutes
- Maximum age8 hours
- Recent verification5 minutes
After a membership change
- Console sessionStill signed in
- Company membershipRemoved
- Next workspace requestAccess denied
Manage the console session
The browser holds an opaque session cookie. The console stores a hash of its token and rotates it after sign-in and fresh verification. In HTTPS mode the cookie uses the Secure and HttpOnly attributes.
- Inactivity limit
- 30 minutes
- Maximum session age
- 8 hours
- Recent verification window
- 5 minutes for privileged workspace actions
Treat app sessions and workspace access separately
Sign out of the console
Signing out ends the console session. Each customer application has its own session to manage.
Check access after revocation
A workspace request is checked against current membership and reseller grants even while the console session remains active.
Verify downstream behaviour in staging
The local browser test verified five-minute access tokens and rejection of replayed refresh tokens. A pilot must test how logout and membership changes reach connected apps.