Getting started

Get into the right workspace

Choose a task first. Use an account with access to that feature in the active organisation; each linked procedure lists its prerequisites.

1. Sign in with your work account
2. Check your organisation and language
3. Find your starting page

Check the result: You can identify the active account and organisation and reach the pages your role permits.

If you get stuck: If sign-in is refused, ask an administrator to check your membership or invitation. If a page is missing, check the active organisation and your role before requesting access.

Sign in and recover access

Screen: /login

Use case: Enter Atlas with the work email account authorised for your organisation.

Before you begin: Use a work email that is already a member of an Atlas organisation, has an outstanding invitation, or belongs to a domain the organisation allows.

How to do it

1. Open the sign-in page. Choose EN or 中文 near the top to set the page language before you continue.
2. Enter your work email under Work email and choose Send code, or choose Continue with Google to sign in with an authorised Google account instead.
3. An email that is not a member, has no invitation and is not on an allowed domain is refused at this step; ask your administrator to invite you rather than trying a different address.
4. Enter the one-time code sent to your email and continue. Atlas then opens at the landing page for your role — see Where Atlas opens for your role.

Expected result: You reach the workspace and can check the active organisation in the rail. If sign-in is refused, read the displayed reason and ask your administrator to check the membership or invitation for that work email.

The browsers used for the 2026-09-06 production study already had sessions and redirected /login to Assistant, so the two dated images below are historical captures, not new production evidence; their captions stay dated accordingly. The screenshot after them is a fresh, signed-out capture from staging on 2026-09-22. No code was sent and no session was ended in either study.

Where Atlas opens for your role

Screen: /

Use case: Know where Atlas lands you after sign-in and what the first rail group offers for your role.

Before you begin: Sign in to the organisation that holds the records; the landing page and rail depend on your role in that organisation.

How to do it

1. Sign in. A rep or a manager lands on the Today workbench at /today; an admin or an owner lands on Business overview at /dashboard.
2. Look at the first entry in the left rail. A rep sees Work, with Workbench and My Tasks below it. A manager sees Work, with My work and My Tasks under a Workbench header and Team review under an Insight header. An admin sees the same Workbench and Insight headers, with Business overview and Team review under Insight. An owner sees the admin's groups plus Business direction and Quote decisions under Insight.
3. Below that first group, every role shares the same four entries: Customers, Knowledge, AI Assistant and More tools.
4. Opening /insights directly redirects to Today for every role; reach Business overview from the Insight group of the Work rail, or at /dashboard, instead.
5. As an owner, open Settings → Personal and use Default landing: “Open Atlas on” offers Default — Insights, Today and Business direction. The choice applies to this browser.

Expected result: You land on the workbench for your role, and Customers, Knowledge and AI Assistant are reachable from the rail whatever your role.

Your account, organisation and navigation

Screen: /today

Use case: Find your account, switch organisation and reach the parts of Atlas your role can see.

Before you begin: Be signed in to the organisation you want to work in.

How to do it

1. Open the organisation button at the top of the rail (for example, Open organisation menu for UAT) to see every organisation your account belongs to and switch between them.
2. Choose a rail group — Work, Team or Insights depending on your role, or Customers, Knowledge, AI Assistant or More tools — then choose a page from the second column that appears.
3. Every page title carries a "?" help control. Choose it to open a short explanation of that page with a link into this manual. The manual itself is also reachable directly, at /guide in English and /zh/guide in Chinese.
4. Open the account button at the bottom of the rail (Open account menu) to see your name, the version pill (for example v0.38.0), your signed-in email address, the Language pair EN / 中文, Settings, Help & Support and Sign out.
5. When a new Atlas version ships, a dismissible update notice appears once per account until you dismiss it. Open the account menu and choose Open release history at any time to see the full history.

Expected result: You can tell which organisation, account and page you are in, and reach every part of Atlas your role permits.

Only an owner's rail carries Business direction and Quote decisions; a manager's Team group carries Team review instead of these. The version pill names the exact deployed build, for example "v0.38.0 (c848b7e)".

Report a problem or suggest a feature

Screen: /assistant

Use case: Give the team enough context to reproduce a problem.

Before you begin: Use an account with access to this feature in the correct organisation.

How to do it

1. Open More tools in the rail and choose Send feedback. Select General, Bug report, Session-specific or Feature request.
2. Describe what you tried, what happened and what you expected (up to 4,000 characters). For a conversation issue, check whether the current conversation will be attached.
3. Optionally choose an available handler/shared inbox and attach relevant files. The form supports up to five attachments of 20 MiB each; remove sensitive information before attaching.
4. Review the content and choose Send only when ready to submit. Check the confirmation or keep the form open to correct an error.

Expected result: A feedback record is submitted with the intended context.

Procedure checked against the deployed source; no feedback was sent during this review. Handler options depend on configuration.