> 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/customization/presentations-and-terms.md). # Presentations & Terms Customize how your estimates look to customers with presentations and terms. Presentations and terms control how your proposals look and what contract language they include. Build branded multi-page presentations, choose the right defaults for each estimate type, and manage the terms attached to new and existing estimates. ## In This Section * [Presentations Overview](/support/customization/presentations-and-terms/presentations-overview.md) — Build branded multi-page proposal presentations with pages, sections, and live previews * [Presentation Sections](/support/customization/presentations-and-terms/presentation-sections.md) — Explore the available section types for layout, media, testimonials, documents, and more * [Setting a Default Presentation](/support/customization/presentations-and-terms/setting-a-default-presentation.md) — Assign the right presentation to each estimate type so new estimates use it automatically * [Updating Estimate Terms](/support/customization/presentations-and-terms/updating-estimate-terms.md) — Add or edit terms in settings and update terms on individual estimates before acceptance * [Setting Default Terms](/support/customization/presentations-and-terms/setting-default-terms.md) — Assign a default terms document to each estimate type --- # 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/customization/presentations-and-terms.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.