# Projects

## **Overview**

Projects help you organize and manage your pipelines while controlling who can access them.

You can assign users and groups to each project through the **Projects** page. Additionally, you can restrict access to **Accounts** and **Globals** by project — in their respective pages, specify which projects are allowed to use these resources.

This structure ensures proper governance and clear separation across integrations.

## **Before you start**

To manage projects, you need the [**Project Manager**](https://docs.digibee.com/documentation/developer-guide/platform-administration/administration/new-access-control/access-control-roles) permission. Learn more in the [**Roles documentation**](https://docs.digibee.com/documentation/developer-guide/platform-administration/administration/new-access-control/access-control-roles).

## **Project management**

### **Creating a project**

1. Go to the **Build** page, in the **Pipeline** tab, and click **Create**.
2. Select **Project**.
3. In the configuration form, fill in the following fields:
   * **Name:** Name of the project.
   * **Description:** Description of the project.
   * **Project assignment:** Enable **Select all users** to assign all current and future users of your realm or define:
     * **Assigned groups:** Groups of users to be assigned.
     * **Assigned users:** Individual users to be assigned.
4. Click **Save**.

<figure><img src="https://866970526-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjvO5S91EQURCEhbZOuuZ%2Fuploads%2FI5ginwfTqL2WFMlW2Icv%2Fcreate-project.gif?alt=media&#x26;token=7ba1bca4-979a-4ca7-b4cf-9bfd5d4ead92" alt=""><figcaption></figcaption></figure>

After creating the project, you can start [building pipelines inside it](https://docs.digibee.com/documentation/developer-guide/development-cycle/build-overview/pipelines/how-to-create-a-pipeline). Pipelines are automatically linked to the project where they’re created. The **Default** project is always available if you prefer not to create a custom one.

### **Editing a project**

Hover over the project name in the left sidebar and click the **three-dot icon** to open the menu:

* **Edit:** Open the configuration form to update project details.

{% hint style="warning" %}
For [audit](https://docs.digibee.com/documentation/developer-guide/platform-administration/administration/audit) reasons, the project name cannot be changed. If you need to rename a project, create a new one with the desired name and migrate the pipelines.
{% endhint %}

* **Archive:** Archive the project. Only empty projects can be archived. To unarchive a project, contact your CSM.

You can also create folders from this same menu — see [Creating a folder](#creating-a-folder) for more information.

### **Moving pipelines between projects**

To move a pipeline to another project or folder, drag and drop its card to the desired location.

#### **Globals and Accounts permanently removed after moving**

Before moving a pipeline to another project, ensure that all **Globals** and **Accounts** used by the pipeline are allowed in the destination project. Update the permissions in the [**Globals**](https://docs.digibee.com/documentation/developer-guide/platform-administration/settings/globals#creating-a-global) and [**Accounts**](https://docs.digibee.com/documentation/developer-guide/platform-administration/settings/accounts#creating-an-account) pages if needed.

If you move the pipeline without updating these permissions, a warning will list the **Globals** or **Accounts** that are not allowed and will be **permanently removed** from the pipeline. You can either proceed with the move or cancel it to update the permissions first.

Once removed, **Globals and Accounts are not restored automatically**. Moving the pipeline back or allowing the project again doesn't revert the removal. You must manually add them to the pipeline.

{% hint style="warning" %}
As of the January 14, 2026 release, pipelines that contain **Globals** or **Accounts** not allowed in their current project will continue to work only until they are saved again.
{% endhint %}

## **Folders management**

Folders help you organize your pipelines within a project.

### **Creating a folder**

1. Open the desired project and click **Create new**.
2. Select **Project folder**.

{% hint style="info" %}
You can also hover over the project name in the left sidebar, click the **three-dot icon**, and select **Create new folder**.
{% endhint %}

3. Enter the folder name. The name of the folder must be unique for the project. The same name can be used in different projects.
4. Click **Save**.

<figure><img src="https://866970526-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjvO5S91EQURCEhbZOuuZ%2Fuploads%2FqmQFcuYRmLREfL4fAV2W%2Fcreate-folder.gif?alt=media&#x26;token=554ba3c8-093d-4330-9291-2ef07aefdf77" alt=""><figcaption></figcaption></figure>

### **Editing a folder**

Hover over the folder name in the left sidebar and click the **three-dot icon** to access the following options:

* **Edit:** Change the folder name.
* **Archive:** Archive the folder. Only empty folders can be archived.

### Folder and pipeline organization rules

You can organize pipelines and folders in the following ways:

* **Move pipelines freely:** Drag and drop pipelines between folders, between projects, from a folder to the project root, or from the root into a folder.
* **Navigate from the project root:** When you click the project root, you see all folders (if any) and any pipelines that are not inside a folder.
* **Use the left-side menu:** Clicking the project root also expands the left-side menu, showing all folders and the **All pipelines** option. Selecting **All pipelines** displays every pipeline in the project.

<figure><img src="https://866970526-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjvO5S91EQURCEhbZOuuZ%2Fuploads%2FNYR5Gc8OZ72dnQmmN3A5%2Fmove-pipelines.gif?alt=media&#x26;token=33081f86-39df-459a-b6b9-c616ed7a3b80" alt=""><figcaption></figcaption></figure>
