> For the complete documentation index, see [llms.txt](https://docs.securepass.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.securepass.me/documentation/admin-user-guide/configuration/audit-log-configuration.md).

# Audit log configuration

This is where you decide what SECUREpass records. Everything the audit reports and the compliance evidence rest on is switched on or off here, which makes it one of the more consequential screens in the console.

Select **Configuration → Audit Log Configuration**.

![The Audit Log Configuration page.](https://content.gitbook.com/content/W2srIAMN6RKFwvuEorV5/blobs/9pJpF5h9N7oYeBeZkBea/assets/01.png)

The summary across the top shows how many products have logging enabled and disabled, how many logs were written today, how many are stored in total, and whether LogManager — the store itself — is reachable.

## The master switch

The **Audit Log Configuration (Master Switch)** turns recording on or off for every product at once.

{% hint style="warning" %}
With the master switch off, **no product records audit logs**, regardless of its own switch. Nothing is written, and nothing appears in Live Logs — so there is no record that recording was ever turned off either. Leave it on in any environment where the audit trail matters.
{% endhint %}

## Per-product switches

Below it, each service is listed with its status, how many events it recorded today, when it last recorded one, and its own toggle.

Turning a product's switch off stops its events being recorded anywhere. LogManager is the only store, so an event not recorded is not retrievable later from somewhere else.

## Live Logs

The eye icon on a row opens **Live Logs** for that product, and **Live Logs (All)** opens them across every product.

![Live Logs.](https://content.gitbook.com/content/W2srIAMN6RKFwvuEorV5/blobs/xeFBrkA24Ysw2NkZNL2P/assets/02.png)

This is the working view — what is being recorded right now, useful when you are checking that a change took effect or watching an action as it happens.

## Manage — event-level control

**Manage** opens the operations for one product.

![Managing which events are recorded.](https://content.gitbook.com/content/W2srIAMN6RKFwvuEorV5/blobs/QqB0eAD3JuVZYiBuXDFh/assets/03.png)

Each product is broken into modules, and each module into individual events. Turn off a whole module, or uncheck individual events within it. The counters show how many modules and events exist and how many are being logged.

The page also shows, per event, how many logs it has produced, its share of the total, and when it was first and last recorded — which is the honest way to decide what is worth keeping.

{% hint style="info" %}
Anything switched off here is not stored and is hidden from Live Logs. Before turning an event off to reduce noise, check whether it is one an auditor would expect to find. Volume is a poor reason to stop recording something.
{% endhint %}