> 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/general-overview.md). # General overview {% @arcade/embed flowId="saP3AgMiKh3yt2sqlpK8" url="" %} ### General overview As an administrator, you are responsible for structuring and managing how services are provided across your organization. equipme gives you a central place to do exactly that, without forcing you into rigid processes or one-off decisions. Instead of handling requests, assets, and orders in separate systems, equipme brings everything together. Your role as an admin is not to react to every individual task, but to create clear structures that work consistently for employees, teams, and locations. *** ### How equipme is structured equipme is built around a simple lifecycle that connects planning, control, and daily operations.\ Instead of treating services, assets, and requests as separate topics, equipme brings them together in one continuous flow. The lifecycle starts with **procure**.\ This is where services enter your organization. The Marketplace, vendor management, and approval processes help you decide which services are available and how orders are reviewed before anything is executed. Once services are in place, the focus shifts to **manage**.\ Here, you maintain visibility and control. Assets, inventory, warehouse management, and cost controlling give you a clear overview of what exists, where it is located, and how it is used across the organization. The final part is **operate**.\ This is where services are actively used in everyday work. Onboarding and offboarding, workflows, and the ticketing system support operational processes and ensure that services continue to work smoothly over time. As an administrator, your role is to connect these three areas. You define structures and rules so services move cleanly from procurement to management and into daily operation. This structure allows equipme to stay flexible while remaining consistent, even as your organization grows. *** ### Your role as an administrator Your main responsibility is to define **how services are handled**, not to manage every single action manually. This includes:\ – structuring employees, teams, and locations\ – deciding which services are available\ – assigning services centrally when needed\ – reviewing and approving orders\ – keeping visibility over costs, inventory, and orders equipme supports this by separating preparation, approval, and execution, so processes stay clear even as your organization grows. *** ### What to expect in the next sections The following sections go deeper into specific admin tasks, such as assigning services centrally, handling approvals, placing orders, and managing inventory. You do not need to understand everything at once. equipme is designed so you can start simple and expand your setup over time. --- # 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/general-overview.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.