> 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-configure-the-room-feature-type-master.md).
# How do I configure the Room Feature Type master?
To configure the Room Feature Type master, which allows you to create a predefined set of amenities for your property, follow these steps:
1\. **Navigate to the Menu:** Go to the FRONT OFFICE module, select MASTERS, then ROOMS, and finally ROOM FEATURE.
2\. **Create a New Feature:** Click the NEW button.
3\. **Enter Details:** Create a unique ID and a name for the specific room feature (e.g., "Sea View" or "Mini Bar").
4\. **Save:** Click the Save button to store the new feature.
**Modifying Room Features**
* **Access the Feature:** To make changes, click the OPEN button and select the specific Feature ID you wish to amend.
* **Edit Constraints:** While modifying, the system only allows you to edit the name of the feature; the ID cannot be changed.
* **Finalize Changes:** Click the Save button once your modifications are complete.
Once these features are established in the master, they can be added to specific rooms within the Room Master tool or viewed in the footer of the Room Search Screen during reservation creation.
---
# 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-configure-the-room-feature-type-master.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.
