Sessions and signing out

Session controls belong to the account service used by your Atlas.

Follow the sign-out controls in your deployment. Closing a browser tab does not, by itself, confirm that its server session has ended. Ask your deployment owner how to revoke access if a device is lost.

Planned session policy

The documented target is a maximum 12-hour session with a 30-minute inactivity limit. It also requires server-side sign-out, administrator session revocation and termination of sessions when an account is disabled.

A proposed 15-minute window for reusing a recent authenticator check across authorised workspaces is part of that design. Separate Atlas sessions and permission checks must still be enforced.

The shared account service is not yet live. These limits and cross-Atlas behavior need deployment-level verification before they can be relied on.