Summary
Use this page as a fast reference for how public report sharing works in TruAgents.Core distinction
| Mode | Intended audience | Access model | Where it starts |
|---|---|---|---|
| Analytics | Authenticated users inside the app | App access | Analytics |
| Public report | External or broader viewers | Tokenized share link | Created from Analytics, managed in Published Reports |
Key properties
- Public reports are share links, not normal user seats.
- Public reports can be managed after creation.
- Token rotation should be treated as a meaningful security or access-reset action.
- Public reports belong to a reporting workflow, not to the core communications workspace.
What the current product implies
The current reporting flow strongly suggests that public reports can:- be active or inactive
- be opened directly by tokenized URL
- have their tokens rotated
- be deleted entirely
Practical implications
Rotation
Rotation should be treated like replacing the external key to the report.Inactive status
If a report is inactive, the first troubleshooting question should be status, not browser caching.Deletion
Deletion is final, so teams should treat it differently from deactivation or token rotation.Simple version
Public reports are controlled external views:- not app logins
- not teammate seats
- not just screenshots in link form
What to document more deeply later
- Which filters or scoping rules can be locked into a public report
- How rotation affects old links
- What inactive versus active status means operationally