# Programs

Before any studies can be added to Study Tracker, you must first add at least one [Program](/documentation/key-concepts.md#programs). Programs are defined as the top-level unit of work in your organization, under which you can register as many studies and assays as you like. 

## Creating a new Program

You can manage programs from the 'Programs' tab of the Admin Dashboard. Click the 'New Program' button on this page to enter the program creation form. Most of the fields on this form are important and required, so take a moment to consider them:

<figure><img src="/files/KB25g4AtOZrETewud4Dz" alt=""><figcaption><p>The program form</p></figcaption></figure>

* **Name**: Your program must have a unique name. It should not be too long, but should be clear in its definition.
* **Code**: This should be a short alphanumeric string, preferably upper-case. It will be used as a prefix for generating [study and assay codes](/documentation/key-concepts.md#study-codes).&#x20;
* **Description**: Provide a brief description for your program, explaining its purpose and goal.
* **Active**: Unless this is a legacy program no longer in use, this value should be set to 'Active'.

### Adding an Electronic Laboratory Notebook (ELN)

If you have configured integration with an ELN (such as [Benchling](/documentation/integrations/benchling.md)), you can connect your program to an existing project in the application. Choose the project you would like to link your program to from the 'ELN Project' dropdown and all of the required fields will be populated from the ELN platform. It is possible to use the same ELN project for multiple Study Tracker programs.

<figure><img src="/files/p2rN2xwd3XyFrZmXIxab" alt=""><figcaption><p>ELN Project selection</p></figcaption></figure>

{% hint style="info" %}
Be sure to create your ELN projects ***before*** adding programs to Study Tracker. Benchling does not support remote creation of projects through their API. It is also important to make sure that the API account Study Tracker is using to communicate with the ELN has write access to requested projects.
{% endhint %}

### Adding File Storage

All programs require a [file storage location](/documentation/managing-your-tenant/storage-folders.md) to create their folder hierarchy for child studies and assays. Select a [root folder](/documentation/managing-your-tenant/storage-folders.md#adding-root-folders) from the 'Parent Folder' dropdown to use. A new folder named after your program will be created within this root folder and will be used as the default file storage location for all studies and assays created within it.

<figure><img src="/files/PWXviwoz35uRdJG2wU86" alt=""><figcaption><p>File storage location selection</p></figcaption></figure>

### Adding Git Repository Group

You can optionally also create a group in any integrated Git server (eg. [GitLab](/documentation/integrations/gitlab.md)) to store Git repositories created for studies and assays within your program. Select the root Git Project Group from the dropdown and a subgroup for your program will be created within it.&#x20;

<figure><img src="/files/NukNdat0Os4TOrqnopDI" alt=""><figcaption><p>Git group selection</p></figcaption></figure>

## The Program Details Page

After successful creation of your new project, you will be redirected to the Program Details page. From here, you can modify your program, browse all associated studies, and view all activity in the timeline. Links are also provided to the newly-created folders in your file storage and ELN systems.

<figure><img src="/files/Fnn6F07vQ5kbeTDplOS1" alt=""><figcaption><p>The program details page</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://study-tracker.gitbook.io/documentation/managing-your-tenant/programs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.