Skip to main content
Open Settings → Personal → Trace privacy to see what Atlan keeps from your agent sessions. Everyone can review their own available history; organization admins with settings access can change the organization policy.

​
Content and usage are separate

Turning session-content storage off leaves usage analytics available. A device configured to drop content continues dropping it even when the organization allows storage.

​
Change content storage

  1. Open Trace privacy and select Organization settings.
  2. Review Store session content.
  3. Change the control. Turning collection on asks you to confirm the effect for everyone in the organization.
  4. Confirm that the saved state is shown after the request completes.
The policy applies to sessions collected after the change. Enabling storage does not recover content that was already dropped. Changing it does not erase content that was previously stored.

​
Review your history

The history lists sessions from the last 30 days. Search the list and open a session to inspect the content available for it. A trace can report that message content is unavailable while still showing usage evidence. If the trace has more spans than the page can load, the page states the limit. If loading later spans fails, retry before treating the visible timeline as complete. For control over fields sent by your own application, see SDK trace privacy. Configure collection at the source before sending sensitive content.