There are two different jobs here, and Tamaat keeps them deliberately separate:
- Distribution is delivering a dependable resource to a wider audience — a public web map, a scheduled pipeline, an API. Distribution goes through Tamaat Server: you Share to Server, which cuts an immutable release into your organization's Non-production environment, and an authorized member Promotes a specific release to Production. Editing your project never changes what Production serves — only Promote (or Rollback) does.
- Collaboration is working with colleagues inside the project — shares, comments, and versions. Collaboration never touches Server and can't affect anything your audience sees.
Nothing in the daily workspace can target Production directly. That rule is what makes "it's in Production" a statement you can trust.
Guides
Share to Server, promote, and manage live web maps.
8 min
Versions, sharing, and project discussion.
8 min
- Confirm symbology and sensitive fields, and publish the layer versions you want to pin
- Choose Share to Server from the project menu to cut a release into Non-production
- Review the release in Server (account menu → Open Server), then Promote it — or collaborate instead
FAQ
Do published map viewers need a Tamaat account?▾
No. Production web maps are either public or restricted by an access token. Non-production maps are reviewable through expiring preview links, so stakeholders can QA without an account.
I edited my project — why didn't the live map change?▾
By design. The live map serves the release that was promoted to Production. Share your changes to Server (a new release in Non-production), then promote that release when it's ready. Rollback can restore any earlier release just as quickly.
Who can promote to Production?▾
Each environment has a protection rule. By default, Production requires an organization admin or owner; analysts request promotion and an approver confirms it, with the decision recorded in the Server activity log.