> 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/deleting-a-crew.md).
# Deleting a Crew
Remove a crew from your account after reassigning or canceling any active jobs assigned to it.
{% hint style="danger" %}
**Important:** this feature requires the paid **Operations add-on.**
{% endhint %}
If a crew is no longer needed, you can delete it from your account settings. There are a couple of things to check before you do.
***
## Before You Delete
A crew cannot be deleted if it has any current or upcoming jobs assigned to it. You'll need to either cancel or reassign those jobs first before the option to delete becomes available.
***
## Deleting a Crew
1. Go to **Account Settings → Billing → User Management → Crews**
2. Find the crew you want to remove
3. Click the `...` next to the crew
4. Select **Delete**
5. Confirm the deletion
{% hint style="info" %}
Deleting a crew does not delete the users associated with it. Your Painter accounts and other team members will **remain active** — they'll just no longer be grouped under that crew.
{% endhint %}
{% hint style="info" %}
Need to remove a person instead of the whole crew? See [Deactivate a User](/support/account-settings/users-and-permissions/how-to-deactivate-a-user.md).
{% endhint %}
---
# 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://help.paintscout.com/support/operations/crews/deleting-a-crew.md?ask=&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.
