A single Atlas project can host multiple interfaces. Each interface is its own configuration — sections, widgets, layout, theme, layer selection, and permissions. What every interface in a project shares is the underlying data: the datasets, connections, comments, and threads. Use multiple interfaces when different audiences need different views of the same project data: an internal dashboard, a public-facing map, a print-ready report, a field app overview.
Why multiple interfaces
Common use cases:
- One dataset, many audiences — public stakeholders see a stripped-down map; the team sees the full data table and analysis widgets.
- Onboarding flow — a Welcome interface with instructions and links into deeper interfaces.
- Mode separation — a map interface for exploration, a full-page interface for KPIs and reporting.
- Localised variants — swap text and titles for different languages while keeping the same data.
Add an interface
In the Builder, open the interface dropdown and click New interface. Pick a template (e.g. Blank interface or Full page) and give it a name. The new interface starts empty; configure sections and widgets as usual.
Switch between interfaces
The interface navigation dropdown sits in the project header. Click it to see all navigable interfaces in the project; click any one to switch.
- Active interface is highlighted in the dropdown.
- Use Arrow keys, Home, and End to move focus inside the dropdown; Enter to switch; Esc to close.
- The dropdown only appears when more than one interface is navigable from the current view.
Rename, reorder, or delete
Open an interface's settings to rename it. Drag interfaces in the list to reorder them — the order in the dropdown matches the order in settings.
Delete an interface from its settings; deletion is scoped to that interface only and does not affect the project's underlying data or other interfaces.
What's per-interface vs. shared
Each interface has its own:
- Layout (sections, widgets, themes).
- Settings (map controls, fullscreen, static-map toggle).
- Layer selection — each interface picks which of the project's layers to include and in what order. Including a layer in one interface doesn't add it to the others.
- Public-access state and per-interface invites — see Interface permissions.
What's shared across every interface in a project:
- Datasets, columns, and records (the underlying data).
- Connections to external data sources.
- Comments and threads (anchored to features/locations, not interfaces).
- Project-level access (workspace members who already have access to the project).
- Project-level settings like map origin and locked map bounds — see Project Settings.
Sharing one interface vs the whole project
Each interface has its own visibility (public/private) and viewer list, gated by your plan. See Interface permissions for the full breakdown.