Public Sharing
Atlas supports exposing dashboards externally via token-based public links. Anyone with the public link — without a Pirivision account — can view the dashboard. Use it for KPI reports shared with customers, public-facing operations screens, and dashboard demos for external stakeholders.
Prerequisite
An Atlas dashboard must exist for which to generate a public link. Public links can only be opened for dashboards you own.
Security Warning
A public link grants viewing access to anyone with the token. The token is the URL itself — anyone who obtains it can access. Do not use public links for dashboards with sensitive data, or rotate the link regularly.
1. Open the Share Dialog
In the Atlas list, click the More (three dots) menu on the dashboard card → click Share.
The dialog has two sections:
- Left panel: Per-username sharing → User Sharing
- Right panel: Public link management (this page)
2. Generating a Public Link
Click the Generate Public Link button in the right panel. The backend calls the create_public_link API and produces a unique token.
After the token is generated, the link appears in this format:
| Action | Behavior |
|---|---|
| Copy Link | Copies the link to the clipboard |
| Open in New Tab | Opens the public viewer in a new tab |
| Revoke | Cancels the link; the token no longer works |
3. Public Viewer Behavior
When the public link is opened:
| Behavior |
|---|
| The login screen is not shown; the dashboard loads directly |
The backend validates the token via bypassAuthMiddleware: true |
isPublicMode = true is set; the UI top bar is hidden or minimal |
canModify = false — no edit mode, save, share, delete buttons |
| The user can change the global filter (per session) |
| Refresh interval works as configured in Cartography |
core-service calls carry the public token info |
Public Mode Endpoint
The public viewer fetches the dashboard layout from a special endpoint:
This endpoint is bypassed by the auth middleware.
4. Multiple Public Links
You can produce multiple public links for a dashboard. Typical uses:
| Scenario | Approach |
|---|---|
| Separate link for customer A and customer B | Generate two separate tokens, share separately |
| Disable an old expired link | Generate a new token, revoke the old one |
| Temporary demo link | Revoke after the demo |
All active links are listed in the share dialog's right panel.
5. Revoking a Link
Click the Revoke button next to the active link. The token is deleted from the backend; browsers using that link receive 403 Forbidden.
Instant Revoke
After Revoke, users with the link still open lose access on page refresh. They can keep viewing as long as the page stays open (cached data).
6. Token Security
| Risk | Mitigation |
|---|---|
| The token URL leaks via logs (proxy, browser history, screenshots) | Avoid public links for sensitive dashboards |
| The token may be shared via social engineering | Generate a separate link per customer; revoke only that link if abused |
| Browser cache | Dashboard may remain visible after logout |
7. Audit / Log
Public link accesses are recorded in backend logs (IP, timestamp). To query how often a link was used, inspect the backend logs; this is not surfaced in the UI.
8. Common Errors
| Symptom | Possible Cause | Solution |
|---|---|---|
| Generate Public Link is disabled | You are not the owner | Ask the authorized user to generate it |
| Public link returns 403 | Token revoked or wrong | Generate a new link |
| Widgets do not load in public mode | The Compass query requires auth | Check the data source permissions on the query |
| Link will not copy | Browser clipboard permission denied | Copy manually (Ctrl+C) |