---
question: Who changed access, and when?
kind: task
via_web: available
via_cli: na
via_python: na
via_api: available
via_config: na
ref_web: Roles & permissions › Audit
ref_api: GET /api/iam/admin/audit
prereq: You are the platform admin, or you hold `nexus:ReadSystem`.
next:
  - /capabilities/platform/test-access-with-the-simulator
  - /capabilities/platform/view-as-another-person
---

# Review the audit log

Every change made on the Roles & permissions pages is recorded before it happens: if the record cannot be written, the change is not made. A record names who acted, the operation, the resource and a short detail, never a key's value or a policy's text. A refused attempt is recorded too.

The log holds:

- IAM changes: policies, attachments, groups and their members, identity provider mappings, service accounts and keys, module approvals;
- the platform's accounts, from Platform Settings › Users: invitations, names, superadmin, deactivation, deletion;
- each view as another person: its start, its stop and each app opened in it (`view_as_start`, `view_as_stop`, `view_as_open_app`).

Role changes made from the Members pages and invitations sent there are recorded by their own routes, not in this log.

## Web UI

### Open Audit

Open the account menu, **Platform Settings**, then **Roles & permissions** under Access, then **Audit**. The newest changes come first, with **When**, **Actor**, **Operation**, **Resource**, **Detail** and **Outcome**.

### Filter

The page loads the 200 newest records. Type part of an operation in **Operation (attach, key…)**, such as `attach` or `view_as`, to keep those records among the 200: the match is on any part of the name, in the browser, so an older record does not show even if it matches. Operations are named after the change: `create_policy`, `attach_policy`, `detach_policy`, `add_group_member`, `create_key`, `rotate_key`, `revoke_key`, `view_as_start`… Type an id in **Resource id (exact)**, such as a person's `usr_…` id or a policy's `pol_…` id, to see what happened to it: this filter is applied by the server first, so it reaches the 200 newest records of that resource. Filter by resource to look further back.

An **Outcome** marked failed is a change that was refused or did not complete.

## CLI

Not applicable. `abi iam` has no audit command. Use the Web UI.

## Python

Not applicable. Use the Web UI.

## REST API

:::warning Session only
The routes under `/api/iam/admin/` take a signed-in session only. A personal API key (`abi_pk_…`) is refused with 403 on `/api/iam/`, so a script that holds one cannot read the log.
:::

```http
GET /api/iam/admin/audit?operation=view_as_start&resource_id=usr_01jexample0000000000000000&limit=100
```

`resource_id` keeps the records of one resource (for a view, the person's id) and `limit` is 1 to 500 (100 by default); together they give the `limit` newest records of that resource. `operation` is applied after the limit and matches the whole name (`view_as_start`, not `view_as`): this call answers the view starts among those 100 records, not the last 100 view starts. An empty answer does not mean nothing happened: raise `limit`, or filter by `resource_id`.

## Config

Not applicable. The audit is always on.
