> For the complete documentation index, see [llms.txt](https://docs.coreway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreway.com/coreway-hr/admin-management/meeting-room-reservation.md).
# Meeting Room Reservation
## 1. Add New Conference Room
* Operation steps: \
\[User Center] > \[Meeting Room Reservation] > \[Meeting Room Management] > \[Add Meeting Room]
* Enter the meeting room name and work location to set the meeting room information.
* You can set whether the specified conference room is open for reservation in "Operation", and the conference room status will be displayed next to the name in real time.
## 2. Book a meeting room
* Open the APP > Schedule > \[+] > Select the meeting room > Select the scheduled date and time
* Meeting room reservation records can be seen in the schedule
---
# 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://docs.coreway.com/coreway-hr/admin-management/meeting-room-reservation.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.
