> For the complete documentation index, see [llms.txt](https://docs.alemba.com/asm-hermes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alemba.com/asm-hermes/setup-and-configure-asm/configuring-your-system/system-administration-settings/system-settings-menu/auditing.md).

# Auditing

When Change Reasons are enabled, Analysts must specify a reason for the change in the **Change Reasons** window. This reason is recorded in the [Administration Audit Trail.](/asm-hermes/setup-and-configure-asm/configuring-your-system/system-administration-settings/system-settings-menu/auditing/administration-audit-trail.md)

{% hint style="warning" %}
This does not enable or disable auditing of system administration or ASM Designer. This is always enabled. You can only specify whether analysts must enter reasons for changes they make.
{% endhint %}

{% hint style="info" %}

### Before you start

You must have **System Set Up** selected in the Admin tab of your **General Access security role**.
{% endhint %}

1. Select the Menu button, then **Admin**, then select **System Administration**. The System Administration window appears. 
2. In the Explorer pane, expand **System**, then select **Auditing** to display the **Auditing** window, showing the following information:

<table><thead><tr><th width="223">System Configuration</th><th>Enables Change Reasons on all changes made in the system administration settings</th></tr></thead><tbody><tr><td>Designer</td><td>Enables Change Reasons on changes to screens, forms and message templates in ASM Designer</td></tr></tbody></table>

3. Save the changes.
   1. The reasons given appear in the [Administration Audit Trail](/asm-hermes/setup-and-configure-asm/configuring-your-system/system-administration-settings/system-settings-menu/auditing/administration-audit-trail.md) (for configuration settings) and on any screen, form, or message template history for changes made through ASM Designer.

## Data Purge/Retention Period

Applies to ASM 10.6.8.15038

1. Select the Data Retention/purge options
   1. Data Retention Period (Years): Defaults to 7 years.&#x20;
   2. Delay Period (Days): Defaults to 30 days.

The default retention period and delay settings can be modified in System Administration as per organizational requirements. More information about the Data Purge service are available on the [Configuring the Data Purge Service](https://docs.alemba.com/asm-hermes-10.6.8/setup-and-configure-asm/configuring-your-system/configuring-the-data-purge-service) page.


---

# 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.alemba.com/asm-hermes/setup-and-configure-asm/configuring-your-system/system-administration-settings/system-settings-menu/auditing.md?ask=<question>&goal=<endgoal>
```

`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.