# Audit

> Review account actions, sign-ins, sessions, and a support-safe history packet without exposing secrets.

Source: https://docs.thalovant.com/account/audit/

---
Audit is the account history page.

Use Audit when you need to review recent account activity, sign-in and session history, visible actions, or a support-safe history packet.

Use [Profile and Security](/account/profile-security/) to change security settings. Use Audit to read the trail, compare sessions, and collect safe context before asking for help.

## What Audit Shows

The page has three sections, and they are named here the way the screen names
them.

  
    Recent sign-ins and browser sessions, with the context you can compare
    against Profile when something looks unfamiliar.
  
  
    Account actions you can see, for building a timeline without exposing any
    private file.
  
  
    A downloadable JSON packet for support — after you have read it and decided
    it is safe to share.
  

If the page says **Some audit sources are unavailable**, the sections it could
not reach are missing rather than empty. Refresh before reading absence as
evidence.

## Audit Is Not Profile

| Need | Start with |
| --- | --- |
| Change two-step sign-in, recovery codes, avatar, or browser sessions | [Profile and Security](/account/profile-security/) |
| Review account trail, sign-ins, sessions, visible actions, or export safe context | Audit |
| Confirm a plan limit or locked action | [Billing and Plans](/workspace/billing-and-plans/) |
| File a support request after checking the owner page | [Get Support](/account/get-support/) |

## Safe Support Packet

The audit packet is designed for support context. It can include account posture, session inventory, visible action trail, and support-safe metadata.

It should not include tokens, passwords, API keys, client secrets, setup links, connection files, recovery codes, payment data, or private customer data.

When you delete the account through Profile and Security, user-linked product telemetry,
activation milestones, analytics session summaries, analytics exports, and linked audit
traces are erased as part of account deletion. One unlinkable `user.delete-self` marker is
retained with no account ID or profile snapshot so the deletion operation remains
auditable.

  Inspect the packet before sharing it. If anything looks sensitive, remove it or ask for a safer support path before posting.

## Before You Share

1. **Refresh Audit.** Make sure the timeline reflects the latest state.
2. **Compare sessions.** If a browser looks unfamiliar, use Profile to remove old sessions before continuing.
3. **Download only when needed.** Use the audit packet when support asks for account history context.
4. **Inspect the packet.** Confirm secrets, setup links, connection files, recovery codes, and private customer data are not included.
5. **Attach it deliberately.** Add it to a support request only after redaction and only when it helps the question.

## Good Uses

Use Audit to answer:

- Which browser sessions are active?
- Did account security change recently?
- Does the timeline match the action you expected?
- Is there safe context to include with a support request?
- Should Profile be opened before a setup link, connection file, or session question continues?

## Audit Is Ready When

Audit is ready when:

- the session list matches the browsers you recognize;
- old sessions have been removed in Profile when needed;
- the timeline gives a clear before-and-after story;
- the audit packet has been inspected before sharing;
- the support request includes the page, goal, visible status, status-page check, and any safe packet context.

Open Profile and Security
Prepare a support request