> 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/locations/location-templates.md). # Location templates {% @arcade/embed url="" flowId="qB8tHMO9Z0cQn8LSTda8" %} A template holds the services that belong to a site by default. You set it up once, and from then on anyone assigned to that location gets them. That includes people moving over from another office, not just new hires. It stays a proposal, not a rule. When someone is assigned, the services appear preselected, and you can uncheck anything this particular person does not need before you continue. A template prepares the assignment, it does not order anything. The items land in approvals like any other request, so the usual decision still happens before something is bought. That decision gets easier if you switch on free inventory first. The site's stock is then checked before a new order is triggered, pre-ordered goods come next, and only then does something new get ordered. Useful in exactly the situation where returned devices pile up while new ones are being bought. The moment to set one up is when you notice you are assigning the same three or four things to every new starter at a site. Templates are not limited to locations. Groups and departments can carry one too, and they are built and maintained centrally under [Template management](/classes/admin/offer-management/template-management.md). ### 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 %} ### Next Templates need people to act on. Next: [Location manager](/classes/admin/locations/location-manager.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/locations/location-templates.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.