Two different jobs, kept deliberately apart.
Collaborating happens inside the workspace, with named colleagues. Share a layer, a project, or a group; give someone "View", "Edit", or "Owner"; talk it through in the Comments panel. Everyone sees the project as it is right now.
Publishing is for an audience outside that. "Publish to Server" takes a snapshot of your work and puts it somewhere people can reach — a public web map, a dashboard, an API, a scheduled flow. Carrying on editing your project doesn't change what they're looking at, which is the whole point.
Guides
Publish a map to a public URL.
6 min
Turn a map's data into a page of charts and indicators.
8 min
Start from one, or publish one for your team.
5 min
Where your published work is operated.
3 min
Let AI agents call what you've published.
4 min
Sharing, permissions, versions, and comments.
8 min
How it connects
Maps aren't the only thing you can publish — ETL flows and API products go the same way.
Do people viewing a published map need a Tamaat account?▾
No. A published map is either open to anyone with the link, or protected by a token you give out. You can also send a reviewer a short-lived preview link before anything goes live.
I edited my project — why didn't the published map change?▾
By design. The published map shows the version you published, so your work in progress never surprises your audience. Publish again when you're ready for them to see it.