This section explains who can do what in Atlas. It covers three things:
- Workspace management — what it means to be a member of a workspace, including roles, seats, and billing. See Workspace Management.
- Project access — who can view or edit a project, and how to share one. See Project Access.
- Teams — how to group people so they all get access to the same projects at once. See Teams.
If you're troubleshooting a specific "why can't I do this?" question, jump to Access Control Troubleshooting.
The three layers
Think of Atlas in three layers:
- A workspace is your organization's home in Atlas. It contains all your projects, members, and billing.
- A project is where the actual mapping and analysis happens. Each project lives inside one workspace.
- A team is a named group of people in a workspace. You can share resources with a team instead of adding people one at a time.
Every person in Atlas fits somewhere in this picture: they're a member of a workspace, they have access to some projects inside it, and they may belong to one or more teams.
Glossary
- Workspace — your organization's home in Atlas. Holds all projects, members, and billing.
- Project — the map and dataset workspace where actual work happens. Always belongs to one workspace.
- Role — Owner, Admin, Regular, or Guest. Governs what you can do to the workspace.
- Seat — Editor, Viewer, or Field Worker. Caps what you can do to any project.
- Team — a named subset of workspace members, used to share projects with many people at once.
- Share — to grant another person, the workspace, or a team some level of access to a project.
- Public project — a project that anyone with the link can view, optionally gated by a password.
For finer-grained controls inside a project — for example, making a single dashboard public while keeping the rest private — see Interface permissions.