> For the complete documentation index, see [llms.txt](https://docs.datasentinel.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datasentinel.io/manual/implementation/platform-usage/configuration/audit.md).
# Audit
Datasentinel can audit the actions performed by your declared users on the platform.
You can thus know the Datasentinel modules as well as the selected instances with their date of use.
Convenient if you want to delete inactive accounts for example
## Configure
{% hint style="info" %}
On a new installation, the audit is **enabled** with a retention of **60** days.
{% endhint %}
{% stepper %}
{% step %}
### Open tools menu
>
{% endstep %}
{% step %}
### Global settings
>
{% endstep %}
{% step %}
### Audit settings
Audit settings
Enable or disable audit logging and configure the retention period (in days) for audit records.
When audit logging is enabled, Datasentinel records all user actions, including the module used and the selected PostgreSQL instance.
{% endstep %}
{% endstepper %}
## View
From the **Tools** menu, click **Users**.
The **Last Use** field shows the date of the most recent action performed by each user.
Audit last use
All user actions can be viewed in the **Usage** tab.
Usage
Actions are grouped by user and PostgreSQL instance. For more detailed analysis, results can also be grouped by day and/or module.
The **Number of Uses** column shows how many times each action was performed.
{% hint style="info" %}
Actions can also be viewed at the individual user level.
{% endhint %}
User audit actions
---
# 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.datasentinel.io/manual/implementation/platform-usage/configuration/audit.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.
{% endstep %}
{% step %}
### Global settings
> 
{% endstep %}
{% step %}
### Audit settings
