Last updated September 11, 2026
Publishing Boards
Publishing gives stakeholders a read-only view without an account. They see only what you include.
What publishing is
A publication is a snapshot, not a live workspace window. A separate viewer renders it at provenmap.com/boards/{org}/{slug} with only selected content.
Workspaces, unpublished boards, source bindings, and conversations stay private.
The wizard
Publishing uses the board toolbar's Publish capsule:
Cover → Access → [Layers] → Contents → Review
Layers appears only when relevant. Review is the final step.
Cover
Set the title, address, and thumbnail. Choose the address deliberately; it is what readers see.
Access
Set who can open it and whether it is discoverable. List on the ProvenMap boards directory is opt-in.
Layers
This step appears when publishing a hub with layers. Choose which layer boards readers can navigate into.
Publish a single layer board and this step disappears.
Contents
Choose what a reader receives:
- Insights — analyses run on this board, one entry per batch
- Aspects — the typed detail on its nodes
- Skills — the app's capability profile
Two things are never publishable: intents and source bindings. The Pages screen is not a published surface either.
A publication includes the insight batches you choose, not an automatic "latest batch." Each selected batch becomes one entry in the published dossier. If an insight concerns a different board, the dossier labels it with that board. Turn insights off to exclude them.
Who can see it
Visibility has three modes.
Anyone with the URL can open it — no authentication. Best for open-source projects, public architecture showcases, or reference architectures you want shared.
- Discoverable, and eligible for the boards directory
- No tokens or passwords needed
Public and Unlisted are on every plan. Public boards are also listed in the boards sitemap, so a search engine can find them without a link from anywhere else.
Start with Unlisted while you are iterating. Move to Public when you are confident in the content, or Protected when the architecture is sensitive.
Password protection and token rotation
Password protection. Set visibility to Protected and enter a password of 4–128 characters. It is hashed server-side, so the plaintext is never stored. A visitor enters it to view the board. You can remove the password later and keep the share token if link-only access becomes enough.
Token rotation. Rotating generates a new random token immediately. Every existing link with the old token stops working, anyone with the new URL gets in, and password protection is unaffected. Use it when someone with access leaves the team, or as a periodic access reset.
Rotating a share token invalidates every existing link at once. After rotating, update bookmarks and embedded references with the new URL.
What a stakeholder gets
A reader opens the publication hub and can navigate included screens: diagram, insights, aspects, skills, and selected layers.
Absent content is not reachable: no workspace, other boards, source bindings, intents, conversation history, or editing.
Living with a publication
Once live, the publish screen shows Board published, Live on the web, and three actions:
- Update settings — reopen the wizard and change anything: the address, the visibility, which layers are included, which contents are included.
- Get embed code — drop the board into a wiki or an internal page.
- Unpublish — take it down. The URL stops resolving.
The boards list also shows a Published badge and the matching Publish to web or View on web action.