What is available
Use the controls and status shown in your workspace to check availability. Automated onboarding, knowledge refresh, recurring routines and connected integrations can require separate enablement. A suggested plan or a connection card does not prove that a workflow is ready to run.
If a capability is unavailable, continue in Classic where you have access, or contact support about availability. These guides do not announce a rollout date or a change to your plan.
Choose a guide
Getting started with Atlas
Access, your first request and returning to Classic.
Review and Apply in Atlas
Exact effects, approval buttons, declining proposals and expiry.
Atlas knowledge and answer quality
Sources, refresh and meaningful test evidence.
Atlas roles, privacy and key delivery
Permissions and handling a private key delivery.
Troubleshooting Atlas
Interruptions, unknown outcomes and limits.
Before an action
Each consequential action needs its own review card and an explicit click on its approval button. The button may say Approve, Approve & send, Approve & publish, Approve & delete or Apply. An ordinary chat yes is not approval. Informational plans have no blanket Apply: review each proposed effect when its own card appears.
A submitted request is not a confirmed result. Check the task and evidence before assuming a change or purchase completed. Follow the unknown outcome guidance if confirmation is missing.