> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/setup-guidepro/admin/approval-notices.md). # Approval Notices **Show important information before customers complete their orders.** Approval notices appear on the final checkout page before someone places an order. Use them to display terms and conditions, cancellation policies, or any other information customers need to see or agree to. ### Setting up your notices **Position**\ Control the order notices appear in. Put your most important ones at the top. **Confirmation Required**\ Turn this on if customers need to actively check a box to confirm they've read the notice. Good for legally required disclosures. **Active/Inactive**\ Toggle notices on or off. Inactive ones stay saved but won't show up on the checkout page until you turn them back on. **Add New Entry**\ Create as many notices as you need. Each one can have different settings and content. ### What to include Link to your terms and conditions, return policies, or any industry-specific requirements. You can also add plain text for quick disclaimers or important notes. The goal is making sure customers see what they need to see before they commit to an order. Keep your notices current so they match your actual policies. --- # 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://hub.equipme.io/setup-guidepro/admin/approval-notices.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.