> 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/resources/resources/paintscout-glossary.md).

# PaintScout Glossary

Definitions for key PaintScout terms, user types, estimating concepts, and integrations.

Use this glossary to quickly look up PaintScout terms. It covers user types, estimate language, pricing concepts, and integrations.

> **For AI/Automation:** A comprehensive machine-readable version of this glossary is available at [`glossary.yaml`](https://github.com/PaintScout/external-knowledgebase/blob/draft/.gitbook/assets/glossary.yaml) with structured definitions, relationships, and metadata.

* **Admin Account:** A legacy account type that granted access to all settings and estimates.
* **API:** Short for Application Programming Interface. It lets different applications communicate and integrate.
* **Area:** A specific space in a project, such as a kitchen or living room.
* **Auto Follow-Up:** A pre-written email or text sent automatically to customers based on specific conditions.
* **Auto-Populate:** Information filled in automatically under certain conditions.
* **Coverage Rate:** The area covered by a specific product measurement, like *400 square feet per gallon.*
* **Crew Note:** A note visible only to crew members on the work order, not customers.
* **Crew User:** A legacy account type for project managers, crew leaders, and painters with limited project access.
* **CSV File (Comma-Separated Values):** A plain-text file for exchanging data across different applications.
* **Dropbox:** A file-hosting platform integrated with PaintScout for sharing and storing documents.
* **Estimate Type:** A project category, such as interior or exterior.
* **Grouping:** Organizing substrates or items into categories for better estimate presentation and organization.
* **Integration:** Allowing separate applications to communicate and share data.
* **Line Item:** A custom item added to an estimate, with or without a cost.
* **Markup:** The difference between selling price and production cost.
* **Painter User:** *Currently in beta*. This is a limited access seat type designed for field workers — painters, crew members, and subcontractors.
* **Pipeline:** A CRM software provider integrating directly with PaintScout for tracking leads and deals.
* **Presentation:** A PaintScout feature adding photos and descriptions to estimates sent to customers.
* **Production Rates:** The calculations PaintScout uses to price surfaces and work.
* **QuickBooks:** Accounting software integrated with PaintScout for small to medium-sized businesses.
* **Sales User:** The primary seat type, designed for anyone who estimates, sells, or manages the business. This type can be fully customized with our custom permissions.
  * Previously, the legacy Sales account granted limited access to sales-related functions, not account settings.
* **Smart Template:** A template that stays up to date with your current settings.
* **Stripe:** An online payment platform for accepting payments securely in PaintScout.
* **Substrate:** A specific surface in a given area to be worked on, like walls or windows.
* **Success Package:** An add-on service that helps with initial account setup.
* **Surcharging:** Passing credit card processing fees to clients by including them in invoices.
* **Team User:** 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.
* **Template:** A preset estimate for frequently done projects, reducing repetition and time taken for estimates.
* **View-Only User:** A legacy account type designed for office staff with restricted access to essential information.
* **Win Rate:** The percentage of leads converting into sales, visible in your dashboard statistics.
* **Wisetack:** Offers consumer financing solutions for residential projects.
* **Workglue:** An integration that supports CRM, scheduling, and crew management workflows.
* **Work Order:** A document detailing all information for crew members to complete a painting job.
* **Zap:** An automated workflow connecting apps or services, usually triggered by an event.
* **Zapier:** Software automatically moving information between web apps, integrated with PaintScout.

&#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>Operations FAQ</strong></td><td>Answers to common Operations questions about deals, jobs, estimates, notes, tags, deal stages, and calendar management in PaintScout.</td><td><a href="/support/operations/crm/crm-faq.md">Operations FAQ</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/resources/resources/paintscout-glossary.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.
