> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/missions/how-to-guides/organize-missions-with-folders.md). # Organize Missions with Folders Folders let you group related Missions together in your [Library](/missions/where-to-find-your-missions.md) and control who has access to them. Instead of one flat list of hundreds of Missions, you organize them by department, project, or any structure that makes sense for your organization. ## Why use Folders? As your Mission Library grows, finding and managing content becomes harder. A restaurant might have 200 Missions across Kitchen, Front of House, HR, and Compliance. Without Folders, every admin sees every Mission. With Folders, the Kitchen manager sees only Kitchen Missions, HR sees only HR Missions, and sensitive content stays restricted. **Example:** A hotel creates three Folders — "Housekeeping", "Front Desk", and "HR Compliance". The Housekeeping supervisor only has access to the Housekeeping Folder and can't see confidential HR surveys. The General Manager has access to all three. ## How to create a Folder 1. Go to **Missions → In Library** 2. Click **New Folder** in the navigation panel 3. Fill in the sidebar form | Field | Required | Details | | ------------ | -------- | ---------------------------------------- | | **Name** | Yes | Max 30 characters, must be unique | | **Tag** | Yes | Same tag system as Missions | | **Category** | Yes | Same category system as Missions | | **Access** | No | Defaults to Public (everyone can see it) | 4. Save ## Controlling access By default, a Folder is **Public** — all admins can see its Missions. To restrict access, choose one of two options when creating or editing a Folder: * **Choose Group** — select one or more [Groups](/your-organization/groups.md). Only members of those Groups can access the Folder's Missions * **Choose People** — select individual [people](/your-organization/people.md) The Folder creator is automatically added as an **owner** with full permissions. Other System Admins added to the Folder can also perform all actions. ### What access controls Users without Folder access **cannot** see or open Missions inside that Folder — not in the [Library](/missions/where-to-find-your-missions.md), not in [Overview](/analytics-and-monitoring/overview.md), not in [Reporting](/analytics-and-monitoring/reporting.md). If they follow a direct link to a restricted Mission, they see an "Access Denied" page. ## Working with Folders ### Adding Missions to a Folder * **Create inside a Folder:** Open a Folder → click New Mission — the Mission is automatically part of that Folder * **Move existing Missions:** Select Missions in the Library → **Move to Folder** → choose the destination * A Mission can belong to **only one Folder** at a time {% embed url="" %} ### Moving and removing Missions * **Move between Folders:** Select a Mission → **Move** → choose a different Folder * **Remove from Folder:** Select a Mission → **Remove from Folder** — it returns to the main Library (no Folder) * If a Mission with the same name already exists at the destination, a **title conflict** window appears — rename or cancel ### Bulk actions inside Folders When you open a Folder, the navigation panel gives you bulk actions: * **Assign** — schedule multiple Missions at once * **Manage Tags/Categories** — update tags or categories in bulk * **Move / Remove** — move or remove multiple Missions from the Folder ## Archiving and deleting Folders
ActionWhat happens
ArchiveThe Folder and all its Missions are archived. Missions with Draft or Ready status stay in those statuses but can't be published while archived.
RestoreReactivates the Folder and all Missions inside
DeletePermanently removes the Folder and all its Missions (only available after archiving)
{% hint style="info" %} If a Folder contains Media Missions used inside other Surveys, Checklists, or Tests, you'll need to replace those references before archiving. {% endhint %} ## Folders across the system Folders aren't just a Library — the Folder name appears throughout your Organization: * **In Teams:** Folder column in the Team Library * **On mobile:** Folder name on Mission cards and Mission details * **In Overview:** Folder column in History, Running, and Scheduled views (filterable) * **In Dashboard:** Folder name in Aging and Execution dashboards * **In Reporting:** Folder column in Closed, Running, Canceled, Overdue, Short Execution, Response Analysis, and Test reports (filterable) * **In exports:** Folder column included in all Excel exports ## Good to know * Folders exist in the **Missions (In Library)** — no nested folders (folders inside folders) * Each Mission can belong to **only one Folder** * [System Admins](/your-organization/people.md#roles) can create Folders; [Organization Managers](/your-organization/people.md#roles) can access Folders they're added to * **Duplicating a Folder** copies tags, categories, and access settings, but **not** the Missions inside * Folder access also restricts which Missions appear in [Dashboard](/analytics-and-monitoring/dashboards.md), [Overview](/analytics-and-monitoring/overview.md), and [Reporting ](/analytics-and-monitoring/reporting.md)— users only see data for Missions they have access to --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://documentation.taskmaverick.com/missions/how-to-guides/organize-missions-with-folders.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.