> 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/release-notes/web/2022/v2.9.6-29th-september-2022.md).
# v2.9.6 - 29th September 2022
**📌 Office Map Kiosk Application**
Our new signage application is here!
You can now display your office map in public areas of your office to allow staff and guests to interact with your building digitally.
The office map application will help with finding and booking spaces as well as understanding occupancy and environmental data at floor or zone level.
To get started, navigate to [**office.meetuma.ai**](https://office.meetuma.ai/) and pair your application using the following steps documented [**here**](/uma-knowledgebase/getting-started/set-up-your-hardware/applications/office-map-application.md)**.**
**✏ Rename 'No Show' to 'Away'**
We've renamed the status **'No Show'** to **'Away'** to improve the understanding of this label.
This helps in circumstances where a user has arrived for their booking but has temporarily left but not cancelled their booking.
**📍 Master Zone**
You can now create or edit a '**Zone'** as a '**Master Zone**'.
This setting only applies to the Office Map application.
At this moment in time this will just be used to allow you to choose a specific '**Zone**' to represent the amount of people on a floor based on people count data.
Only one master zone can be assigned per floor.
---
# 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/release-notes/web/2022/v2.9.6-29th-september-2022.md?ask=&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.
