In Atlas, sharing is interface-centric. The Share dialog lets you decide, per interface, who can see it and whether it's public — so you can publish one interface to the world, share another with a single client, and keep the rest private. Project-level access (workspace members and the project owner) underlies all of it; per-interface settings layer on top.
For the full invite walk-through (interface scope picker, teams, seat behaviour), see Inviting collaborators.
Public access toggle per interface
In the share dialog, the Public access section shows every interface in the project with a switch:
- The master toggle at the top flips every interface to public or private at once.
- Each row toggles a single interface independently. The badge shows whether each interface is Public or Private.
- The header summary shows how many interfaces are currently public (e.g. "2 of 4 interfaces currently public").
Plan gating
Toggling individual interfaces requires the per-interface public access feature (currently included on Team plans and above). On plans without it:
- The master toggle still works (everything public or everything private).
- Per-row toggles show a lock icon and trigger an upgrade prompt when clicked.
A "Toggle interfaces individually" upsell card appears at the bottom of the section when this feature isn't on your plan.
Inviting viewers vs editors
The Share dialog's Invite people row lets you grant access to one or more interfaces by email or team name. Atlas distinguishes two access tiers:
- Viewer — read-only access to that interface; can't edit data or layout. Counts against the workspace's Viewer seat allowance.
- Editor — full editing access; counts against the workspace's Editor seat allowance.
The default tier you can invite depends on your plan:
- If your plan supports viewers (the viewers plan feature is enabled), you can add people as viewers to a specific interface, and they're added to the workspace as guests. Per-interface access stays read-only.
- If your plan does not support viewers, invitees are added as workspace editors instead — they get edit access to the workspace, and per-interface access is still read-only.
In other words: on plans without viewer seats, "invite to interface" upgrades the user to a full workspace editor. Plan accordingly when sharing externally.
What guests see
A user invited to a single interface as a Viewer:
- Lands on the shared interface URL.
- Cannot navigate to other interfaces in the project unless they're also public.
- Cannot edit, comment on data, or download datasets unless allowed by interface settings.
Practical examples
- Public report + private dashboard: keep the internal dashboard interface private; flip the public-facing report to Public.
- Client review: invite a client by email as a Viewer on the "Client review" interface only. They never see the team's working interfaces.
- Embed: combine public access with Embed Maps to drop a single interface into another website.
Limits and notes
- Visibility changes propagate immediately; refreshing a guest's tab is enough.
- Workspace members of the underlying project still see every interface they have project-level access to — per-interface invites grant access to outside guests, they don't take access away from existing members.
- Audit who has access by reviewing the Project Collaborators table in the Share dialog regularly.