Audit log
A record of who changed what in your organisation: templates, keys, members, queue decisions and billing. Rows are kept for 365 days.
The audit log answers who changed what, and when: a template published, a key revoked, a member's role changed, a queue item decided. Use it to trace a change in how content is handled back to the change in configuration behind it.
It is a page of the dashboard, Settings, Audit log, newest change first. The API has no endpoint for it.
What a row holds
- The action, as a resource and a verb.
templates.publishis shown as "Templates ยท publish". - Who did it: a member by name, an API key, or System for something that happened on its own, such as a failed payment or a suspension that ran out. A change made by the Infrared team carries a Staff badge and always a reason.
- The target: what kind of thing it was, and its id.
- The time.
- Details, where there are any. Open the row to read them as JSON: the scopes of a new key, the version that was published, the role a member was given.
A change made through the API is recorded with the key that made it. Each row also stores the caller's IP address and the request id; the page does not show them. When a member deletes their account, their rows stay and the IP address is removed from them.
What is recorded
| Area | Actions |
|---|---|
| Organisation and projects | organizations.create, organizations.update, projects.create, projects.update, projects.archive |
| Members | invitations.create, invitations.resend, invitations.revoke, invitations.accept, invitations.register, members.update_role, members.remove |
| API keys | api_keys.create, api_keys.revoke |
| Templates | templates.create, templates.update, templates.update_draft, templates.publish, templates.discard_draft, templates.archive, templates.restore, templates.simulate |
| Guidelines and wordlists | guidelines.create, guidelines.update, guidelines.delete, wordlists.create, wordlists.update, wordlists.delete, wordlists.add_terms, wordlists.remove_terms |
| Webhooks | webhooks.create, webhooks.update, webhooks.rotate_secret, webhooks.delete, webhooks.replay |
| Actions | actions.create, actions.update, actions.delete, actions.execute |
| Authors | authors.block, authors.suspend, authors.enable, authors.trust_override |
| Review queue | queue.resolve, queue.reopen, queue.assign, queue.priority |
| Moderations and media | moderations.remoderate, media.reveal_original |
| Billing | billing.checkout, billing.checkout_pack, billing.checkout_confirmed, billing.change_plan, billing.cancel, billing.resume, billing.portal_session, billing.sync, billing.plan_changed, billing.checks_purchased, billing.checks_refunded, billing.payment_failed, billing.payment_disputed, billing.grace_expired |
| The Infrared team | staff.organizations.update, staff.billing.assign_plan, staff.billing.sync, staff.checks.purchase, staff.checks.adjustment, staff.entitlement_overrides.create, staff.entitlement_overrides.delete |
What is not recorded
Creating a moderation, reading anything, a run of the template test console, a note on a queue item, an edit to an author's name or metadata, and signing in.
An existing account joins an invitation at its next sign-in, and that leaves no row of its own: the invitations.create row is the trace. A new account created from the link is recorded as invitations.register.
Find an entry
The page has two views: the current project, and Whole organisation. Billing, changes to organisation members and changes made by the Infrared team name no project, so they appear only in the organisation view.
The filter box takes an action and matches it exactly: templates.publish finds every publish, templates finds nothing. Load older fetches the next 50 rows.
Who can read it
The page opens for Owners and Admins. People who hold only a project role see it keep loading.
How long rows are kept
A row is kept for 365 days, on every plan, and then deleted. There is no export.
Next
- Members and rolesInvite people to the whole organisation or to one project, and choose what each of them can do. Five roles, from Owner to Moderator.
- API keysA key signs every request and decides which project it lands in. Create one for each place that calls Infrared, with only the scopes it needs.
- Data retention and privacyWhat Infrared keeps of a moderation, for how long, and what the nightly purge removes. Set it for a project, a template or a single request.
Something missing or unclear on this page? Write to support@useinfrared.com.