> 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/user-guides/visitor-management/check-in-out-of-a-building.md).
# Check in / out of a building
### **Pre-Registered Check In**
Checking in via the kiosk or mobile follows the same process:
Click on GIF to enlarge
1. Enter your name.
2. If the visitor is found, it will allow them to proceed to check in.
3. Check in.
4. The host is notified via an email notification.
### **Ad-Hoc Check In**
Checking in via the kiosk or mobile follows the same process:
* A prompt will ask if you’ve been invited.
* Press ‘no’ to continue to check in.
* Here you can check in as a visitor or an employee.
* Check in and the visit will be registered in the visit log.
### **Check Out**
Checking out via the kiosk or mobile follows a similar process:
* Enter your name.
* If the visitor is found, it will allow them to proceed to check out.
* Check out.
* The host is notified via an email notification.
---
# 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/user-guides/visitor-management/check-in-out-of-a-building.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.
