> 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/assign-services-centrally.md). # Assign services centrally {% hint style="info" %} Walkthrough goes here. {% endhint %} Central assignment answers one question: who gets this. You can point the same service at one employee, at a whole team, at a department or at a location, in a single pass instead of repeating the configuration for every person. Assigning is preparation, not execution. Nothing is ordered at this point. The assignment defines scope and intent, and only after approval does anything get provisioned or delivered. The step beyond doing it by hand is templates. A template on a location or a group holds the standard set for that context, so someone joining the site or the department receives it without anyone assigning it again. Free stock is taken into account when that happens. That is worth setting up once you notice you are 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 %} ### Next You know who gets what. Next comes where it goes: [Place orders](/classes/admin/place-orders.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/assign-services-centrally.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.