> ## Documentation Index
> Fetch the complete documentation index at: https://docs.truagents.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Share and manage public reports

> Create and maintain shareable analytics links without giving recipients access to the main app.

## Summary

Public reports let teams share analytics outside the authenticated product experience.

The current app makes this workflow fairly explicit:

1. create the share link from **Analytics**
2. copy the generated link immediately
3. manage it later from **Analytics → Published Reports**

## Who this is for

* Operators sharing performance results outside the app
* Campaign managers who need controlled reporting distribution
* Admins responsible for link hygiene and reporting access

## Where to find it in the app

* **Analytics**
* **Analytics → Published Reports**

## Typical workflow

1. Open **Analytics** and determine what should be shared.
2. Click **Share** from the analytics header actions.
3. Copy and distribute the generated link.
4. Revisit **Published Reports** to review, disable, rotate, or delete the link later.

## What gets locked into the report

The current creation flow builds the share link from the analytics view you are already looking at.

That means a public report can carry forward current scope such as:

* selected channel
* selected campaign
* selected segments
* default date range

One important nuance from the current implementation: dates remain adjustable on the public report, even when the report is otherwise locked to a specific scope.

## Locked versus adjustable behavior

| Part of the report    | Expected behavior                                        |
| --------------------- | -------------------------------------------------------- |
| Channel scope         | Can be locked when the report is created                 |
| Campaign scope        | Can be locked when the report is created                 |
| Segment scope         | Can be locked when the report is created                 |
| Tokenized access link | Created for the specific report and can later be rotated |
| Date range            | Still adjustable on the shared report                    |

## What the management surface supports

From **Analytics → Published Reports**, teams can manage the link over time. The current app supports:

* activating or deactivating a report
* rotating the token to create a new link
* deleting the report
* opening the public version in a new tab
* reviewing the locked scope and report configuration from the management table

## When public reports are the right tool

Use a public report when you want someone to see reporting without giving them a normal authenticated app experience.

Good examples:

* sharing results with an external stakeholder
* sending a controlled status view to a client
* giving a broader audience visibility into outcomes without creating user seats

Avoid using a public report when the recipient actually needs to operate the product or investigate deeply inside internal workflows.

## Safe sharing checklist

Before you send a link, confirm:

* the selected channel or campaign scope matches what you intend to share
* the date range defaults make sense
* the link is meant for link-based viewing, not for active collaboration inside the app
* someone on the team owns the ongoing hygiene of that link

## Common mistakes

* assuming a public report is equivalent to giving someone app access
* forgetting that the link may still allow date changes even when channel or campaign scope is locked
* sharing a link without reviewing whether the current analytics filters match the intended audience
* rotating or deleting a link without warning people who depend on it

## Success checklist

* [ ] The team understands that a public report is a share link, not a normal app seat.
* [ ] Report owners know where to disable or rotate a link later.
* [ ] Teams understand which parts of the analytics view are locked into the report and which are still adjustable.
* [ ] Shared links are created intentionally and reviewed periodically.

## Related pages

* [Analytics and public reports](/concepts/analytics-and-public-reports)
* [Analytics and report links](/support/analytics-and-report-links)
* [Report sharing model](/reference/report-sharing-model)