Skip to main content

View the Audit Log

Goal​

Browse the change-audit log for an environment and narrow it down to the entity, record, or kind of actor you are investigating.

Prerequisites​

  • You are signed in to the Admin Control Center with a maker or platform administrator role.
  • The environment exists and has at least one audited entity (see Enable Auditing on an Entity).

Steps​

  1. In the Admin Control Center, open Audit Log.
  2. Check the environment in the top bar: the log is that environment's. Switch it there to read another environment's history.
  3. (Optional) Narrow the results:
    • Table — pick one table from the list. Only tables with auditing on are offered, because the others have no history to find; search by display name or logical name.
    • Record id — follow the full history of a single record.
    • Actor type — show only changes made by a particular kind of actor, such as a person, an external application, or an automated process.
  4. Select Query. The matching changes are listed newest first, each showing when the change happened, the entity and record, the operation (create, update, or delete), the actor and — when the change was automated — the specific business rule or process that made it, and the fields that changed.

What happens behind the scenes​

The audit log for each environment is kept separately from every other environment's, so browsing one environment's history never mixes in another's. Each entry records who or what made the change and, when a person originally started an action that a rule or process later carried out, both facts are kept. Older entries are removed automatically once they pass the environment's retention period, so the log does not grow without bound.

Reading a change a business process made​

A change made by a running process names the run as its actor, with the run's identifier beside it, so you can go and open that run's own history. Where the change was caused by somebody's decision, the agent column names the task they decided at as well. A process makes both kinds of change — some by itself as it advances, and some the instant a person presses an outcome on a task — and this is how you tell one from the other.

Troubleshooting​

  • No entries appear. Confirm the chosen environment has an audited entity and that records have changed since auditing was enabled. Enabling auditing does not backfill changes made before it was turned on.
  • "The 'from' date must not be after the 'to' date." The date range is reversed; set a start date that is on or before the end date.
  • A change shows no actor. The change reached the data outside the platform's normal write path — a useful signal that something bypassed the expected route.
  • Enable auditing on an entity.
  • Create an environment.