> For the complete documentation index, see [llms.txt](https://support.meetuma.ai/uma-knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.meetuma.ai/uma-knowledgebase/getting-started/services/approving-requests.md). # Approving requests Service requests have their own dedicated approval workflow, separate from resource booking approvals. This means approvers only see the service requests relevant to their categories. ### Reviewing and approving requests 1. Navigate to **Requests** in UMA, or open the approval notification email 2. Review the service request details, including items, quantities, pricing, delivery times, and any special instructions 3. Filter by status to focus on pending requests 4. **Approve** or **Decline** the request * If declining, provide a reason — the requester will be notified 5. The reviewer's name is recorded against each action for audit purposes ### Key behaviours * Each service category generates its own service request, so different categories can have different approvers * Approving or declining a service request does **not** affect the room booking itself * If a booking is cancelled, all associated service requests are automatically cancelled * If a requester edits a booking after a decline, a new approval cycle is triggered automatically ### Notifications **Requester notifications:** * Sent when a service request is submitted * Updated when service requests are approved or declined (with reason if declined) **Approver notifications:** * Sent when a new service request is awaiting approval * Include all service details, delivery times, and any special instructions --- # 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, and the optional `goal` query parameter: ``` GET https://support.meetuma.ai/uma-knowledgebase/getting-started/services/approving-requests.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.