> 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/account-settings/users-and-permissions/how-to-deactivate-a-user.md).

# Deactivate a User

Remove or deactivate a team member from your PaintScout account and optionally transfer their estimates to another user before removal.

Deactivating a user in PaintScout removes their access to the account. Before you deactivate them, you can transfer their estimates to another team member. If your account includes the Operations add-on, the same choice also applies to their deals.

## How to Deactivate a User

1\. Go to **Account Settings** → **Billing** → **User Management** and click **Deactivate** on the user you want to remove.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-66c9cdce39fd94b616246bdbff65c97f63bc95a5%2FScreenshot%202026-04-30%20at%2010.22.09%E2%80%AFAM.png?alt=media" alt="Screenshot showing the User Management section with the Deactivate button for removing a user"><figcaption></figcaption></figure>

2\. A window will appear where you can decide what to do with the user's existing estimates.

* If your account includes the [Operations add-on](/support/operations/crm.md), this selection also determines what happens to that user's deals.

{% hint style="warning" %}
You cannot deactivate the account Owner. [Transfer ownership](/support/account-settings/users-and-permissions/account-ownership.md) to another Sales user first.
{% endhint %}

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-028afdcc8a10e8b23118c71e8f48350fc6fac31b%2F1730583123_445832ebc8222c0e28c83a699c34?alt=media" alt="Screenshot showing the deactivation prompt with options for handling the user&#x27;s existing estimates"><figcaption></figcaption></figure>

***

## What happens when you transfer records?

When you transfer estimates, you choose an active user to become the new owner of those records. That user receives notifications for those estimates, and the estimates count toward their dashboard metrics.

If you have the Operations add-on, transferred deals also move to that same active user.

This action cannot be reversed.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-9b2cd4e482e609c63624da6a78098049ca6d6d95%2FScreenshot%202026-04-21%20at%209.05.12%E2%80%AFAM.png?alt=media" alt="Screenshot showing the transfer records option when deactivating a user and reassigning estimates or deals"><figcaption></figcaption></figure>

{% hint style="info" %}
This does not transfer account ownership. [Account ownership](/support/account-settings/users-and-permissions/account-ownership.md) can only be transferred by the current Owner to another Sales user.
{% endhint %}

***

## What happens to a user's jobs if I remove them from a crew or deactivate them?

If your account includes the [Operations add-on](/support/operations/crm.md), a user may be assigned to a crew as a lead or crew member. In that case, PaintScout reminds you to remove them from the crew before you complete deactivation.

After you remove them from the crew, they stay listed on current and past jobs. They are not added to future jobs.

After you deactivate the user, they are removed from all records, including current and past jobs.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-8444e64314a0e2c37a3cc3baff09ce2187eb4645%2FImage%2011.png?alt=media" alt=""><figcaption></figcaption></figure>

***

## What happens to a deactivated user’s estimates in reports?

If you don’t transfer a user’s estimates, those estimates remain under that user. They’re included in your Dashboard and Reports, so your historical numbers remain accurate.

To view a deactivated user’s numbers, open the estimator filter on the Dashboard or in Reports and expand the **Deactivated** group. [Learn more about filtering the Dashboard >](/support/dashboard-and-reports/dashboard-search-reporting/filtering-on-the-dashboard.md)

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-93104235ffe4cbad437a9051be924fa5d24c970b%2FScreenshot%202026-10-13%20at%2012.33.32%E2%80%AFPM.png?alt=media" alt=""><figcaption></figcaption></figure>

&#x20;&#x20;

## Related articles

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Add a New User</strong></td><td>Add new team members to your PaintScout account and assign the right user type for their role.</td><td><a href="/support/account-settings/users-and-permissions/how-to-add-a-new-user.md">Add a New User</a></td></tr><tr><td><strong>Custom Permissions</strong></td><td>Configure access levels for Sales, Team, and Painter users using custom permissions to control what team members can view and edit.</td><td><a href="/support/account-settings/users-and-permissions/user-permissions.md">Custom Permissions</a></td></tr></tbody></table>


---

# 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/account-settings/users-and-permissions/how-to-deactivate-a-user.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.
