> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# Create and manage projects in Studio

> Create and manage projects in Studio

## Create projects

Create a project with either the **New Project** or **Project Builder** flows.

* **New Project** opens a blank project with a starter workflow and takes you to the editor.
* **Project Builder** lets you create or extend a project by adding assets during setup.

![](/_fern-img/34ce3cffdd45fbac3acded9e8505e5dcca57e644762ac625500e568d5369591f.webp)

### Create a new project

Click **New Project** to start an "Untitled Project" that includes a default workflow. The name shows in the left sidebar just like a regular Studio workflow.

![](/_fern-img/cf5a630317220806a5890696b39b17247c5106a5517561c39fb930145dea6a26.webp)

Open **Settings** by clicking the gear icon under the project name to rename it, add a description, or set a thumbnail.

![](/_fern-img/2b5e4f6862d4ff0aa434dd97a2c7fd1a207ea3841126012bc96c1e82fd80e0eb.webp)

Jobs run from a project include the project name in their Operations Manager entry.

![](/_fern-img/3802a59e4f6520bdad12a2ae0a2efb5e613f8670ff30d824d46578a47bc1577d.webp)

### Create a project using Project Builder

Open **Project Builder** from the homepage. Pick an asset tab (workflows, JSON forms, command templates, analytic templates, templates, or transformations).

![](/_fern-img/54e7a115729bbc0a0ffe89b981e26cb822a394ca4e1147527a6675ca67ab900b.webp)

Check the boxes for the assets you want and click **Create New Project**. In the dialog, name the project and choose to copy or move the assets. Click **Continue** to open the new project with the first selected asset visible.

![](/_fern-img/57e26e51de1baab7a3b4556de405b3cb78155654cca54651b554ec7943c57f39.webp)

After adding assets to an existing project, a success notification appears with a link you can click to open the project.

## Add assets to a project

To add assets to a project, hover over the **(+)** button in the Project Builder toolbar.

![](/_fern-img/3423821bf49d6430c0146c19bfb249f789d02764f0f8935581702349b5effae6.webp)

### Add a new asset

Choose **+ Add New Asset** to open a modal that lists available asset types. Select a card and fill out the details (name, description, type, etc.) in the create dialog.

![](/_fern-img/204e2189d37208d7232bc57aa7d05ef6206c36c98afa3ca4ec40d2174e4eb340.webp)

Asset names are unique within a project. The same name can exist in global space or in other projects but not twice in the same project.

### Add an existing asset

Select **+ Add Existing Asset** to open the view that lets you pick any asset not already in the project or any asset from another project.

![](/_fern-img/7c29451374c659883e91ae3fa4da7d5112f55e881c53eb15017d9b979c2729e9.webp)

Select the checkbox next to each asset you want to add and click **Add To Project**. A dialog prompts you to copy or move the selected assets. All selected assets display under **Selected Assets** on the right.

![](/_fern-img/1edb93f9615c51d07bcf6bd374e8f3e7c45d86759b24228540f2a8ab829152d8.webp)

Moving assets removes them from Studio and makes them inaccessible from the Global View.

## Import and export projects

When importing or exporting, remember that projects only include Studio assets. Use the standalone bundle feature if you need to package non‑Studio items (for example, Operations Manager triggers or infrastructure definitions).

To **import a project**, navigate to the Projects homepage and click the import button. Upload the project by drag and drop, or browse the file system.

![](/_fern-img/30b4459d8ec41bf926ec9be3435e755b39aee16253e7f1b140c472a04e489d75.webp)

To **export a project**, click the export button at the bottom of each project card and save the project to a specified location.

![](/_fern-img/f3e70c6faaeb9597191d1f18653f3190bd3ab5358eb8fd7a2eaf86618d529b07.webp)

## Duplicate projects

To **duplicate a project**, click the duplicate button at the bottom of a project card. The duplicate appears in the project list with **(clone)** appended to the project name.

![](/_fern-img/dcf5e220292e02587923efaec1506994ab203b73ccb86df2cfe4b01afa748264.webp)

## Manage project assets

For any project, you can view asset details and rename assets using the left sidebar. You can also create folders to organize assets.

### Edit details

