> 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/can-i-link-multiple-features-to-a-single-room-number.md).
# Can I link multiple features to a single room number?
Yes, you can link multiple features to a single room number in the system.
This process is managed within the Room Master tool by following these steps:
1. **Access the Master:** Navigate to **FRONT OFFICE > MASTERS > ROOMS > ROOM MASTER.**
2. **Select the Room:** Open a new room or select an existing one to modify its details.
3. **Add Multiple Features:**
* Locate the **"FEATURE DETAILS"** section at the bottom of the room configuration screen.
* Click the **search icon** to select a feature from your predefined list.
* To add additional features to the same room, click the plus icon (+) to create more rows and select more features.
4. **Manage Features:** If you need to remove a feature, you can use the delete icon next to the specific feature row.
5. **Finalise:** Click the Save icon to store the links.
Once these features are linked, they will automatically appear in the footer of the Room Search screen when that specific room is highlighted during the reservation process, helping staff identify room amenities at a glance. Please note that these features must first be created in the Room Feature master before they can be assigned to individual rooms.
---
# 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/can-i-link-multiple-features-to-a-single-room-number.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.
