> 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/team-user.md).
# Team User
Understand who should use a Team seat, what Team users can do, and which extra permissions are available.
## What is a Team User?
A **Team User** is a lighter seat type designed for people who need broad visibility across the account but don’t build estimates and invoices. Think office staff, production managers, and scheduling coordinators — people who keep jobs moving and support the business without being in the sales seat.
Team seats can be added on **any plan**, with or without the Operations add-on.
***
## What Team Users Can Do
By default, Team users have broad read and management access across the account:
* View all users' documents (estimates, invoices, etc.)
* View pipelines, estimates, invoices, calendars, tasks, contacts, and companies
* Create deals and have full capability on deals
* Create events and assign others to sales events or jobs
* Create tasks, contacts, and companies
* Manage their own profile and notification preferences
### On estimates and invoices:
Team users can’t create estimates or edit areas, line items and pricing, but they can still take meaningful action on them:
* Add crew notes
* Add/change colour on products
* Add additional work
* Add payments
* Edit the job address and job identifier (e.g., a PO or job number)
* Send estimates and invoices
* Upload images
* Change status, pipeline, stage, tags, source, estimate type, and template
* View activity, chat, and calculations in the sidebar
***
## Custom Permissions
These are all **off by default** for new Team seats and can be enabled per user:
| Permission | What it does |
| ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Access to account settings** | Manage account-wide settings including estimate types, production rates, products, templates, branding, communications, and more |
| **Access to account settings — Billing** | View the account's subscription, billing information, and user management |
| **Access to dashboard** | View the account dashboard and stats |
| **Access to reports** | View sales and pipeline reports |
| **Ability to export data** | Export contacts, deals, and other data |
{% hint style="info" %}
**Pro Tip:** For a production manager or scheduling coordinator, consider enabling **Dashboard** and **Reports** access so they can track job progress and workload without needing a Sales seat.
{% endhint %}
***
## What Team Users Cannot Do
* Create estimates or invoices
* Edit areas, line items or pricing on estimates and invoices
* Be the owner of a sales event
* Be the account owner or transfer account ownership
***
## Adding a Team User
1. Go to **Account Settings** → **Billing** → **User Management**
2. Click **+ Add User**
3. Enter their name, email, and select their role
4. PaintScout will recommend the right seat type based on the role selected — Team is recommended for administrators, project leads, accounting or marketing roles.
* If PaintScout recommends a Sales seat, click **Switch to Team seat** **instead** if you feel a Team seat is more appropriate!
---
# 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/team-user.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.
