> 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/crm/tags-in-paintscout.md).

# Tags

Use tags to label and organize contacts, companies, deals, estimates, and invoices for easy filtering and grouping.

Tags in PaintScout are customizable labels you can add to contacts, companies, deals, estimates, and invoices. Use them to organize, filter, and group records — for example, "Repeat Customer" or "High Priority."

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

## What Is a Tag?

A **tag** is a simple label you can add to contacts, companies, deals, estimates, and invoices to help organize and filter your data. Tags make it easy to group similar records and find what you’re looking for later.

Examples:

* “Repeat Customer”
* “New Lead”
* “High Priority”

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

***

## How Do I Customize Tags?

1. Click the **person icon** in the top right and choose **Account Settings**
2. Go to the **Tags** section
3. Here you can edit, remove, and add new tag labels

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

&#x20;&#x20;

## Related articles

* [Notes](/support/operations/crm/notes-in-paintscout.md) — Add and manage internal notes on contacts, companies, and deals
* [Operations Guide](/support/operations/crm/paintscout-operations-guide.md) — Explore the full Operations workflow across deals, events, jobs, and tasks

## 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>Notes</strong></td><td>Add, pin, edit, and manage internal notes on contacts, companies, and deals in PaintScout with version history tracking.</td><td><a href="/support/operations/crm/notes-in-paintscout.md">Notes</a></td></tr><tr><td><strong>PaintScout Operations Guide</strong></td><td>Overview of PaintScout Operations features including deals, sales events, jobs, tasks, contacts, companies, notes, tags, and automations.</td><td><a href="/support/operations/crm/paintscout-operations-guide.md">PaintScout Operations Guide</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/operations/crm/tags-in-paintscout.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.
