The audit log records who did what in Dashbuilder, with before and after values for every change, so admins can always see who accessed or changed member data. Admins open it at Settings › Audit log: click your name in the bottom-left user menu, choose Settings, then the Audit log tab. Officers don't have this tab.
What's recorded
Every change (create, update, delete, restore) to users, audiences, dashboards, blocks, metrics, trackers, saved views and campaigns, with the before and after values, the time, IP address, browser and page. Passwords and two-factor secrets are never recorded.
Named events on top of that:
Area | Events |
|---|---|
Sign-in and access | Every sign-in; access updated; invite resent |
Data | Data uploaded; audience membership uploaded; refresh requested |
Personal data | Exported (any CSV download, with level and row count); Contacts accessed (someone opened a member-level table) |
Dashboards | Blocks reordered; visibility changes |
Trackers | Published, archived; links issued, revoked, reissued; link probes (someone tried a dead or fake link); Results and Responses exports |
Campaigns | Went live, published, closed, duplicated; files added, downloaded, removed |
Assistant | Assistant connected or disconnected; everything done through it is tagged |
Step 1: Open the log
Settings › Audit log. The newest events are at the top. Each row shows who, what, when and on which item; open a row for the before and after details.
Step 2: Filter to what you need
Filter | Use it to |
|---|---|
Who | See everything one person did |
Subject type | Narrow to users, dashboards, audiences, trackers, campaigns and so on |
Action | Pick an event such as Exported or Contacts accessed |
Through an assistant | Show only what Claude or ChatGPT did (also linked from the bottom of Settings › Assistants) |
Date range | Limit to a period |
Clear the filters to return to the full list.
Common questions and how to answer them
Question | Filters |
|---|---|
Who downloaded member data last month? | Action Exported + date range. The row shows the level and number of rows |
Who has looked at members' contact details? | Action Contacts accessed |
Who changed this person's access? | Subject type User, then open the row to see roles and scope before and after |
What did a particular admin change today? | Who = that admin + today's date |
What has the AI assistant done? | Tick Through an assistant |
When did this dashboard go public, and who widened it? | Subject type Dashboard; look for the status or visibility change |
Who uploaded the membership file? | Action Data uploaded |
Is someone trying old tracker links? | Action link probe |
Security alerts: the log's early warning
You don't have to watch the log. Admins get a security alert in Notifications, and by email unless your workspace has turned emails off, when any of these happen:
- A user is created, removed or restored, or their access changes (including being made admin)
- Two-factor is turned off on a non-enforced workspace
- Data is uploaded
- Member-level data is exported
- A dashboard's visibility is widened
- An admin is locked out after failed sign-ins
- An assistant connects for the first time, or drafts a dashboard
Open an alert, then use the audit log to see the detail.
Troubleshooting
Problem | Why | Fix |
|---|---|---|
No Audit log tab | Only admins have it | Ask an admin |
Can't find an event | Filters too narrow, or the wrong date range | Clear filters, widen the date range, then filter one thing at a time |
Assistant actions mixed in with yours | They're done as you | Tick Through an assistant to separate them |
Not receiving security alert emails | Emails are turned off for your workspace, or caught by spam | Check Notifications in the app; check spam; ask Lluminate whether emails are on |
Need a copy for an investigation | No export button in the log | Note the filters and take screenshots; ask Lluminate support if you need more |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article