> 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-add-a-new-user.md).

# Add a New User

Add new team members to your PaintScout account and assign the right user type for their role.

Add new team members from User Management. PaintScout recommends a user type based on the role you choose.

## How to Add a New User

1\. Click the person icon in the top right and go to **Account Settings** → **Billing** → **User Management**.

2\. Click the **+Add User** button.

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

3\. Enter the user's name, email, and select their **role**.

4\. Review the recommended user type.

* **Sales** is best for owners, estimators, and sales reps who create estimates.
* **Team** is best for office staff, coordinators, and production managers who need visibility without estimate creation.
* **Painter** is best for field crews and subcontractors who need job access.

{% hint style="info" %}
You can adjust custom permissions later. See [Custom Permissions](/support/account-settings/users-and-permissions/user-permissions.md), [Sales User](/support/account-settings/users-and-permissions/sales-user.md), [Team User](/support/account-settings/users-and-permissions/team-user.md), and [Painter User](/support/account-settings/users-and-permissions/painter-user.md).
{% endhint %}

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-89f4eae6ae1d4409587968ca1d04a279739f15cd%2FScreenshot%202026-04-30%20at%2010.15.41%E2%80%AFAM.png?alt=media" alt="Screenshot showing the new user information form with fields to fill out and Save button"><figcaption></figcaption></figure>

5\. Click **Save**.

6\. Send the password creation email so the user can log in.

&#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>Deactivate a User</strong></td><td>Remove or deactivate a team member from your PaintScout account and optionally transfer their estimates to another user before removal.</td><td><a href="/support/account-settings/users-and-permissions/how-to-deactivate-a-user.md">Deactivate a 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-add-a-new-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.
