> 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/settings/meeting-settings/meeting-types.md).

# Meeting types

### Meeting Types

Meeting Types allow organisations to categorise room bookings — such as "Client Meeting," "Training Session," or "Internal Stand-up" — so admins can report on how meeting spaces are being used and make data-driven decisions about their workspace.

### Admin setup

#### Creating meeting types

1. Go to **Company Settings → Meeting Types**
2. Click **Add Meeting Type**
3. Enter a name (e.g., "Client Meeting")
4. Click Save

#### Managing meeting types

* **Edit** — update the name of an existing meeting type at any time
* **Activate / Deactivate** — deactivating a meeting type removes it from the dropdown for new bookings, but it remains on any existing bookings for historical accuracy
* **Delete** — permanently remove a meeting type if it's no longer needed

Only active meeting types appear in the user-facing dropdown.

### User Experience

When booking a room, users will see a **Meeting Type** dropdown in the booking form.

* Selection is **optional** — users can leave it blank if they prefer
* Only active meeting types are shown
* The selected meeting type is stored with the booking and visible on the booking details

### Reporting

The **Resource Booking Report** CSV now includes a **Meeting Type** column, making it easy to:

* Analyse how meeting spaces are used across your organisation
* Identify the most common types of meetings by building, floor, or room
* Spot trends over time to inform space planning decisions


---

# 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/settings/meeting-settings/meeting-types.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.