Platform workflows
Sign in, sessions and sign out
Use the configured identity flow, return safely to Atlas and understand session limits.
Sign in and registration
- From the public landing page choose Open Atlas, then Continue to sign in on Enter your organisation.
- Complete the identity provider’s sign-in flow. Registration options are controlled by that provider; Atlas has no separate public registration form. Do not assume that a registration button is available in every environment.
- After the callback returns, Atlas resolves current organisation memberships and deployment permissions. Signing in alone does not grant access to another organisation’s designs.
- If you arrived from an invitation, continue to its explicit acceptance screen. Review the recipient and organisation before accepting.
Session behaviour
The product restores and refreshes its browser-tab session when possible. Session credentials are kept in browser session storage and are not passed to Unity. A refresh can fail or access can change while you work; a session-expired error means you must sign in again. Unsaved editor changes could not be saved when that error is shown.
The public documentation site has no product session, authentication, analytics or non-essential cookies. Opening this guide does not sign you in or save a design.
Sign out
- Apply any inspector draft and Save if you want to keep your design. Choose Sign out in the Atlas header.
- If asked to discard unsaved changes, cancel to return and save, or confirm only if you accept losing them.
- Atlas clears the local session and redirects through provider logout when it has the required session information. An older session may show a local-session-only warning: sign in with the current application, then sign out again to complete provider logout. The warning does not mean the provider session was ended.