> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/organization-and-workflows/folders.md).

# Folders

Group recordings and bug reports in public or private folders, and pin the ones you use.

Folders group recordings so your team can find them. Each recording section in the sidebar has its own folders:

* **Customers**: recordings your customers send, including video call recordings.
* **Team**: your team's recordings and bug reports.
* **Reusable**: recordings you keep and send again.

{% embed url="<https://app.screendesk.io/recordings/d2abad27-1977-4855-bc99-2a58202e517b>" %}

A recording can only go into a folder of its own section.

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2Fhs1xfgnzD59y5ckUy35W%2Ffolder-page.png?alt=media" alt="A folder with its reports"><figcaption></figcaption></figure>

## Create a folder

Open a section, select the folder switcher in the top bar (it reads **All folders**), then **New folder**. Enter a **Name**, an optional **Description**, choose who can see it under **Access**, and select **Create folder**.

Anyone except Watch only members can create folders. Names must be unique within a section.

## Move recordings into a folder

Select recordings in a list and choose **Move to** in the bar that appears, or use **Move to folder** on a recording's page. Moving something into a folder sets off the [automations](https://docs.screendesk.io/organization-and-workflows/workspace-automations.md) that start when a recording is added to it.

## Folder menu

Open a folder and use the menu next to its name:

* **Edit folder**: rename it or change its description.
* **Manage access**: switch between public and private, and add people.
* **Pin to sidebar**: adds it under **Folders** in the sidebar. Pins are yours only; drag them to reorder.
* **Archive**: hides the folder and keeps what's in it. Restore it from **Archived folders** in the folder switcher.
* **Delete**: deletes the folder **and everything in it**. This can't be undone.

To act on what is added to a folder, such as posting it in Slack, creating an issue or adding a label, make an automation that starts when **A recording is added to a folder**. See [Automations](https://docs.screendesk.io/organization-and-workflows/workspace-automations.md).

{% hint style="warning" %}
Archiving or deleting a Customers folder also deletes the [triage rules](https://docs.screendesk.io/organization-and-workflows/recording-triage.md) that move recordings into it. Restoring the folder doesn't bring them back.
{% endhint %}

## Private folders

Available on Plus, Pro and Enterprise.

A private folder is visible only to the people you add, the person who created it, and workspace admins and editors. Choose **Private** when you create the folder, or later in **Manage access**. Switching a folder back to public clears its member list.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/organization-and-workflows/folders.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
