Approvals audit log

Owner: Mira Holm · Epic: ENG-1510 · Shipped: Thursday 13 August · Shaped in Emargen as "Approvals audit log"

Why

Customers' auditors ask who approved each person's access, and when. Northgate asks every quarter; every security questionnaire asks too. Decisions were kept on the request, but there was no log a customer could read or export.

What we built

• Every decision on an access request: who decided, when, approve or decline, the request's reason, and the role they decided under. Requests closed after 14 days are logged too, as closed by the system.
• Changes to access and settings: roles given and taken away, depots, single sign-on settings, administrators added or removed. Who, what and when.
• At launch, past decisions were brought in from each request's history (from January 2025) and marked "from request history": who decided, when, approve or decline, and the reason from 29 July. The first night's 400-day run trimmed them to decisions from 9 July 2025.
• Kept for 400 days (about 13 months), the same for every customer.
• Administrators read and filter it in the portal: Settings › Audit log.
• Export a date range as CSV, or take a daily export file. There is no live stream.

What we left out

• Sign-ins. They are in the portal's sign-in log, which is separate.
• Retention per customer. Every customer gets 400 days.
• Sending the log to a customer's own systems as it happens.

Since

• 1 October: approvals by depot managers are logged the same way as administrators', with the depot the approver covers (ACM-247).