# Audit Log: See Who Did What (Beta)

> A new team audit log records key actions across your workspace so you can review activity. Now in beta.

Beta · 26 June 2026

## What changed

The Team section now includes an **audit log** — a dated record of significant actions taken across your workspace. It is available now in beta. It gives workspace owners and admins a clear answer to the question of who did what and when, without needing to reconstruct activity from memory or ask the relevant team member directly.

Actions currently logged include member changes such as invitations sent, roles updated, and seats removed; matter-level actions such as matters being created, archived, or deleted; and billing-relevant events such as credit top-ups and plan changes. Each entry records the team member who took the action, what they did in plain language, and the date and time it happened. The most recent activity appears at the top of the list, so the latest changes are easy to find without scrolling.

## How to use it

1. Open **Settings**, then navigate to **Team**, then **Audit log**.
2. The log displays recent activity across the workspace in reverse chronological order.
3. Use it to investigate specific changes: confirm who archived a matter, check when a team member's role was updated, or review recent billing events.
4. Scroll through the entries to find the activity you are looking for.

The log is read-only. Entries cannot be edited or deleted, which is intentional: the value of an audit trail depends on it being a complete and unaltered record.

## Why it matters

As a chamber or legal team grows and more people share a workspace, it becomes important to know who made a given change and when. If a matter is unexpectedly archived, if a team member's access level is modified, or if a billing event does not appear where expected, an audit trail is the fastest way to understand what happened. Without one, reconstructing activity from conversations or memory is slow and unreliable, and the answer may not even be recoverable.

The audit log provides that trail without requiring any change to how your team works. Actions are recorded automatically as they happen. No one needs to log a change manually, and owners do not need to be present for every action to have a record of it after the fact.

For chambers handling sensitive client matters, having a clear record of workspace activity is also simply good practice. Knowing that a log exists tends to make everyone more deliberate about consequential actions — archiving a matter, removing a member, changing access levels — which benefits the team as a whole.

## Good to know

- The audit log is in **beta**. The set of recorded actions and the way they are presented may change as we learn how teams use it and what they find most useful. Feedback on which actions you most want to see captured is welcome.
- The log is visible to **owners and admins** only. Other team members do not have access to it.
- The log records the fact that an action occurred — who took it and when — not the content of anyone's research, drafts, or case notes. Client work is not exposed.
- Because this is a beta, the range of logged actions is still expanding. Actions not yet captured will be added in coming releases, prioritised by what teams identify as most important to track.
- To share feedback on the audit log, use the feedback option in Settings. We are actively shaping the final scope based on how teams are using it during the beta period.

https://niyam.ai/changelog/audit-log-beta