> 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-manager.md). # Location manager {% @arcade/embed url="" flowId="pGJwxjWRAFbwUlliOjZG" %} A location manager is the person responsible for one site. Assigning them from the site itself is the short path, because the matching role comes with the assignment. You do not have to set it up separately under Settings first. The dropdown decides how far that responsibility goes. Both variants manage the services of their location. The purchaser can also order, the planner cannot. So the question you are really answering is whether this person should be able to spend money for their site, or only keep it in order. Purchaser is worth using when procurement should happen close to where the work is. A site manager who knows a replacement is needed does not have to route it through central IT first. Sites can have more than one manager, which is worth using rather than avoiding. A single named manager who is on holiday is a bottleneck, especially when approvals run through that role. ### Beyond the assignment: what the role itself carries The walkthrough above stops at the assignment, but the role has a second layer that is easy to miss. Open it under Settings, Roles and rights, and the Permissions tab shows what the role allows or denies for everyone who holds it. Four of these decide how much room a location manager really has. **Access to employees for the location manager** is the one people trip over. Without it, the manager sees the site and its equipment but not the people at it, and nobody understands why. **Access to the entire marketplace** lets them request anything in the catalogue, not only what is enabled for self service. Sensible for someone who orders for a whole site, surprising if you forget it is on. **Record and remove service instances** skip approval, ordering and fulfilment entirely. Recording is useful for entering existing stock after the fact. Removing deletes an active service without deprovisioning, which is why it is usually denied even for purchasers. **Skip approval** allows an order to bypass the approval flow, and only works with simple approval flows. Leave it off unless you have a reason that survives an audit. ### Read more {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/X3LUfEcujlAUipqAIvfQ" %} [Ordering in equipme: roles, scope and responsibilities](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/settings/portal-settings/roles-and-rights/ordering-in-equipme-roles-scope-and-responsibilities) {% endcontent-ref %} {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/vO7Eu5A5PcHEO85mj0HJ" %} [Individual Permissions for Employees](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/settings/portal-settings/roles-and-rights/individual-permissions-for-employees) {% endcontent-ref %} ### Next Sites are set up and someone is responsible for them. Next: [Employees](/classes/admin/employees.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-manager.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.