> 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-link-a-room-type-to-a-specific-room.md).
# How do I link a room type to a specific room?
To link a room type to a specific room, you must use the **Room Master** tool located in the Front Office module. This tool serves as the primary interface for creating rooms and associating them with their defined categories.
**Steps to Link a Room Type**
1. **Navigate to the Menu:** Go to **FRONT OFFICE > MASTERS > ROOMS > ROOM MASTER**.
2. **For a New Room:**
1. Click on **NEW** to begin creating a new room record.
2. Enter the room details and, in the provided field, add the corresponding **Room Type** from the list.
3. Click the **Save** icon to finalize the link.
3. **For an Existing Room:**
1. If you need to change the room type of an existing room, select the specific **room number** from the drop-down list.
2. Select the new **Room Type** from the corresponding drop-down menu.
3. Click **Save** to update the record.
**Important Considerations**
* **Modification Limits:** While the system allows you to change the **room type** associated with a room, you cannot change a room number once it has been created.
* **Deletion Policy:** A room cannot be deleted if it has already been referenced in any transactions.
* **Room Building:** During this process, you also have the option to link the room to a specific **Room Building** and enable the **sharer room** option if applicable.
---
# 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-link-a-room-type-to-a-specific-room.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.
.png?alt=media)