# v3.3.5 - 16th April 2026 ## Service request approval workflow **Who this is for:** Admins, Approvers Previously, service items were bundled with resource booking approvals. Now, services that require sign-off are routed through their own dedicated approval workflow — giving approvers clearer context and ensuring the right people review the right requests. #### Why it matters * Service requests are created per category, so approvers only see what's relevant to them * Approvers can approve or decline with a reason, and every action is attributed — creating a clear audit trail * Request status (Pending, Approved, Declined, Cancelled) is visible directly on the booking card, so bookers always know where things stand * Editing a booking after a decline automatically triggers a fresh approval cycle, keeping the process clean * Existing resource booking approvals are unaffected — this runs alongside your current setup *** ### Approval owner configuration **Who this is for:** Admins Getting service requests to the right approver used to require workarounds. Now you can configure exactly who approves what — by service category and optionally by cost centre — so requests are routed correctly from the start. #### Why it matters * Assign approver teams or individuals at the category level to ensure domain experts review requests * Override at the cost centre level when different budgets have different sign-off requirements * If no approver is configured, requests are auto-approved — keeping things moving for low-risk items * Changes only affect new requests, so in-flight approvals aren't disrupted *** ### Service tasks **Who this is for:** Admins, Building Admins Managing vendor fulfilment for meeting services has traditionally meant chasing emails and spreadsheets. Service Tasks changes that by automatically generating trackable tasks from approved service requests, giving facilities teams full visibility into what's been ordered, who's delivering it, and where things stand — all in one place. #### Why it matters * Every approved service request now creates a Service Task with a complete snapshot of items, quantities, pricing, and delivery times — no more manual tracking * A dedicated **Service Tasks** page provides a real-time overview of all vendor activity, sorted by delivery time * Status tracking (Pending → In Progress → Delivered → Completed) means you always know where each request is in the fulfilment process * Overdue tasks are flagged automatically, so nothing slips through the cracks * Filtering by building, category, status, or date range makes it easy to focus on what needs attention right now #### Vendor assignment * Vendors are assigned at the service category level and automatically inherited by tasks, reducing manual setup * If a category's vendor changes, active tasks update automatically — keeping everything in sync *** ### Export CSV from service tasks **Who this is for:** Facilities Managers, Finance Users Tracking service costs across buildings, vendors, and cost centres is now much simpler. You can export your Service Tasks data as a detailed CSV — perfect for financial reporting, cost reconciliation, and vendor performance reviews. #### Why it matters * A comprehensive export with 22 columns gives you everything you need: delivery dates, item-level pricing, cost centres, matter numbers, and vendor details * The export respects your current filters, so you get exactly the data you're looking for without manual cleanup * Vendors only see their own tasks, maintaining data separation * All dates reflect your configured timezone for accurate reporting *** ### Cost centre management **Who this is for:** Admins, Building Admins For organisations that need to track and allocate service costs, cost centres provide the structure. Admins can create, manage, and control visibility of cost centres so that spending is attributed correctly and only relevant options are shown to each user. #### Why it matters * Cost centres can be restricted to specific teams, so users only see the ones relevant to them — reducing errors and speeding up the booking process * Deactivating a cost centre removes it from new requests while preserving historical data for reporting * When requesting services, users are prompted to select a cost centre when costs are involved — ensuring proper allocation from the start * Cost centres flow through to Service Tasks and CSV exports, giving finance teams the traceability they need *** ### Matter number for service requests **Who this is for:** Meeting Organisers When services need to be billed to a specific project or client, a matter number makes that possible. This optional field lets organisers tag service requests with a billing reference that carries through to Service Tasks and CSV exports. #### Why it matters * Provides a clear link between service costs and the project or client they relate to * Fully optional — it's there when you need it and stays out of the way when you don't * Flows through the entire chain from request to task to export, so finance teams can reconcile costs without chasing down references *** ### Per-Item delivery time for meeting services **Who this is for:** Meeting Organisers and Vendors Not everything needs to arrive at the same time. Per-item delivery times let organisers specify when each service item should be delivered during a meeting — whether that's coffee at the start or lunch halfway through. #### Why it matters * Each item defaults to the meeting start time for quick submission, but can be adjusted independently for more precise scheduling * If the meeting time changes, unmodified delivery times update automatically — manually adjusted items are flagged so nothing is lost * Delivery times must fall within the meeting window, preventing scheduling errors * Vendors see the exact delivery time per item on their Service Tasks, improving fulfilment accuracy *** ### Drag and Drop Calendar Bookings **Who this is for:** All Users Rescheduling a booking no longer means opening the full booking form. You can now drag to move or resize to adjust bookings directly on the calendar — a faster, more intuitive way to manage your day. #### Why it matters * Quick adjustments that used to take multiple clicks now happen with a simple drag * A confirmation step shows you the original and proposed time before anything is saved — no accidental changes * Permission-based controls ensure you can only move bookings you're authorised to edit * Conflicts and working hours violations are caught automatically before confirming, so you won't accidentally double-book #### Permissions * **Users** — own bookings only * **Managers** — own bookings plus desk bookings made by others * **Advanced Managers, Building Admins, Admins** — all bookings *** ### Meeting type dropdown **Who this is for:** Admins (for setup), All Users (for selection) Understanding how your meeting rooms are being used starts with knowing what types of meetings are happening. Admins can now define meeting types that users select when booking a room — making it easy to report on meeting volumes by category. #### Why it matters * Gives organisations insight into how meeting spaces are used — whether it's client meetings, internal stand-ups, or training sessions * Users can optionally tag their bookings with a meeting type, keeping the process lightweight * The **Resource Booking Report** now includes a Meeting Type column, so you can analyse usage patterns and make data-driven decisions about your space --- # Agent Instructions: 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://support.meetuma.ai/uma-knowledgebase/release-notes/web/2026/v3.3.5-16th-april-2026.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.