Signing in

Start with the Atlas address supplied by your organisation.

Use the customer entrance to open that address, then follow the sign-in instructions shown by your deployment. The entrance does not collect your password or authenticate you itself.

Current availability

The shared named-account and authenticator sign-in service is not yet live. An answering Atlas address does not establish that account access is ready. Your deployment owner can confirm which sign-in method is currently available.

The planned account model

The documented design uses an email address, password and authenticator code on each sign-in, without a remembered-device bypass. It calls for 14–128 character passwords, checks against known breached passwords, rate limiting and responses that do not reveal whether an account exists. These are implementation requirements, not a claim that every Atlas enforces them today.

Never send a password, authenticator code or recovery code to support.