> 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/using-lab-atlas/locking-records.md).

# Locking Records

Freezing a project, study, or assay so its record can't be changed

Locking a project, study, or assay stops anyone from changing what Lab Atlas records about it until it is unlocked. Use a lock when a record needs to stay exactly as it is. For example:

* a study is finished and its results have been signed off
* a project is under review or audit
* a plan has been agreed and shouldn't drift

**A lock covers everything beneath the record.** Lock a project and all of its studies and assays are locked too. Lock a study and all of its assays are locked.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FmyWVF7TTRaGbwZg6vs0k%2Fimage.png?alt=media&amp;token=41d4ba59-49ee-40e1-bb86-650ed0aef55b" alt=""><figcaption></figcaption></figure>

## Locking and unlocking

Open the record's page and choose **Lock** from the **Actions** menu. On the [Planning](https://docs.labatlas.com/using-lab-atlas/planning.md) page, **Lock** is in the **⋮** menu of the record's details panel.

To unlock, choose **Unlock** from the same menu. The banner at the top of a locked record's **Overview** tab also has an **Unlock** option.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FaEFNF5mkelcGt6slquek%2Fimage.png?alt=media&amp;token=432c5c53-22b1-4d25-8fc2-253bbeadcef4" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}
A lock can only be removed from the record it was set on. If a study is locked because its project is locked, unlock the project. If a study was also locked separately, it stays locked after the project is unlocked.
{% endhint %}

Drafts can't be locked.

## Recognizing a locked record

A locked record shows:

* a lock icon and **Locked by** the locked record's code in the page header, and next to the record on the Planning page
* a banner at the top of the **Overview** tab, which reads either:
  * **This record is locked**, if the lock was set on this record, or
  * **This record is locked by** the project, study, or assay that holds the lock, if it inherited the lock
* disabled buttons and menu items, with a tooltip saying which record holds the lock

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2Fcp04lXtr2bPpFcHYw0dm%2Fimage.png?alt=media&amp;token=19dd4261-e58d-4c65-b484-8444411d24f5" alt=""><figcaption><p>An assay that has been locked by it's parent study.</p></figcaption></figure>

## What a lock prevents

While a record is locked, nobody can:

* edit its fields, description, or dates
* change its status, or [activate](https://docs.labatlas.com/using-lab-atlas/planning/activating-records.md) it
* change its owner or members, or invite people to a locked project
* add, edit, or complete its [tasks](https://docs.labatlas.com/using-lab-atlas/tasks.md)
* add or edit its notes
* attach or change its storage folders, ELN entries, Git repositories, external links, collaborators, or keywords
* add new studies or assays beneath it
* move it to another project or study
* delete it

The same rules apply to changes made through the [REST API](https://docs.labatlas.com/developer-tools/rest-api-reference.md) and the [MCP server](https://docs.labatlas.com/developer-tools/mcp-server.md), so a script or AI assistant can't get round a lock.

## What still works

Some actions don't change the record itself, so they're still allowed:

* **Files.** You can still upload, rename, and delete files in the record's storage folders. Files live in your storage service, which people can often reach directly, so Lab Atlas doesn't try to freeze them.
* **Archiving and restoring.** Archiving retires a record rather than editing it, so a locked record can still be archived and later restored.
* **Things that refer to the record.** You can still add a locked study to a study collection or change team membership.

## Who can lock

| Record                 | Who can lock and unlock                                                          |
| ---------------------- | -------------------------------------------------------------------------------- |
| **Study** or **Assay** | The record's owner, or an Organization Admin.                                    |
| **Project**            | The project's owner if they are a Super User or above, or an Organization Admin. |

Every lock and unlock is recorded as a Governance event. It appears in the record's **Activity** tab and on the [Activity](https://docs.labatlas.com/using-lab-atlas/activity.md) page, as well as in the organization's [Audit Log](https://docs.labatlas.com/managing-your-organization/audit-log.md).

## For administrators

* Organization Admins can lock and unlock any record, whoever owns it. Use this when the owner has left or is unavailable.
* To permanently delete a locked record, unlock it first. Archiving doesn't require unlocking.
* Locks are separate from project visibility. A lock controls whether a record can change. Visibility controls who can see it.
