Publishing takes a snapshot of your map rather than putting your live project online. Your audience sees a fixed thing; you carry on working without it shifting under them.
Publish it
When Ava Reyes is ready to publish "Harbourview Network Buildout", she opens the project menu on the map and chooses "Publish to Server".
- 1
Give it a "Name" — this becomes its address — and a "Release note" answering "What changed?". You'll be glad of the note in six months.
- 2
Check which version of each layer is going out. Click "Adjust" to pick a different one — you might hold "Pressure Zones" on last quarter's version while "Distribution Mains" takes the latest — then "Done".
- 3
Confirm. "View in Server" takes you to it.
Publishing again creates the next version. The one you published before stays exactly as it was.
Show someone before it goes live
Your map lands in Non-production first, and only goes live when it's promoted.
To get a review before that, use "Copy preview link". It gives you a link your reviewer can open without a Tamaat account, and it expires on its own.
Who can see the live map
Once live, your map is served at its own URL, and you choose how open it is:
- Public — anyone with the link.
- Restricted — the link only works with an access token you hand out. Without it, visitors are told: "This published web map requires an access token. Add ?access_token=... to the URL."
Your charts come along
If your project has analytics widgets, they travel with the published map. Viewers can filter with them, but can't change them.