Organizations

An organization owns your projects. A synced one also owns everything your team shares: members, cloud projects and their timeline, chat, calls, prompt drafts and Spaces. The organization switcher at the top of the rail creates, switches, renames and deletes them.

Local or synced

Atlas starts you in a local organization called Personal. It lives on this machine only, needs no account, and never makes a network call.

A synced organization lives in your Atlas account. It appears on every device you sign in on, and it is what the team features need.

In a local organization, Chat and Members in the rail are disabled, and Atlas Agent's composer says the organization is local and offers to sync it.

Create an organization

Open the switcher and select Create organization….

1. Enter a Name. Atlas suggests a Handle from it, using lowercase letters, numbers and hyphens.
2. Choose a Type. Cloud is "Synced across your devices and shareable with your team" and needs you to be signed in. Local is "Private and offline".
3. For a cloud organization, choose a Region. Atlas hosts organizations in the United States. European Union appears in the list but is not available yet.
4. Select Create organization.

A cloud handle must be unique across Atlas, and Atlas checks it as you type. A local handle only needs to be unique on your machine.

Whoever creates a synced organization is its Owner and an Admin. See Members & roles.

Turn on sync for a local organization

Switch to the local organization, open the switcher, and select Turn on sync for <name>… at the bottom. Atlas creates the organization in your account with the same name and handle. Signed out, the same item starts sign-in first.

Once synced, the row reads <name> is synced. There is no switch to turn sync off again.

Turning on sync doesn't upload anything by itself. Each project still stores its sessions locally until you put it in the cloud.

Put a project's sessions in the cloud

Sessions reach the organization one project at a time. Open the project and press ⌘⌥C, or select the project name in the title bar, to open session capture. Under Where sessions are stored, Local is "This machine only" and Cloud is "Shared with your Organization".

Choosing Cloud offers two ways in:

• Create registers a new cloud project in the organization. Pick a Slug, confirm the Repository Atlas detected, and optionally Restrict to named members. Otherwise every member of the organization can read it.
• Connect joins a cloud project a teammate already created. Atlas preselects the one that matches your checkout's repository, so several people's sessions merge into one timeline.

A project that has been recording locally shows Sync instead. It walks you through the same Create or Connect choice and publishes the history you already have. A cloud project shows Change, which moves its sync to a different cloud project and re-sends what was captured.

Before anything leaves your machine, Atlas shows what it is about to send: the number of sessions, their date range, and how many secrets were redacted. Nothing is sent until you confirm.

Cloud needs three things: you are signed in, the active organization is synced, and git is installed. When one is missing, the Cloud option is disabled and says which. A cloud project always syncs to the active organization.

Session capture covers capture itself, and the timeline lists what a cloud project sends.

Find your way around the rail

The top of the rail holds the organization-wide destinations:

• Timeline: every recorded session in the organization. See Timeline.
• Chat: team chat, also ⌘⇧C. Disabled until the organization is synced.
• Members: the members manager. Disabled until the organization is synced.

Below them, under Modules: Agents, Knowledge, Terminal, Source control, Memory, Usage and More, which opens any other module.

Switch organizations

Select an organization in the switcher to move into it. Search the list by name or handle, and use the refresh button to pull in organizations you were added to elsewhere. Atlas remembers the project you last opened in each organization.

A synced organization is locked, with a padlock, when you are signed out or when your account isn't a member of it. Local organizations never lock.

Copy the organization ID

Select Copy organization ID in the switcher to copy the active organization's server ID. Support may ask for it. A local organization has no ID until you turn on sync.

Rename an organization

Hover a local organization and select the pencil. Renaming changes the name, not the handle.

A synced organization's name belongs to the server. An admin renames it in the web app under Settings, Organization, Organization name, and the desktop picks up the new name when your account refreshes.

Delete an organization

Hover an organization in the switcher and select the bin. Atlas removes its projects and their chats from Atlas, and never touches the project files on disk. You can't delete your last organization.

For a synced organization, deleting it on the server takes the Admin role. Without it, Atlas removes only this machine's copy, and the organization can reappear on the next refresh while you are still a member.

An admin can also delete a synced organization from the web app, under Danger zone in the organization settings. That removes its members, chat, calls and projects for everybody.

Next

• Members & roles: invite teammates
• Timeline: read your team's sessions
• Your account: sign in