> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/operations/crews/create-a-crew.md).

# Create a Crew

{% hint style="danger" %}
**Important:** this feature requires the paid **Operations add-on.**
{% endhint %}

Crews let you group your team members together so you can assign and schedule jobs on the Production Calendar. Once a crew is set up, you can assign them to jobs and track their workload at a glance.

***

## Creating a Crew <a href="#h_31f2111191" id="h_31f2111191"></a>

1. Go to **Account Settings → Billing → User Management → Crews**
2. Click **+ Add Crew**
3. Give your crew a name
4. Select a Lead — this can be any active Team or Sales user
5. Choose a crew color — this will show up on the Production Calendar to help you quickly identify assignments
6. Click **Confirm**

<figure><img src="/files/6X82bTPw9ljY4z9qYyGB" alt=""><figcaption></figcaption></figure>

***

## A Few Things to Know <a href="#h_2fe13d2902" id="h_2fe13d2902"></a>

* A crew **Lead** can be any active PaintScout user with a Team or Sales seat
* Crew colors appear on the **Production Calendar Schedule view** to help with visibility
* A crew **cannot be deleted** if it has current or upcoming jobs — you'll need to cancel or reassign those jobs first


---

# 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:

```
GET https://help.paintscout.com/support/operations/crews/create-a-crew.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
