> 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/planning/activating-records.md).

# Activating Records

Starting planned work, and choosing where its storage and ELN entries go

**Activating** a planned project, study, or assay marks the point where the work actually begins. Until then, nothing has been set up for it. When you activate it, Lab Atlas:

* creates the record's storage folder,
* creates or links its ELN folders and entries (if your organization uses Benchling or CDD Vault),
* sets its status to **Active**, and
* records today as its start date, if no start date was entered.

Activation can't be undone. An active record can't go back to In Planning.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FTEZH0uechkpqKu2dlWc5%2Fimage.png?alt=media&amp;token=4466eda2-2818-42a9-95c3-0d317edb92af" alt="" width="375"><figcaption><p>Activation information in the planning page for a study with In Planning status.</p></figcaption></figure>

## Before you activate

A record needs a few things in place before it can be activated:

* A **description** — all records.
* A valid **code** — projects.
* An **assay type**, with all required **assay fields** filled in — assays.
* Its **parent must already be active**. You can't activate a study while its project is still being planned. The **Activate** button is disabled until then, and its tooltip tells you which record to activate first.
* The record must **not be locked**.

If something is missing, the details panel shows a warning such as *"2 fields needed before activation"*. Clicking **Activate** lists each missing field, with a link to fill it in.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FcoXJ8kLgAtW7wONepQmx%2Fimage.png?alt=media&amp;token=12c5dcae-15a3-4d4f-ba47-98a0af3b1d38" alt="" width="375"><figcaption><p>Planning page notification of missing fields required for activation.</p></figcaption></figure>

## Activation settings

Records in Draft or In Planning have an **Activation settings** section in their details panel and edit form. Here you choose where the record's resources will be created when it's activated. Nothing is created until then, so you can change these settings as often as you like.

{% tabs %}
{% tab title="Projects" %}
**Storage.** Where the project's folder will go. If you leave this blank, the organization's default storage location is used. Click **Change** to pick another location, or to use an existing folder instead of creating a new one.

**ELN.** Link the project to an existing Benchling folder or CDD Vault project. This option only appears if your organization has the integration connected.
{% endtab %}

{% tab title="Studies and assays" %}
**Storage.** A study's folder is always created inside its project's folder, and an assay's inside its study's. This is shown in the settings but can't be changed.

**ELN.** Choose whether to create a new Benchling folder and entry (blank, or from a template) and/or a CDD Vault entry. Change this in the record's edit form. If you don't choose anything, the record gets an entry on each ELN platform its parent is linked to.
{% endtab %}
{% endtabs %}

Storage folders and ELN entries can't be attached by hand to a record that hasn't been activated. Use the activation settings instead.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FNNG7cgXoA9w6hjIkrLvJ%2Fimage.png?alt=media&amp;token=e94bf566-7b15-443f-84ea-8e15e44ddb9c" alt="" width="563"><figcaption></figcaption></figure>

## Activating a single record

Click **Activate** in the details panel, or on the record's status button on its own page. A confirmation explains exactly what will be created. For example, for a project:

> **Activate PRJ? This can't be undone.** A new folder will be created in Lab Atlas Cloud.

For a study or assay, it explains that the folder will be created inside its parent's folder and lists any ELN entries that will be created.

When you edit an In Planning record using the full form, you can also click **Save and activate**.

## Activating a branch

When a project or study has planned children, the details panel also offers **Activate branch**. This activates the record and every planned study and assay beneath it, starting with parents, in one go.

* **Your own drafts** in the branch are included. They're given codes and become visible to the team, and the confirmation lists them first.
* **Other people's drafts**, and everything beneath them, are left alone.

Lab Atlas checks the whole branch **before** activating anything. If any record isn't ready (missing a description, locked, and so on), nothing is activated, and you'll see a list of the records that need attention, each linking to its details. If the top record is ready by itself, you can choose **Activate just this record** instead.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FjImK5hZftq4HZQo6GWg5%2Fimage.png?alt=media&amp;token=317286df-f1f0-4b48-8b60-6568ac35b375" alt="" width="375"><figcaption><p>Planning page controls for activating a record or whole branch</p></figcaption></figure>

When the branch runs, the confirmation reports progress, for example *"Activated 7 of 8"*.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FYb7UX13dvxGuCr9PX4da%2Fimage.png?alt=media&amp;token=e6200097-4335-44cc-b5d4-e75724286c89" alt="" width="375"><figcaption><p>Confirmation dialog.</p></figcaption></figure>

## When activation fails

Activation can fail partway: for example, if a storage or ELN integration is unavailable. When it does:

* The record's status changes to **Initialization Failed**. It keeps its code.
* Anything beneath it stays In Planning, and the rest of the branch carries on.
* Any resources that were already created are kept, so they won't be created twice.

Click **Retry** to run the activation checks again and pick up where it left off. If the branch was being activated, retrying also continues down that record's children.

Before retrying, you can still change any activation setting whose resource hasn't been created yet. The settings section says *"Change any setting that hasn't been created yet, then retry Activation"*, and marks resources that already exist as *"Linked before Activation failed. Retry skips it."*

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FDz2BPAheDqUnYtXJiuKs%2Fimage.png?alt=media&amp;token=e730aff8-a262-4ea8-a105-a7e19d870a17" alt="" width="563"><figcaption></figcaption></figure>

## For administrators

Activation creates real resources in your organization's integrations, so it relies on them being set up correctly:

* **Default storage location.** Projects that don't choose a storage location use the organization's default. See [File Storage](https://docs.labatlas.com/managing-your-organization/storage-folders.md).
* **Storage integrations.** If a project has chosen a storage drive whose integration is disabled or failing a health check, activation is refused with: *"The chosen storage drive's integration can't be used right now. Fix it in Settings or change the storage setting."* Fix the integration, or change the project's storage setting.
* **ELN integrations.** ELN options appear in activation settings only when Benchling or CDD Vault is connected. See [Benchling](https://docs.labatlas.com/integrations/benchling.md) and [CDD Vault](https://docs.labatlas.com/integrations/cdd-vault.md).
* **Who can activate.** Anyone who can contribute to a project can activate its studies and assays. Activating a project itself requires the Super User role or above.

Activations, and activations that fail, appear in the **Planning** group on the [Activity](https://docs.labatlas.com/using-lab-atlas/activity.md) page, so you can see when work started and spot failures quickly.
