> 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/administrative-functions/assign-services-centrally.md). # Assign services centrally {% @arcade/embed flowId="YyJywPzZQanc7FwQamEy" url="" %} *** ### Defining service assignments When assigning services centrally, you decide **what should be assigned** and **to which scope**. Assignments can be made for: * individual employees * complete teams * departments * locations This makes it easy to reflect organizational structures and roles directly in your service setup. *** ### Assigning services to multiple recipients A key benefit of central assignment is the ability to assign the same services to multiple recipients at once.
For example, when a team requires a standard set of services, you can assign this setup centrally instead of repeating the same configuration for each individual employee. The same applies to departments or locations where identical service structures are required. This helps ensure: * consistent service setups * identical configurations * reduced manual effort * clear visibility across the organization *** ### Preparation, not execution Assigning services centrally does **not** place an order by itself.\ At this stage, you are defining structure and intent. The actual execution happens later, when these assignments are turned into orders and enter the approval flow. Only after approval are services provisioned, delivered, and activated. *** ### How this fits into the overall process Central service assignment is an important step before placing orders.\ It separates planning from execution and allows you to prepare clean, scalable setups before anything is processed operationally. This approach is especially useful for: * onboarding scenarios * team or department expansions * recurring service distributions * standardized setups across locations --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://hub.equipme.io/classes/administrative-functions/assign-services-centrally.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.