The audit log

Some actions change what other people can do: a role granted, a member removed, a website approved. Those are written to a log that nobody can edit afterwards.

Where it is

Audit Logs appears in the sidebar for super admins. Ordinary admins and other roles do not see it, and opening the address directly tells them the page belongs to a different account type.

What it holds

Immutable audit log events, searchable by action, actor or summary.

Each entry records what was done, who did it and when. The kinds of thing that land here are the ones with consequences for access and ownership:

• Role changes, and members being added, deactivated or removed
• Super admin transfers
• Website settings and verification changes
• Superadmin approvals of a website, which carry the reason the person typed

Ordinary work does not land here. Publishing an article, accepting a swap or running an audit are recorded in their own modules, where they are more useful.

Why it cannot be edited

The point of a log like this is that it is worth trusting six months later, when somebody asks who removed an account or when a role changed. A log that can be tidied up answers that question with whatever the last person to edit it wanted it to say.

So entries are written and never modified. There is no delete, and no bulk clear.

The platform log

Rankbench also keeps a platform-wide log covering every workspace, including every time a platform superadmin looked inside one. That one is only visible to platform superadmins and is not part of your workspace.

Where to go next

For the controls that generate most of these entries, read people and roles.