> From https://brixsignage.com/blog/digital-signage-audit-trail/ . All Brix pages as markdown: https://brixsignage.com/llms.txt

# What auditors check in a digital signage audit trail

An auditor checks who changed what and when, whether the log can be edited, how long it is kept, and how to export it.

Security Published October 27, 2026

An auditor checks four things in a digital signage audit trail: who changed what and when, whether the log itself can be edited, how long it is kept, and whether you can export it. If your security questionnaire has a line item for "audit and traceability", these are the four lines behind it; see [answering a digital signage security questionnaire](https://brixsignage.com/blog/digital-signage-security-questionnaire/) for the rest of what IT will ask.

You can ask any signage vendor these four questions before you sign. This page answers each one for Brix.

## The four-question checklist

Before you take a vendor's word for it, ask them to show you each of these, live, in a trial account.

-   **Who changed what, and when?** Every entry names the actor, the action, the target, and the time, down to the second.
-   **Can anyone, including the vendor's own staff, edit or delete an entry?** If the answer is "no, because of a policy", ask how you would know if that policy were broken.
-   **Can you get the data out, in a format your SIEM or auditor can read?** A log you can only view one page at a time in a browser is not an export.
-   **How long are rows kept, and what happens when that time is up?** A retention window with no fixed number, or one that changes with your plan, is not something you can write into a policy.

## Who changed what, and when

In Brix, every entry in **Settings > Audit log** records the actor (the member or the API key), the action, the target it acted on, the organization node it happened in, the IP address, and the timestamp to the second. Search by name, target, or phrase, and filter by action or actor. Sign-in attempts are not in the audit log; for who can get in, **Settings > Organization > People** shows each member's last sign-in and 2FA state.

![The Audit log: the search box, the Action and Actor filters, and one row for each change.](https://brixsignage.com/images/screenshots/audit-log-main.png)

The Audit log: the search box, the Action and Actor filters, and one row for each change.

The log covers every mutating action across the account: screens, playlists, schedules, designs, media, users, roles, billing, emergency takeover, and feature settings. It is scoped to your workspace; nobody outside it can read a row, and a query for another workspace's data returns "not found", not a permissions error that would confirm the other workspace exists.

Access is gated by its own permission (`audit-log.view`), separate from every other permission, so you can grant it to a compliance role that has no access to screens or content at all. Permissions in Brix are not one on/off switch: each of the 25 kinds of thing in the account, screens, playlists, users, billing, the audit log itself, and more, carries its own verbs (such as view, create, edit, delete, approve, publish and export), so a role is any combination you build.

## Scoped to the right place in a multi-location account

A retail or franchise account is a tree of locations, not one flat list. Grant `audit-log.view` at a place in that tree and the rows you see are everything at or below it, not the whole account. A district manager checking their own stores never sees a sibling district's changes, and a corporate-wide reviewer who genuinely needs everything is granted at the root.

## Whether the log can be edited, and how long it is kept

The audit log has no update or delete path in Brix's own code, for anyone, including an Owner or Brix staff acting through support tools. The only way a row gets written is an insert, and the only delete it ever gets is the three-year retention sweep that removes a row once it passes that age. Nothing else issues an update or a delete against it.

That is still a claim about our conduct, not proof. So Brix computes a daily hash chain over the log: each day's checkpoint links to the one before it, so changing any row, on any day, changes every checkpoint after it. In the CMS, open **Settings > Audit log > More audit actions > Check it has not changed** (on a phone, the button is **Verify log**), then **Run the check**. It re-reads every row in the last 90 days of checkpoints and recomputes the hash, so you are not trusting a cached answer. Record a digest yourself and you can check months later whether it still matches, without asking us.

One limit: the check does not cover today until the day ends, so today's rows have no checkpoint yet. Checking the chain needs the audit-log permission on every location in your account, not only a grant at the root: a role scoped to one site, or a root grant that does not reach a nested franchisee workspace, cannot verify the whole chain.

## Exporting the log

Two export paths, for two different readers:

-   **CSV, from the page.** Filter the log to the rows you want, then select **Export CSV**. This is the one for a one-off auditor request or your own records.
-   **A feed, for a SIEM.** `GET /v1/audit/export` returns the same rows as newline-delimited JSON, oldest first with a resume cursor, built for a collector that polls on a schedule rather than a person who reads top-down. It carries the same actor names, targets, and permission scoping as the page.

## FAQ

### Does the audit log cost extra, or need a higher plan?

No. It is on the one Brix plan, with no audit-log tier. It is on by default for a workspace with more than 10 screens, and any workspace can turn it on under **Settings > Organization > Feature defaults**.

### Can a vendor's own staff see or change our audit log?

A partner that manages your account for you, such as a reseller, writes its own actor row for every action they take in your workspace, named by their email and their company, visible in your own audit log like any member's. Our own staff's actions, taken through internal support tools, show in the log too, but as the generic actor "System", not by name. Nothing, for anyone, edits or deletes a row, in the product or through a support tool.

### How is this different from proof of play?

Proof of play is a separate log of what content played on a screen and when; the audit log is who changed the account and its settings. Brix keeps both, and they live under the same **Settings** area. See [proof of play and the audit log](https://brixsignage.com/guides/proof-of-play-and-audit/) for the full feature walkthrough, including how to turn recording on and report on a date range.

Try the audit log for yourself before you put it in a questionnaire: [start a free trial](https://brixsignage.com/start), no card needed.
