> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/settings/customize-jobs-task-folders.md).

# Customize your Jobs task folders

On the Jobs tab of Tasks settings you can rename any Jobs folder, add close-out folders your technicians pick from when they finish a job, and add standalone folders your office staff move work into by hand. To group custom folders under task categories, use the [Custom Folders tab](/administration/settings/organize-task-categories-and-folders.md). You can also move an existing standalone folder from Jobs into one of your categories there.

> **Where to find it:** Settings -> Work Management -> Tasks -> Jobs

You need Task Automations write access to save changes. Without it the folders are read-only and the Save button stays disabled.

## The three kinds of Jobs folder

**Job Summary Statuses** are the close-out folders. When a technician finishes a job, the Job Status dropdown on their job summary lists these, and the task lands in the folder they pick. Complete (Ready to Invoice), Complete (No Invoice Needed), and Incomplete (Needs Another Visit) are the defaults and can't be removed. Add your own with **Add close-out folder** when a job can end another way, such as "Complete (Warranty)" or "Complete (Needs Parts Ordered)". Custom close-out folders show a **Custom** badge and appear in the mobile app alongside the defaults. Job summary questions asked for **Any job status** are asked for your custom close-out folders too; questions tied to one of the default statuses stay with that status.

**Opened automatically** holds Missing Summary and Never Clocked In. Essential files a task in these when a job closes out with something missing, so you can rename them but not remove them. See [Choose when Never Clocked In tasks are created](/administration/settings/choose-when-never-clocked-in-tasks-are-created.md) for the timing setting.

**Standalone folders** are never picked in the field and never opened automatically. Office staff move tasks in by hand using **Move to Folder**, or create a task there with **Create a task**. Add one with **Add standalone folder** when you want somewhere to park work between the automatic folders, such as "Ready for Review". They show a **Manual** badge and are never offered in the mobile app's Job Status dropdown. Workflows and the assistant can't file tasks into folders you added; move tasks there with a task's Quick Actions. If you move a job's task into one, the technician's job summary shows that folder as the current Job Status; they can leave it there or pick a close-out status, and editing the summary leaves the task's status in that folder unchanged.

## Rename, reorder, and add folders

1. Type a new name into any folder's box to rename it. Renaming is label-only: open tasks, task status automations, and reports stay attached to the folder they're already in.
2. Drag your own folders by the grip handle to reorder them. The default folders keep their fixed positions ahead of yours.
3. Use **Add close-out folder** or **Add standalone folder**, enter a name, and confirm how tasks get there. A new folder starts with To Do, In Progress, and Done statuses; set its statuses on the Task Statuses tab.
4. Click **Save**. Nothing changes until you do.

If you switch businesses while this tab is open, your pending folder edits stay with the business where you made them. Switch back to continue editing and save.

Each folder shows how many open tasks it holds. A renamed folder keeps its new name everywhere: the Tasks sidebar, the move-to-folder picker, Task Statuses, Task Automations, and the technician's Job Status dropdown.

## Remove a folder you added

Use the trash icon next to a custom folder. If the folder still has tasks, the **Move work before deleting** dialog asks you to choose another Jobs folder for them; open tasks stay open and done tasks stay done in the folder you pick. The folder you pick needs a Done status for the finished tasks and an open status for the rest; if it is missing one, add it on the Task Statuses tab first. Any Task Automations set up for the removed folder are removed with it. A folder that a published workflow refers to can't be removed until that workflow is republished with another folder; the error names the workflow. Save to apply the deletion.

Moving tasks as part of folder deletion does not trigger folder-change or status-change workflows. This lets you reorganize folders without starting follow-up actions for all the moved tasks. Moving a task normally through Quick Actions still triggers any applicable workflows.

## Related guides

* [Add, rename, reorder, or remove task statuses](/administration/settings/add-rename-reorder-or-remove-task-statuses.md)
* [Automate task statuses with Task Automations](/administration/settings/automate-task-statuses-with-task-automations.md)
* [What creates Jobs tasks (and moving them between folders)](/field-operations/tasks/what-creates-jobs-tasks-and-moving-them-between-folders.md)
* [Task folder and subfolder meanings](/field-operations/tasks/task-folder-and-subfolder-meanings.md)
* [Set up Job Summaries](/administration/settings/set-up-job-summaries.md)


---

# 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://learn.withessential.com/administration/settings/customize-jobs-task-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.