Hover over any asset in the left sidebar to display the menu button (**⋮**). Select **Edit details** to open a dialog where you can update the project name and description.

![](/_fern-img/aa0c4c17eee9375be772c51460c0a9dda5fb867c907b044533536fa3a2f27516.webp)

### Rename assets

Double-click an asset name in the left sidebar to enable the name field. Type the new name and click the checkmark to save.

![](/_fern-img/c5d1076fc454ab9d35dac5940d55bb846830dd9d93a95f8c5c3f230254efb8e9.webp)

### Asset folders

Assets in the sidebar are distinguished by icons rather than separated by type. You can organize assets into folders two ways:

* Hover over the **(+)** button in the **Project Builder** toolbar and select **+ Add New Folder**.
* Hover over an asset in the left sidebar, click the menu button (**⋮**), and select **+ New Folder From Selected**.

![](/_fern-img/28d6ce827bf7af3c492f7b2ae3479c06b718d22e9b82aafb398becbcfb98659c.webp)

To rename a folder, double-click the folder name, type the new name, and click the checkmark. Additional assets and nested folders can be added under any top-level folder.

![](/_fern-img/9174822c8d3eea385c13b4a0b81a6a5851a1163af078dbb607f11f2c3eae6d36.webp)

### Best practices

* Keep each project focused on a single initiative or related set of assets.
* Do not attach unrelated files merely to move them between environments; this undermines search and organization.
* Use project access controls to manage permissions for a group of assets instead of setting permissions on each asset individually.

## Configure project settings

Click the gear icon in the toolbar beneath a project name to open **Settings**. Use the **Details** tab to configure project information and appearance, and the **Access** tab to manage members.

### Details tab

Six color options are available, or you can upload a custom thumbnail image (330 x 120 px is the optimal size). After entering the project details and selecting a thumbnail, click **Save Settings**. The chosen thumbnail appears for the project on the Projects homepage.

![](/_fern-img/eb819c2f97f9e604cfcbcd7459efb5ca5f6fb42c27afffeedfa31e76428e2745.webp)

### Access tab

Click **Add Members** to open a dialog for adding an individual user or user group to the project. Select the member from the dropdown and set their role as Owner, Editor (default), Operator, or Viewer.

![](/_fern-img/d6dd9e57e97fcd84c757a2cc4d6a725013b0da9d8a246ee6163368735d095a01.webp)

To remove a member, select the member and click **Remove Members**.

![](/_fern-img/b5a3ebb2fe7d133fbb9b88865ec95e8daee36f0de249c3d60a563178c516c984.webp)

### Member roles

Click the radio button for the appropriate role and click **Save Settings** to apply changes.

* **Project Owner**: Full privileges. All projects must have at least one owner.
* **Project Editor**: Same file privileges as owner, but cannot change project members.
* **Project Operator**: May only view and execute files in the project.
* **Project Viewer**: May only view the project.

### Project Admin role

The Project Admin role is an application-level role, separate from the per-project member roles you set in the **Access** tab. The `projectsadmin` role grants it. It provides access to every Studio project system-wide, regardless of an admin's individual project-level permissions, so admins can resolve orphaned or inaccessible projects. For example, after a project owner's account changes or is removed. Itential records all actions taken with this role in the audit log.

An admin assigns

the `projects:admin` role in **Cloud Hub**.

With this role, an admin can:

* Get any Studio project system-wide, regardless of their individual project-level permissions.
* Update Studio project membership to Owner, Editor, Operator, or Viewer for any user, on any Studio project.
* Delete any Studio project system-wide.

The role is exposed through its own API endpoints, separate from the standard Studio Projects API, which are available based on each caller's project-level access:

| Method   | Endpoint                                       | Description                |
| -------- | ---------------------------------------------- | -------------------------- |
| `GET`    | `/automation-studio/admin/projects`            | Get all Studio projects.   |
| `GET`    | `/automation-studio/admin/projects/:projectId` | Get a specific project.    |
| `PATCH`  | `/automation-studio/admin/projects/:projectId` | Update project membership. |
| `DELETE` | `/automation-studio/admin/projects/:id`        | Delete a project.          |

These endpoints bypass project-level role access and are available only through the `/automation-studio/admin/projects` API.