> For the complete documentation index, see [llms.txt](https://docs.momocode.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.momocode.de/en/shopware-6/admin-activity-log/3.-configuration.md).

# 3. Configuration

The plugin configuration is located under **Extensions → My Extensions → Admin Activity Log → Configure**.

![Plugin configuration page with entity scope, retention period, and system actions toggle](https://459847022-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtiS3-dzuXFp_IH7yRw-1972196547%2Fuploads%2Fgit-blob-8cefdb03df5caa32e36523a42d9c5f5e3eb07756%2F5.png?alt=media)

## Tracked Entities

| Setting    | Value                                          |
| ---------- | ---------------------------------------------- |
| Config key | `trackedEntities`                              |
| Default    | Products, Orders, Customers, Categories, Media |
| Type       | Multi-select                                   |

Choose which entity types should be tracked in the activity log. Changes to unselected entities are not logged.

Available entity types:

* Products
* Orders
* Customers
* Categories
* Media
* Manufacturers
* Properties
* Shipping Methods
* Payment Methods
* Sales Channels
* CMS Pages

**Note:** Changes take effect immediately for new log entries — no cache flush or restart required. Existing log entries for deselected entities are preserved.

**Note:** Order, delivery, and payment status transitions are captured automatically regardless of whether "Orders" is selected. Third-party plugins can register additional entities — see [Developer Extension API](/en/shopware-6/admin-activity-log/5.-extension.md).

## Excluded Associations

| Setting    | Value                    |
| ---------- | ------------------------ |
| Config key | `excludedAssociations`   |
| Default    | empty (nothing excluded) |
| Type       | Multi-select             |

Some plugins attach a very large number of related records to every record, for example stock movements of an ERP system on every product. This quickly clutters the log. Select these associations here so that **no new log entries** are created for them.

Each option shows the association with a readable label, its technical name, and the parent entity, for example "Prices (prices) — Product". A selection always applies only to the named entity. The search field matches both the label and the technical name.

* All other changes to the same record are still logged.
* If a change consists only of excluded associations, no log entry is created.
* Existing log entries are not changed.
* The setting takes effect immediately for new writes — no cache flush required.

**Note:** The list shows the associations of the saved **Tracked Entities**. If you have just added an entity, save the configuration first and reload the page so that its associations appear.

**Note:** Stored entries that are no longer detected (for example after uninstalling a plugin) are shown as "(no longer detected)", are ignored, and can be removed.

## Retention Period

| Setting    | Value           |
| ---------- | --------------- |
| Config key | `retentionDays` |
| Default    | 90 days         |
| Type       | Single-select   |

Configure how long log entries are retained before automatic deletion.

| Option      | Description                                                |
| ----------- | ---------------------------------------------------------- |
| 30 days     | Entries older than 30 days are deleted daily               |
| 60 days     | Entries older than 60 days are deleted daily               |
| **90 days** | **Default** — entries older than 90 days are deleted daily |
| 180 days    | Entries older than 180 days are deleted daily              |
| 365 days    | Entries older than 365 days are deleted daily              |
| Unlimited   | No automatic deletion                                      |

Cleanup runs daily via a scheduled task. Expired entries are removed together with all associated field change records.

## Log System Actions

| Setting    | Value              |
| ---------- | ------------------ |
| Config key | `logSystemActions` |
| Default    | enabled            |
| Type       | Boolean (yes/no)   |

Controls whether writes triggered by the following sources are logged:

* CLI commands (`bin/console`)
* Scheduled tasks
* API integrations without a logged-in admin user

**Enabled (default):** All writes are logged regardless of their source. API integrations appear with the integration name and an "Integration" badge.

**Disabled:** Only changes directly triggered by a logged-in admin user appear in the log.

**Note:** Login events are always logged regardless of this setting.

## Store Readable Names for Referenced Records

| Setting    | Value                   |
| ---------- | ----------------------- |
| Config key | `resolveReferenceNames` |
| Default    | enabled                 |
| Type       | Boolean (yes/no)        |

Controls whether references to other records — for example manufacturer, tax rate, category, or sales channel — are stored as "Name (ID)" instead of the bare ID.

**Enabled (default):** Names are resolved when the log entry is written, collected per entity type.

**Disabled:** Only IDs are stored. This can improve performance during very large imports. For associations such as categories or tags, the plugin then behaves as it did before this feature was introduced.

**Note:** The setting only affects new entries. Entries that are already stored are neither converted nor deleted.