Audit Activity Page

The Audit Activity page (/audit) shows a chronological, filterable log of every meaningful action across reviews you can see. It is the workspace-wide companion to the per-review audit trail described in the 21 CFR Part 11 Audit Trail article.

Who can see what

• Owners and Admins — see every audit entry across the workspace.
• Reviewers — see audit entries scoped to reviews they own or are assigned to.
• Auditors — see audit entries scoped to reviews they have been granted.

Scope enforcement is automatic. You will never see an entry from a review you don't have access to.

Filters

Across the top of the page:

• Action — narrow to a specific action type (e.g. create, update, lock, unlock, export).
• Entity — narrow to a target type (e.g. review, paper, extraction, team-membership).
• User — narrow to one actor.
• Date range — last 24 hours, last 7 days, last 30 days, last 90 days, all time.

Filters compose: user = Alice, entity = extraction, last 7 days gives you exactly Alice's extraction work in the last week.

What each row shows

Each entry includes:

• Timestamp (relative + exact on hover)
• Actor (name, role, organization)
• Action (verb)
• Target (entity type + entity id, with a link to the relevant review or paper)
• Optional change summary (before/after for fields that changed)
• IP address and user-agent badge (privacy-respecting hash, full value visible to Owners only)

Common workflows

• "Who froze the protocol on review X?" — filter by review = X, action = lock. The single resulting row tells you who, when, and from which device.
• "What has Alice done this week?" — filter by user = Alice, last 7 days. Sort by timestamp.
• "Show me everything that touched extraction in the last month" — filter by entity = extraction, last 30 days.
• "Export today's activity" — filter by last 24 hours, then click Export CSV in the top-right.

What this page is not

• It is not the full per-review audit trail. The per-review trail (downloaded from the SLR hub) ships with hash-chain integrity verification, signature envelopes, and the full before/after payloads. The Audit Activity page is the discoverable, browsable view; the downloaded JSON is the cryptographically verifiable view.
• It is not a security incident log. Sign-in attempts, password resets, and integration tokens live under Settings → Security, not here.
• It is not a notification feed. The bell shows things that happened to you; this page shows things that happened anywhere you can see.

Best practices

• Bookmark a filter. If you check the same view weekly (e.g. "everything on review X this week"), bookmark the URL — the filters are encoded in the query string.
• Export before milestones. Run a CSV export at every milestone (protocol freeze, screening close, manuscript submission). Attach it to your trial master file or dossier alongside the per-review audit JSON.
• Use it for handoffs. When a teammate joins a review mid-flight, an Audit Activity filter on that review is the fastest way for them to catch up on what has happened.