> 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/approve-requests.md). # Approve requests Approving requests is one of the core responsibilities of an Admin in equipme. This is the moment where a request turns into a binding action. Whether it is a service order, a change to an existing setup, or a request created through a template, approval is the control point that keeps processes clean, costs transparent, and responsibilities clear. As an Admin, you do not decide whether approvals exist. You are the role that reviews and approves them.
### What a request represents A request is a formal ask within equipme that requires an explicit decision. It usually originates from the Self Service area or from structured internal processes. Typical examples are new service orders, changes to active services, or assignments that were prepared automatically but must be confirmed before they move forward. The key idea is simple. A request can be fully prepared and visible in the system, but nothing is executed until it is approved. This separation is what prevents uncontrolled actions and unexpected costs. ### How to approve a request To approve a request, you work directly from the **Approvals** area in the main navigation. This is the central place where all requests that require an administrative decision are collected.
Inside the Approvals view, each row represents a request or a change that is waiting for approval. You can see all relevant information at a glance, including the service name, assignment context, costs, provider, and current status. To review a request in detail, select it from the list. Once selected, the request becomes active and its full context is displayed. This allows you to verify what exactly will happen once the request is approved. Before approving, take a moment to review the following: * The requested service and configuration * The assignment, such as employee, group, or location * One time and monthly costs * Delivery and provider information, if applicable * Any notes or justification added to the request If everything is correct, you approve the request by proceeding with the action provided in the approval view. At this point, you also confirm the applicable terms, such as the general conditions, before finalizing the approval. Once approved, the request immediately moves forward in the process. Depending on the type of request, this can trigger order placement, fulfillment steps, or downstream processes with the connected provider. From this moment on, the request is no longer pending and becomes an active operation within equipme. Approval is therefore the final checkpoint before execution. Nothing is ordered, assigned, or fulfilled until this step is completed. --- # 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/approve-requests.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.