> 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/estimating/areas-and-rates/saving-rates-and-line-items-to-settings.md).
# Saving Rates & Line Items to Settings
Save custom rates and line items from an estimate to Settings so they are reusable on future estimates.
You can now save your custom rates and line items to Settings, so they're available every time you build an estimate, without having to re-enter them.
{% hint style="info" %}
**Note:** This feature is only available to users with permission for account settings.
{% endhint %}
### Why use this
If you regularly use the same rates or line items across jobs, saving them once means you won't have to type them in from scratch each time.
### How to save a custom rate or line item
1. Open an **estimate**.
2. Find the rate or line item you want to save.
3. Click the **3 dots** next to it.
4. Select **Save to Settings**.
Your saved item will now show up as an option whenever you're building an estimate.
***
### Editing or removing saved items
1. Go back to **Account** **Settings > Production Rates or Line Items**.
2. Click on the item you want to change.
3. Update the details and click **Save**, or click **Delete** to remove it.
Changes you make here won't affect estimates you've already created, only new ones going forward.
---
# 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/estimating/areas-and-rates/saving-rates-and-line-items-to-settings.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.
