Account trail
Recent account and security events that help explain what changed.
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 to change security settings. Use Audit to read the trail, compare sessions, and collect safe context before asking for help.
Start Here If
Section titled “Start Here If”- an active browser looks unfamiliar;
- you need to understand recent account or security changes;
- support asks for a safe account history packet;
- you want to compare sessions before removing old browsers;
- a profile, sign-in, or setup question needs a short timeline.
What Audit Shows
Section titled “What Audit Shows”Sign-ins and sessions
Recent browser sessions, sign-in history, and session context you can compare with Profile.
Visible actions
User-visible account actions that can help build a timeline without exposing private files.
Audit packet
A downloadable JSON packet for support after you inspect and decide it is safe to share.
Audit Is Not Profile
Section titled “Audit Is Not Profile”| Need | Start with |
|---|---|
| Change two-step sign-in, recovery codes, avatar, or browser sessions | Profile and Security |
| Review account trail, sign-ins, sessions, visible actions, or export safe context | Audit |
| Confirm a plan limit or locked action | Billing and Plans |
| File a support request after checking the owner page | Get Support |
Safe Support Packet
Section titled “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.
Before You Share
Section titled “Before You Share”- Refresh Audit. Make sure the timeline reflects the latest state.
- Compare sessions. If a browser looks unfamiliar, use Profile to remove old sessions before continuing.
- Download only when needed. Use the audit packet when support asks for account history context.
- Inspect the packet. Confirm secrets, setup links, connection files, recovery codes, and private customer data are not included.
- Attach it deliberately. Add it to a support request only after redaction and only when it helps the question.
Good Uses
Section titled “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
Section titled “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.