> 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/writebackextreme/features/management-console/schemas/audits.md).
# Audits
WriteBack Extreme keeps an audit trail of changes for visibility and compliance. There are two audit types: **Schema Audits** (changes coming from the Tableau extension) and **System Audits** (changes made in the Management Console).
### Schema Audits (Tableau Extension)
Schema audits capture changes created via the Tableau extension. By default, schema audits are stored in the **repository database**.
Schema Audits can be accessed from either the general Audits page in the main menu or on the audits tab of the schema edit page.
### Remotely Access audits
From version 6.0 it is possible to move audit data of schemas to a **connection database** which enables the ability to query them directly from your tableau dashboard. Go to the general Audits page (accessible from the main menu) and click the \`Audit data locations\` link in the blue box to open the page where you can move the audit data.
***
### System Audits (Management Console)
System audits track changes performed inside the Management Console (e.g., users, groups, schemas, connections, semantic models).
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.infotopics.com/writebackextreme/features/management-console/schemas/audits.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
