AtlasWork, planned itself.

    The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

    System status
    • SSO
    • SCIM
    • Two-factor sign-in
    • Audit log

    Product

    • Overview
    • PDF tools
    • Diagram tools
    • People & HR
    • Integrations
    • Marketplace
    • Pricing

    Resources

    • Guides
    • Glossary
    • Compare
    • Docs
    • API reference
    • Support
    • Changelog
    • Status

    Company

    • About
    • Careers
    • Press
    • Contact

    Legal & trust

    • Trust center
    • Security
    • Privacy
    • Terms
    • DPA
    • GDPR
    • SLA
    • Refunds
    • Google API data
    Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
    PrivacyTermsSecurityStatus

    You are in control of your cookies

    Atlas uses strictly necessary cookies to keep you signed in. With your consent, we add anonymized product analytics, conversion attribution, and remembered preferences. Change your mind any time at /privacy/cookies.

    Off until you agree · Change it any time

    • NecessaryAlways on
    • AnalyticsOpt-in
    • MarketingOpt-in
    • PreferencesOpt-in
    Still loading. Try again in a moment.Still loading. Try again in a moment.Still loading. Try again in a moment.
    Skip to documentation
    Docs
    Back to Atlas

    Start here

    • Overview

    Developer

    • REST API guide
    • Authentication
    • API reference
    • MCP (AI agents)
    • MCP tools reference
    • SDKs
    • Quick actions
    • Changelog

    Webhooks

    • Overview
    • Quickstart
    • Events
    • Payloads and headers
    • Security and signing
    • Delivery and retries
    • Managing via API

    Connect

    • Connectors
    • Integrations

    Product

    • Collaboration and chat
    • Signing in and security
    • Client portal
    • Client portal domains

    Reference

    • Glossary
    • Keyboard shortcuts
    • Module reference

    Guide

    Signing in and account security

    Every way into Atlas, how to manage your passkeys, and how an administrator sets up single sign-on for a company domain.

    Ways to sign in

    The sign-in page shows only the ways your Atlas address offers, and marks the one this device used last, such as "You last signed in with Google". That note stays on this device and holds only the name of the method, never your address or a code.

    • Password: your email address and password. Forgot password? on the password row emails you a reset link.
    • Email code: choose Email me a code under the form and enter the 6-digit code from your inbox. You can ask for another code after 30 seconds.
    • Email sign-in link: choose Email me a sign-in link and open the link from your inbox.
    • Passkey: choose Sign in with a passkey, or pick a saved passkey from the suggestions in the email field where your browser offers them.
    • Google, GitHub, GitLab, Microsoft, LinkedIn, Slack, Discord and Facebook: continue with the account you already use there. Google, GitHub and GitLab appear whenever Atlas has them set up. The others appear when the Atlas administrator has turned them on.
    • Single sign-on: choose Use single sign-on and enter your work email.

    Atlas uses only an email address the provider has verified. If the provider has not verified yours, sign-in stops and asks you to verify it there first, so nobody can claim your address through another account.


    Email sign-in link

    A sign-in link works once, for 15 minutes. Open it in the browser where you asked for it and you are signed in straight away. Opened in any other browser, the page first asks you to confirm the address it was sent to, shown in part, and signs nothing in until you choose Continue. A forwarded link cannot sign somebody in without that decision.

    After you ask for a link, the page shows Check your email with the address it went to. You can send the link again after 30 seconds, or choose Use a different email. A used or expired link says so: choose Request a new link. The answer is the same whether or not the address has an account, so the page never reveals who uses Atlas.


    Verifying your email address

    After you sign up with a password, Atlas emails a 6-digit code and a link to your address. Enter the code on the page that follows, or open the link, within 5 minutes. Choose Skip for now to carry on and verify later.

    To verify later, open Settings, then Security. While the address is not verified, a card there says so: choose Send code, then enter the code. Asking again sends a new code and cancels the old one, up to 3 times in 10 minutes.

    Verifying your email address

    An address that is never verified stays unconfirmed, because anyone can type any address into a signup. The first time somebody proves they read that address, by an emailed code, an emailed link, a password reset or a verified Google or Microsoft account, Atlas removes the password, two-step verification, recovery codes, passkeys and signed-in sessions that the unverified account held, and that person signs in fresh. Verify your address right after signing up and none of this applies to you.

    Accounts created from an invitation, an email code or a social account are verified when they are created, because each of those already proves the address.


    The language of your emails

    Your sign-in codes, sign-in links, password resets and invitations arrive in the language saved on your account. If you have not saved one, they arrive in the language of the browser you asked from, and an invitation to an address without an account arrives in the language of the browser it was sent from. When Atlas does not offer that language, the email is in English.

    Emails in Arabic and Hebrew are laid out right to left.


    Passkeys

    A passkey signs you in with your device's screen lock or a security key instead of a password. It counts as two-step verification on its own, so Atlas does not ask for an authenticator code after a passkey.

    1. 1

      Open Passkeys in security settings

      Go to Settings, then Security, and find the Passkeys card.

    2. 2

      Confirm it is you

      Adding a way into your account asks for your current password, or a 6-digit code emailed to your own address.

    3. 3

      Create the passkey

      Give it a name you will recognise, such as the device it is on, and follow your browser's prompt.

    • You can hold up to 20 passkeys. Rename or remove any of them from the same card.
    • Passkeys work on the main Atlas sign-in page. On a firm's own client portal address, sign in another way.
    • A browser that cannot use passkeys says so when you choose the button. Closing the prompt is not an error: try again, or sign in another way.

    Single sign-on

    Single sign-on sends you to your company's identity provider, which confirms who you are. Choose Use single sign-on and enter your work email. Atlas finds the workspace that has verified your email domain and turned single sign-on on, and you come back to Atlas signed in.

    When single sign-on is not set up for an address

    No workspace has verified your email domain, or its single sign-on is turned off. Choose Back to sign in and use another way, or ask your administrator.

    Two-step verification

    With two-step verification on, every way into Atlas also asks for the 6-digit code from your authenticator app: a password, an emailed code or link, and Google, Microsoft or any other account. Without the app, choose Use a backup code instead. Turn two-step verification on and create backup codes in security settings. A passkey already proves both factors, so it skips this step.


    Verified domains for administrators

    Single sign-on can only find your workspace from a work email whose domain your workspace has proved it owns. Workspace owners and admins manage these in the Verified domains card under Settings, then Security, next to the single sign-on settings.

    1. 1

      Add the domain

      Enter the part of your people's email after the @ sign, such as example.com: the domain name only. A domain written in another script is shown as you wrote it and stored in its encoded form.

    2. 2

      Publish the TXT record

      At the company that manages your DNS, add a TXT record named _atlas-sso. followed by your domain, with the value the card shows. Copy both with the buttons beside them.

    3. 3

      Verify now

      Choose Verify now. A new record can take a while to appear. If the check fails, the card says what it found, and you can try again later.

    • A domain can be verified by one workspace at a time. Another workspace that has already verified it blocks the claim.
    • A subdomain is a separate domain and must be verified on its own.
    • Removing a domain stops single sign-on finding your workspace for that domain. People can still sign in another way.
    • Members who are not owners or admins see why they cannot change the list.
    • Single sign-on signs a person in only when their address is on a domain the workspace has verified. An address on any other domain is refused, even when the identity provider vouches for it.

    Related

    • Security settingsPasskeys, two-step verification, sessions and single sign-on.
    • Sign inThe page where every way in begins.
    About this page

    On this page

    • Ways to sign in
    • Email sign-in link
    • Verifying your email address
    • The language of your emails
    • Passkeys
    • Single sign-on
    • Two-step verification
    • Verified domains for administrators
    • Related