> 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/classes/admin/offer-management/template-management.md). # Template management {% hint style="info" %} Walkthrough goes here. {% endhint %} A template is a standard set of services tied to a context. Attach it to a location, a group or a department, and anyone who lands in that context receives the set without a request being written for it. This is where you build and maintain those sets centrally. The template itself lives here, under Offer management. Where it applies is decided on the location or the group it is attached to. Two properties are worth knowing before you build your first one. A template proposes rather than dictates: when someone is assigned, the services come preselected and anything they do not need can be unchecked. And it prepares rather than orders. The items go into approvals like any other request, so the usual decision still happens. The free stock option is the one that pays for itself. With it switched on, existing stock at the site is used before a new order is triggered, then pre-ordered goods, and only then something new. That is exactly the situation where returned devices otherwise sit in a warehouse while identical ones are being bought. The moment to build one is when you catch yourself assigning the same three or four things to every new starter. ### Read more {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/nApeKYjcyYz9yzaDlEe4" %} [Template management](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/offer-management/template-management) {% endcontent-ref %} {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/U8pfUbRiPnd0bRirROuy" %} [Automated Service Assignment with Templates](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/my-company/groups/automated-service-assignment-with-templates) {% endcontent-ref %} ### Next Not everything runs on a template. For everything else: [Assign services centrally](/classes/admin/assign-services-centrally.md). --- # 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/classes/admin/offer-management/template-management.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.