Admin Activity Log & Audit Trail

No. The core logs keep working as configured in Settings → Logging. This add-on records what they do not: the old and new values of every changed field, settings and add-on changes, payment, shipping, promotion, user group and vendor changes, and the request context (dispatch, IP address, browser).

No. Password, key, token, card and credential fields are masked before anything is written, payment processor and carrier settings are masked as a whole, and values that look like card numbers are masked wherever they appear. User passwords and API keys show only Changed (value hidden). You can add your own field names in Also mask fields containing.

The storefront is not touched at all. In the admin panel a page view costs nothing measurable; a save costs one insert plus a few small reads of the changed objects (about 3.5 ms for a product on our test stores). The diffs are taken only for the object types you select.

A bulk edit is one entry with all changed objects (up to 200 with diffs, the rest counted). Imports and other cron jobs run from the console, which is not recorded by default; switch on Console and cron in Record actions from if you want them.

Entries cannot be edited. Administrators with Manage the activity log can purge entries older than a number of days, and every purge is itself logged (and can send an alert). Changes made directly in the database are found by Verify integrity.

No. Only actions in the admin panel, the vendor panel, the REST API and (optionally) the console are recorded. When an administrator edits a customer account or an order, the change is recorded like any other admin action.

The log holds the name and e-mail of the staff member who acted, the IP address and browser of the request, and the changed values, which can include personal data of the edited customer account or order (for example a new e-mail or address). Keep only what you need:

• set Keep entries for (days) to your retention period (365 days by default; entries are deleted daily);
• choose IP addresses: Anonymized or Do not store;
• choose Store request parameters: Parameter names only or Nothing;
• mention the activity log (security and accountability of staff actions, legitimate interest) in your privacy notice for staff.

To answer an access or erasure request, filter the log by the person's e-mail and export or purge as needed.

No. Vendors see only the actions of their own administrators. The marketplace administrator sees everything, including actions taken through Act on behalf of.

Without a valid license (no key after the 14-day start period, an invalid or revoked key, a domain the license does not cover, or no successful check for 14 days), no new activity is recorded and no alert e-mails are sent. The existing log stays readable, exportable and purgeable. Once the license is valid again, recording resumes.

Open Add-ons → Manage add-ons → Admin Activity Log & Audit Trail → Settings → License. The status line says what is wrong: no key, a key for another add-on, a revoked license, or a domain that the license does not cover. Fix it and click Check now. See License.

Yes. Subdomains of your licensed domain (for example staging.yourstore.com) and local development hosts (localhost, private IP addresses, .local, .test) are covered by the same license.

No. The check runs in the admin panel or from cron, once a day. The storefront never runs it.