> For the complete documentation index, see [llms.txt](https://docs.labatlas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.labatlas.com/managing-your-organization/audit-log.md).

# Audit Log

The Audit Log is a single, org-wide trail of the changes that affect who can see and do what in Lab Atlas. Where a project, study, or assay timeline answers "what work happened on this record?", the Audit Log answers "who was given access to what, and when?".

You will find it under **Settings → Organization → Audit log**. It is available to Super Users and above.

## How activity is classified

Every event Lab Atlas records falls into one of three categories, and the category determines where you see it.

| Category           | What it covers                                                                                                               | Where it appears                       |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------- | -------------------------------------- |
| **Research**       | The day-to-day work on a record — creating and updating studies and assays, adding notes, completing tasks.                  | Record timelines only                  |
| **Governance**     | Access and visibility changes scoped to a single record — adding someone to a project team, changing a project's visibility. | Record timelines **and** the Audit Log |
| **Administrative** | Organization-level changes — inviting or removing users, changing roles, connecting or disconnecting integrations.           | The Audit Log only                     |

The effect is that a record's timeline stays readable as a history of the science, while everything with a governance or compliance dimension is also collected in one place an admin can review.

## Reading the log

Entries are listed newest first and paged twenty at a time. Each one records what happened, which record or user it affected, who performed it, and when.

Some of the things you will find here:

* Users invited, joining, being removed, or having their role changed
* Members and teams added to or removed from a project
* A project's visibility changing between Public, Protected, and Private
* Integrations being connected, disconnected, disabled by a failed health check, or re-enabled
* Tasks being assigned, or moving between statuses

{% hint style="info" %}
API and MCP traffic is recorded the same way as work done in the web interface. A key acts as the person who created it, so activity performed by a script or an AI assistant is attributed to that user and shows up here alongside everything else.
{% endhint %}