# Organizing Studio with folders

> Group simulations and coaches into folders, find them with search, filters and sorting, and duplicate, move, transfer or delete them.

- Plans: All plans
- Canonical: https://docs.devlin.ai/get-started/organize-studio-with-folders

Folders group the simulations and coaches in a workspace so a growing library stays easy to scan. This page covers creating and managing folders, moving items into them, finding items with search, filters and sorting, and the actions on each card's menu: duplicate, transfer and delete. Folders are available on all plans.

## Before you start
- Open **Studio**. Folders appear as a row of chips on the **Simulations** and **Coaches** tabs, above the list. The row shows once the workspace has a folder or the tab has at least one item.
- Folders belong to the workspace, not to a tab. The same set of folders shows on both tabs, and a folder can hold simulations and coaches together.
- Every member of the workspace can create, rename and delete its folders. See [Members and roles](https://docs.devlin.ai/workspace-and-team/members-and-roles).
- Folders are flat: a folder cannot contain another folder. An item is in a single folder or in none, which Studio calls **Unfiled**.
- Evaluators are not filed in folders. The **Evaluators** tab has its own list.

## Steps
1. On the **Simulations** or **Coaches** tab, select **Create folder** at the start of the folder row.
2. In the **New folder** dialog, type a name under **Folder name** and select **Create folder**. A name can be up to 60 characters, and spaces at the start and end are removed. Names must be unique in the workspace, ignoring capitalisation; a duplicate is rejected with "A folder with that name already exists".
3. Open the menu on a card and select **Move to folder…**.
4. In the dialog, select the folder. The folder the item is already in is marked **Current** and cannot be selected. Select **Unfiled** to take the item out of its folder.

You can also drag a card onto a folder chip, or onto the **Unfiled** chip, to move it.

## Result
The folder appears as a chip in the folder row, in alphabetical order. Select a folder chip to show only the items in that folder, **Unfiled** to show items that are in no folder, or **All** to show everything. While **All** is selected, each filed card shows the name of its folder.

Moving a simulation to a folder does not record a new entry in its [version history](https://docs.devlin.ai/simulations/version-history).

## Renaming and deleting a folder
Select a folder's chip first. A pencil icon and a trash icon then appear on that chip.

- To rename, select the pencil icon, change the name in the **Rename folder** dialog and select **Rename**. The same naming rules apply as when you create a folder.
- To delete, select the trash icon, then confirm with **Delete folder**. Deleting a folder does not delete what is inside it: the simulations and coaches move back to **Unfiled**. If you were viewing that folder, the list returns to **All**.

## Search, filters and sorting
The search box, filters and view switch appear above the list once the tab has at least one item.

- Search: on the **Simulations** tab, search matches a simulation's name and its character description. On the **Coaches** tab, it matches the coach's title and the coach's name. Matching ignores capitalisation.
- Status: filter by **All statuses**, **Published**, **Draft** or **Archived**.
- Sort: choose **Newest first**, **Oldest first** or **Name A–Z**. Newest and oldest refer to when the item was created.
- View: switch between **List view** and **Tile view**. Your choice is remembered in the browser you are using.

Search, the status filter and the selected folder combine, so the list shows only items that match all of them.

## Actions on a simulation card
The menu on a simulation card has **Edit**, **Duplicate**, **Move to folder…**, **Transfer…** and **Delete**.

### Duplicate
**Duplicate** creates a copy in the same workspace, named after the original with "(Copy)" at the end.

The copy keeps the simulation's content and settings, the folder it was in, and the languages you added to it. The copy never shares the original's voice agent, so editing the copy does not change the original's voice setup. When the original has voice turned on, the copy normally gets its own voice agent straight away. Otherwise it gets one the next time you save its voice settings.

The copy does not keep:
- The publish status. The copy always starts as a draft, so it is never live until you publish it.
- The embed key. The copy gets a new one, so existing embed codes and links still point at the original.
- The [daily spending cap](https://docs.devlin.ai/plans-and-billing/daily-spending-caps).
- The setting that collects a [learner identifier](https://docs.devlin.ai/workspace-and-team/learner-identity), which returns to its default.
- Learner conversations, results and version history. Those stay with the original.
- Links to coaches and evaluators.
- Linked knowledge bases and source materials. Link them again on the copy.

### Transfer to another workspace
**Transfer…** moves a simulation to another workspace you belong to. It appears only when you belong to more than one workspace and you are the owner of the workspace you are in. The server enforces the owner rule and refuses anyone else with "Only owners can transfer simulations out of this workspace". The destination can be any workspace you are an active member of, in any role.

1. Select **Transfer…** on the card's menu.
2. Under **Destination workspace**, select the workspace.
3. Select **Transfer**.

The simulation leaves the current workspace and no longer appears in it. In the destination workspace:
- It arrives **Unfiled**, because folders belong to a workspace.
- Its version history and added languages move with it.
- Its links to coaches and evaluators are removed. The coaches and evaluators themselves stay in the original workspace.
- Its publish status and embed key are not changed by the transfer.
- Its linked knowledge bases and source materials do not come with it, because knowledge belongs to a workspace. Link knowledge again in the destination workspace.

Coaches and evaluators cannot be transferred. For more on workspaces, see [Workspaces](https://docs.devlin.ai/workspace-and-team/workspaces).

### Delete
**Delete** asks you to confirm, then permanently removes the simulation. This cannot be undone.

- The simulation is unpublished first.
- Its learner conversations, evaluation results, version history, added languages, and links to coaches and evaluators are deleted with it.
- Voice sessions that have not been billed yet are settled before the simulation is removed. Credit usage already recorded stays in the workspace's credit history. See [Credits and usage](https://docs.devlin.ai/plans-and-billing/credits-and-usage).
- If the delete cannot finish, the simulation can be left in the **Archived** status instead of being removed.

Export any results you need before you delete. See [Exports](https://docs.devlin.ai/results-and-analytics/exports).

## Actions on a coach card
The menu on a coach card has **Edit**, **Duplicate**, **Move to folder…** and **Delete**.

- **Duplicate** creates a copy in the same workspace, named "Copy of" followed by the original's title. The copy starts as a draft with a new embed key and no daily spending cap. It keeps the coach's content and settings, its folder, and its links to simulations and evaluators. It does not keep linked knowledge bases or source materials. A coach copy never shares the original's voice agent either. Coach conversations and version history are not copied.
- **Delete** asks you to confirm, then permanently removes the coach, its conversations, its version history and its links to simulations and evaluators. This cannot be undone. The coach is unpublished first, unbilled voice sessions are settled before it is removed, and credit usage already recorded stays in the workspace's credit history.

## Evaluators
Each row on the **Evaluators** tab has a single action, **Delete**. After you confirm, the evaluator and all of its results are permanently deleted, along with its links to simulations and coaches. Evaluators have no folders, no duplicate action and no search or filters in this list. See [Evaluators](https://docs.devlin.ai/evaluators/evaluators-scoring-submitted-work).

## Bulk actions
On the **Simulations** and **Coaches** tabs, point at a card to show its checkbox, and select the checkbox on each card you want. The number selected shows next to the tab's heading, with **Clear** to deselect everything.

While cards are selected, the menu on any selected card acts on the whole selection: it can duplicate, move to a folder or delete every selected item, and **Edit** is unavailable. For simulations, owners who belong to more than one workspace can also transfer the selection. Dragging a selected card onto a folder chip moves the whole selection when more than one card is selected.

- A bulk delete asks for a single confirmation and is permanent, the same as deleting each item on its own.
- Each item is processed separately. If some fail, they stay selected so you can retry. For duplicate, move and delete, the message names the first few that failed. For transfer, it says how many were transferred.
- Changing the tab, the folder, the status filter or the search clears the selection, so a bulk action only ever applies to cards you can see.

## AI tools over MCP
An AI tool connected through the [MCP server](https://docs.devlin.ai/integrations/mcp-server-and-ai-tool-connectors) can do part of this:

- Folders: with `manage_folder`, a tool whose token has write access can create a folder or rename one, under the same naming rules, and the change is applied without an in-app approval step because nothing learners see changes. A tool cannot delete a folder; that stays in the app. To move a simulation or coach into a folder, a tool sets the folder when it updates that simulation or coach.
- Archive or delete: with `delete_entity`, a tool can remove a simulation or a coach. By default it archives the item, which takes it offline for learners; it permanently deletes only when the request explicitly asks for that. Either way the tool has to confirm the call explicitly, and it can ask for a preview that changes nothing. If the workspace requires in-app approval, the confirmed call is recorded as a change request for an owner or admin to approve in the app instead of being applied.

## Related
- [Version history, undo and restoring a version](https://docs.devlin.ai/simulations/version-history)
- [Workspaces](https://docs.devlin.ai/workspace-and-team/workspaces)
- [Members and roles](https://docs.devlin.ai/workspace-and-team/members-and-roles)
- [Find your way around](https://docs.devlin.ai/get-started/find-your-way-around)
- [MCP server and AI tool connectors](https://docs.devlin.ai/integrations/mcp-server-and-ai-tool-connectors)