> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/front-office-module/fo-masters/faq-on-masters/how-do-i-define-a-new-room-type.md).
# How do I define a new Room Type?
To define a new Room Type, you must access the Room Type master within the Front Office module. This master allows you to categorise rooms and configure specific parameters like occupancy limits and overbooking rules.
**Follow these steps to create a new Room Type:**
1. **Navigate to the Menu:** Go to the **FRONT OFFICE** module, select **MASTERS,** then **ROOMS**, and click on **ROOM TYPE** followed by **NEW.**
2. **Configure Occupancy:** Enter the maximum count of persons permitted for the category. You can set these limits separately for adults and children.
3. **Set Overbooking Rules:** If the property allows for more bookings than physical rooms for this category, enable the overbooking option, enter the allowed percentage, and select the required parameter.
4. **Additional Configurations:**
* Enter the total count of maximum allotted persons per room if specific restrictions apply.
* Enable the Paymaster type checkbox if this room type is being created for internal or clearing purposes.
* Mention any specific room facilities associated with this category.
5. **Finalize:** Click the Save icon to create the room type.
Once a Room Type is defined, you can link it to specific room numbers within the Room Master tool.
---
# 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://help.rbsgo.com/front-office-module/fo-masters/faq-on-masters/how-do-i-define-a-new-room-type.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.
