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

# Audit trail

> See who changed what in your organization, filter the changes, and export them.

**Audit trail**, under **Prove** in the sidebar, lists every change made in your organization, newest first. Owners and admins see it; members do not.

## What is recorded

Each entry says when it happened, who did it, what happened, and what it was done to. For example:

| What happened | Target |
| - | - |
| Changed a member's role | The member |
| Applied guardrails | The AI system |
| Created a virtual key | The key |
| Changed content logging | The organization |
| Changed an alert rule | The rule |
| Opened an incident | The incident |
| Dismissed traffic in Discover | The key |
| Decided about a model in the Model catalog | The model |
| Changed an MCP server's owner, status or tool risks | The MCP server |
| Started an access review | The review |
| Ran a red-team against guardrails | The AI system, or the organization |
| Viewed the content of a request | The request |

Altrum records changes to your account, members and invitations, the organization and its alert rules, incidents (opened, changed, a note added, a request linked), AI systems, assessments, guardrails, the AI Gateway's settings, credentials, MCP servers, prompts and prices, virtual and personal keys, traffic dismissed in [Discover](/discover) or brought back, decisions in the [Model catalog](/model-catalog), with Approved models only turned on or off, the owner, status and tool risks of [MCP servers](/mcp-servers), [access reviews](/access-reviews) (started, keys kept or revoked, completed) and [red-team runs](/guardrails/red-team). Every time someone reads the kept content of a request, that is recorded too.

An entry names the fields that changed, never what they changed to. A password, a key or a message never appears in one.

A change made by someone at Altrum acting for your organization, such as extending your plan, shows as **Altrum support**. A change Altrum made by itself, such as a plan ending, shows as **Altrum**.

## Find a change

* Pick a date range from **Today**, **7 days**, **30 days**, **This month**, **Last month** and **This quarter**, or set **From** and **To**. Ranges are up to 400 days. The page opens on **30 days**.
* Filter by **Person**, by **Action** (**Account**, **Members**, **Organization**, **AI systems**, **Projects**, **Assessments**, **Guardrails**, **AI Gateway**, **Keys** and **Content**, several at once) and by **Target**, the kind of thing changed.
* The range and the filters are part of the page's address, so a link you share opens the same view.
* Select an entry to see the full time with its time zone, the fields that changed, the action's name and the request id. Quote the request id to support when you ask about a change.
* **Load more** shows 50 more entries.

## Export

**Export CSV** saves the entries loaded on screen: the time, the person, what happened, the action's name, the target, the fields changed and the request id. **Print** prints the page in black on white.

## How long entries are kept

Entries are kept for 24 months, then deleted.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.