Collaboration in Atlas happens at two levels: individual projects and entire workspaces. Project invitations give team members access to specific maps and data. Workspace invitations provide access to all projects within that workspace.
Project-Level Invitations
Project invitations let you share specific maps with team members while keeping other projects private. This approach works well when different teams work on separate initiatives within the same workspace.
Opening the Share Dialog
Click the Share button in the top-right corner of any project to open the sharing interface. The dialog displays two tabs: Share and Publish. The Share tab manages collaborator access and invitations.
Inviting Team Members
Click the Invite collaborators button at the bottom of the Share dialog. A new screen appears with the title "Invite team members" and a subtitle explaining the invitation purpose.
Enter email addresses in the input field labeled "Emails, comma separated". You can invite multiple people at once by separating addresses with commas. Press Send invitation to deliver the invites.
Recipients receive an email invitation with a link to join your project. They need an Atlas account to accept the invitation. New users can create an account during the acceptance process.
Understanding Access Levels
Atlas provides two access levels for project collaborators: Full seat and Viewer. The access level determines what actions a team member can perform.
Full seat access grants complete editing permissions. These collaborators can add data, modify layers, create bookmarks, and adjust project settings. They participate fully in project development and maintenance.
Viewer access provides read-only permissions. These collaborators can view the project, explore data, and add comments. They cannot modify project content or settings. Use viewer access for stakeholders who need visibility without editing rights.
Project Roles
The Share dialog displays all collaborators in a list format. Each entry shows the person's name, email address, role, and access level. The project creator appears with an Owner designation and Full seat access.
Owners have complete control over project settings and collaborator management. They can invite new members, adjust access levels, and remove collaborators. Each project has exactly one owner.
Regular collaborators appear without the owner designation. Their permissions depend on their assigned access level. You can adjust access levels by clicking on the dropdown next to each collaborator's name.
Access Level Indicators
The Share dialog includes an access level dropdown at the top showing the current project privacy setting. When set to Private, the interface displays the text "Only the map creator and invited collaborators can edit". This confirms that project access is restricted to the invited team.
Workspace-Level Invitations
Workspace invitations differ from project invitations by granting access to all projects within the workspace. This approach suits organizations where team members need visibility across multiple initiatives.
Workspace administrators manage these invitations through workspace settings. Adding someone to the workspace automatically gives them access to every project created in that space.
Consider workspace structure carefully before sending invitations. Once someone joins a workspace, they see all projects unless you implement additional project-level restrictions.
Managing Existing Collaborators
The collaborators list in the Share dialog provides ongoing management capabilities. Review this list regularly to ensure appropriate access levels for each team member.
Remove collaborators who no longer need project access by clicking the removal option next to their name. This immediately revokes their access while preserving project history and audit trails.
Adjust access levels as roles evolve. A viewer might need full seat access as responsibilities expand. Similarly, you might reduce someone to viewer access when their active involvement concludes.
Copy Link Feature
The Share dialog includes a Copy link button that captures the current project URL. This link provides direct access to the project for anyone with appropriate permissions.
Sharing this link with workspace members gives them instant access if they already have permission. External recipients see an access request or login prompt depending on project settings.
Best Practices
Invite collaborators at the project level when working with external consultants or temporary team members. This approach maintains security by limiting access to specific initiatives rather than your entire workspace.
Use viewer access for executives, clients, and stakeholders who need project visibility without editing requirements. This prevents accidental modifications while maintaining transparency.
Document your collaboration structure somewhere accessible to the team. Clarify who owns which projects and what access levels different roles require. This reduces confusion and access request overhead.
Review collaborator lists quarterly or when team members change roles. Remove inactive collaborators promptly to maintain security and reduce workspace clutter.
Communicate access changes to affected team members before implementation. Sudden permission changes disrupt workflows and create frustration. Brief advance notice maintains team harmony and productivity.
Test invitations with a colleague before sending to large groups. Verify that invitation emails arrive correctly and that the acceptance process works smoothly. This prevents confusion and support requests.
