> 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/admin-setup.md).

# Admin setup

## Admin setup

This guide covers the initial setup required before users can start requesting services with their bookings.

### 1. Configure service categories

Service categories group related service items, such as Catering, AV Equipment, or Room Setup.

**How to create a service category:**

1. Go to Manage → Services → Service Categories
2. Click Add Category
3. Enter the following details:
   * Name – e.g., "Catering"
   * Buildings – one or multiple buildings where this category is available
   * Description (optional) – internal or admin notes
4. Click Save

You can edit or delete categories at any time.

### 2. Create service items

Service Items are the actual services users can request (e.g., "Coffee & Tea," "Projector," "Room Setup Assistance").

**How to create a service item:**

1. Go to Manage → Services → Service Items
2. Click Add Item
3. Enter:
   * Name – e.g., "Coffee & Tea Service"
   * Category – select one (each item belongs to one category only)
   * Buildings – select the buildings linked to that category
   * Unit Price (optional) – for reference or internal billing
   * Description (optional) – details about the service
4. Click Save

{% hint style="info" %}
Admins can create, edit, or delete service items anytime. Service item currency can be updated within the company or building settings.
{% endhint %}


---

# 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://support.meetuma.ai/uma-knowledgebase/getting-started/services/admin-setup.md?ask=<question>&goal=<user_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.