Check your access
Sign in to your own Chat.co account. Atlas is available to enrolled accounts with the required permissions. When your account has access, open the Atlas workspace. If that page is unavailable, use your usual Chat.co pages and ask the account owner or support to check access.
The account owner can work across their account once Atlas access is available. Admin access depends on the Use Atlas permission, and account-level actions need the relevant admin permissions. Team members need Atlas assistant access for assigned bots and remain limited to their bot permissions. See roles and permissions before delegating work.
Make a clear request
- Name the bot and your goal. For example, ask to inspect its knowledge sources before proposing changes.
- Read the reply and source evidence. If the target is unclear, clarify it before continuing.
- Open the relevant task to follow its status. Waiting for you means a decision is needed; it does not mean the task is complete.
- For a proposed change, read its own review card. Check the target, draft, scope and cost information before clicking its approval button: Apply on hosted workflow reviews, or Approve and its send, publish or delete variants on standard reviews.
An ordinary chat yes is not approval. Learn how review and Apply work before authorizing an effect. Do not paste credentials into a request or upload them as knowledge.
Return to Classic
Select Classic in the Atlas header. The app saves your shell preference before navigating to your classic landing page. Owners normally land on the chatbot dashboard; team members may land on an assigned bot.
If the switch reports that it could not save, try Classic again. If it keeps failing, open your usual classic page directly or contact support. Navigating directly does not confirm that your preference was saved.
Switching views is not a task cancellation or a reversal of an applied change. Check any active task and outstanding review when you return. If its result is unclear, use the interruption guidance.