Public maps
Sometimes the point of a map is to be seen — a roadmap for customers, a plan for a community, a course outline for students. A public link shows the map to people who are not on your instance at all.
Switching it on
In the map's share dialog, turn on Public link and copy the address. Anyone who can reach your installation's address sees the map through it — on a LAN or VPN setup that means the local network; on an instance behind a public domain it means the internet. Turning the toggle off revokes the link.
The public link is deliberately unlisted: the map is never offered or listed anywhere — the instance is not a shop window. Only people you send the address to can reach it. The project card reminds you with a "Public map" badge.
What a visitor sees
A visitor without an account gets the map canvas with a blue bar — "Publicly shared map — view only, changes are not saved" — they can browse and pan the map, and nothing more.
What the link shows — and what it never shows
A public link is read-only and shares only the map canvas: the goals, their statuses and the structure. Tasks, comments, attachments and the stash are not visible through it — the execution layer stays with the team.
Read-only for viewers, alive for you
The link always serves the current state of the map — visitors watch the plan progress without you exporting anything.
When a public link is not the right tool
- Somebody should edit or comment — share the map with their e-mail instead, or with the whole organization: Team and roles.
- The map should leave the instance as a file — use export to PNG, PDF or JSON.
Next
- Team and roles — the narrower sharing circles
- HTTPS and a reverse proxy — making the instance reachable from outside