Every person you share with in Atlas gets one of three roles. The role decides what they can do inside a project, and which seat they use in your workspace.
- Editor — builds the project. Opens the project editor, edits data, maps and settings, builds and publishes interfaces, and invites others.
- Collaborator — works through the interfaces you share with them. Collaborators can't open the project editor, but they can edit through the interface itself — popups, tables, forms and data-entry widgets — depending on how you've configured it.
- Field worker — a collaborator with access to the field app: everything a collaborator can do, plus collecting data on site through Field Apps in the Atlas mobile app.
Compare roles
| Editor | Collaborator | Field worker | |
|---|---|---|---|
| Open the project editor | ✓ | — | — |
| Edit data, maps and settings | ✓ | — | — |
| Build and publish interfaces | ✓ | — | — |
| Invite others | ✓ | — | — |
| Open shared interfaces | ✓ | ✓ | ✓ |
| Edit data through popups, tables and widgets (as configured) | ✓ | ✓ | ✓ |
| Add data through forms and widgets | ✓ | ✓ | ✓ |
| Comment | ✓ | ✓ | ✓ |
| Work on tasks in the field app | ✓ | — | ✓ |
| Seat used | Editor | Collaborator | Field worker |
Whether collaborators can edit is up to you, per interface. Popups, tables and data-entry widgets each have a setting that opens them up to collaborators; until you turn one on, that part of the interface is read-only. See Sharing one interface for the settings.
Collaborator and field worker seats are available on the Team plan and above. On Free and Pro, everyone you invite gets an editor seat — see Billing and plans.
The seat is a ceiling, not a grant
Each workspace member has a seat of one of the three types. Giving someone a seat does not give them access to any project. Giving them access to a project does not let them do more than their seat allows. Both need to be in place, and the lower one wins: a member with a collaborator seat who is shared a project as an editor still only gets the interfaces.
Seats are separate from workspace roles (owner, admin, regular, guest), which govern the workspace itself — inviting members, billing, teams. See Workspace roles and seats.
The 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.
Where to go next
- Sharing a project — invite people or teams, and review or revoke who has access.
- Sharing one interface — publish a single interface, invite someone to just that interface, and choose what collaborators can change.
- Public links and passwords — share with people who don't have an Atlas account.
- Embedding a map — put an interface on another website.
- Teams — share with a group of people at once.
- Workspace roles and seats — owners, admins, guests, and who pays for what.
- Troubleshooting access — "why can't they see or edit this?"
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, Collaborator, or Field worker. Caps what you can do inside 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.
- Visitor — someone using a public interface without being invited. Visitors get collaborator-level access at most, subject to the same interface settings.