All docs pages (49)
Config Monitor
See who changed what in Setup: the latest 1,000 Setup Audit Trail entries, with search, section and user filters, change counts, and CSV export.
Updated 2026-11-09
Config Monitor answers "who changed what in Setup, and when?" It reads the org's Setup Audit Trail and shows the most recent changes in one searchable table. Open Metadata → Config Monitor. The page heading is Config Change Monitor.
How to use it
- Open the page. It loads the audit trail for the org you are connected to straight away.
- Type in Search changes… to find a word in the change text, the action name or the section.
- Narrow by area with All sections, or by person with All users.
- Click a column header (When, Who, Section) to sort.
- Click Export CSV to download the rows that match your filters.
- Click Refresh to read the audit trail again.
What you see
Counts at the top, worked out from the entries that were loaded:
- Total changes: how many entries were loaded (at most 1,000).
- Last 24h and Last 7 days: how many of them fall in those windows.
- Busiest area: the Setup section with the most entries.
- Most active: the user with the most entries.
The table has four columns:
- When: the date and time, in your browser's local time. Newest first by default.
- Who: the user who made the change. If Salesforce returns no name, it shows (unknown).
- Section: the Setup area Salesforce recorded for the change, or (none).
- Change: the description Salesforce recorded for the change. If there is none, the action name is shown instead, or (no details) if both are empty.
A line above the table reads, for example, 25 of 1000 changes, so you can see how many rows your filters keep.
If the org has no entries, or your user can't read them, the page shows No audit-trail entries.
The CSV is named config-changes.csv and has the columns Date, User, Section, Action and Detail. Dates are written as Salesforce returned them. Cells that start like a spreadsheet formula are made safe before they are written.
What it reads and writes
It runs one SOQL query on the SetupAuditTrail object, reading Action, Section, Display, CreatedDate and the creator's name, newest first, limited to 1,000 rows.
It changes nothing in the org and stores nothing: the list is kept only while the page is open.
Limits
- 1,000 entries at most. Only the newest 1,000 are read. If your org made more changes than that in the period you care about, older ones are not shown, and the counts (including Last 7 days) only cover what was loaded. The page subtitle notes that Salesforce keeps about 180 days of entries.
- Setup changes only. Setup Audit Trail records changes made in Setup, not changes to record data.
- Search covers the change text, action and section, not the user name. Use All users to filter by person.
- No alerts and no schedule. It shows the trail when you open or refresh the page; it does not watch the org in the background or notify you.
- No diff. It shows Salesforce's one-line description of each change, not the before and after values of the metadata.
- If you need the changes made just before a specific failure, ranked by what to check first, use Investigate, which reads the same audit trail for a chosen time window.