> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/trulyp/writebackextreme/schemas/audits.md).
# Schema audits
Schema audits provide a history of changes made to records in a Writeback schema.
To view Audits of a schema, click on the "Audits" tab in the relevant schema.
Use schema audits to answer questions such as:
* Who changed a record?
* What type of change was made?
* Which record was affected?
* When did the change occur?
* Which values were changed?
### Audit statuses
| Status | Description |
| ------------ | ------------------------------------------------------------------- |
| **Created** | A new record was added. |
| **Updated** | An existing record was changed. The audit shows the changed fields. |
| **Deleted** | A record was removed. The audit preserves its previous values. |
| **Rollback** | A previous record state was restored. |
### View schema audits
1. Open the relevant Schema.
2. Select the **Audits** tab.
3. Review the audit history.
Each audit entry includes:
* **Member** who made the change
* **Audit status**
* **Record ID**
* **Date and time**
* **Changed values**, when available
{% hint style="info" %}
Hover over a **Record ID** to see the recorded field changes.
{% endhint %}
### Filter audit history
Use the available filters to narrow the audit history:
| Filter | Description |
| ---------- | ------------------------------------------------------------------------- |
| **Search** | Searches the recorded changes. |
| **Date** | Shows changes made on a specific date. |
| **Status** | Filters by **Created**, **Updated**, **Deleted**, or **Rollback** events. |
| **Member** | Filters changes made by a specific member. |
### Audit storage
By default, schema audits are stored in the **Writeback repository database**.
You can optionally move audits to the database associated with the schema's connection. This is useful when you need to query audit data directly alongside the schema data.
The current audit storage location is shown at the top of the **Audits** tab:
* **Repository database**
* **Same database as this schema**
### Move audits to the connection database
Members with **schema manager** permissions can move a schema's audits to its connection database.
1. Open **Audits**.
2. Select **Audit data locations**.
3. Find the relevant connection.
4. Select **Move all audits**.
5. Confirm the operation.
The process creates an audits table in the connection database if one does not already exist, then moves the existing audits for the schemas on that connection.
{% hint style="warning" %}
**Moving audits is irreversible.**
The operation may take longer when the connection uses a cloud data warehouse such as Snowflake, Databricks, or BigQuery.
{% endhint %}
#### After moving audits
After the move:
* New audits for the schema are stored in the connection database.
* Existing audits remain available from the schema's **Audits** tab.
* The audit data location is marked as **Moved**.
### Permissions
Viewing and managing schema audits requires the **schema manager** permissions.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.infotopics.com/trulyp/writebackextreme/schemas/audits.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
