Web maps live in Tamaat Server (account menu → Open Server) — your organization's shared catalog of everything deployed, separate from the daily map-building workspace.
The lifecycle
- Share to Server (from the project menu in Map Builder) cuts an immutable release — your chosen layer versions and styling, frozen — into the Non-production environment. Sharing again cuts v2, v3, and so on.
- Preview Non-production with an expiring preview link (no Tamaat account needed for reviewers).
- Promote a specific release to Production. Protected environments route this through request → approval. The public URL updates the moment promotion completes.
- Roll back to any earlier release instantly — releases are immutable, so history is always available.
What Server shows you
- Which release each environment currently serves, and whether Production is behind Non-production
- Stable public URLs (and custom domains on Enterprise plans), plus access mode — public or token-restricted
- The activity record: who shared, promoted, approved, or rolled back, and when
- One project can back multiple web map deployments with different names and audiences
Why this matters
Editing a project never changes a live map. That separation lets authors keep working freely while the audience-facing map stays exactly as approved — and makes "what is production serving?" a question with a recorded, auditable answer.