> For the complete documentation index, see [llms.txt](https://docs.interaktifotel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interaktifotel.com/zh-cn/zhu-su-she-shi-guan-li/structure.md).

# 住宿设施、楼层、客房与公寓

开放酒店分公司 个人资料,地板和房间定义.

![酒店分支和单位的定义](https://923543600-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFYpr3SG1RnMm4DANLHfW%2Fuploads%2Fgit-blob-1c3f48db0cfc367caee91477bee69e897a87d31f%2Fproperty.png?alt=media)

## 规划结构

级别是酒店 →酒店分支/分支 →楼层和单位. 一个单位可能是公寓,房间,宿舍或床. 房间可以属于公寓,床可以属于房间. 物理地板和主体单位是单独的关系;多层公寓内的房间可能位于不同层.

## 创建地板和单位

1. 选择酒店分支,然后打开地板和房间定义.
2. 设置地板代码,显示名称和顺序. 不要在同一酒店分店内重复使用地板代码.
3. 在单元表格中,选择公寓,房间或宿舍类型,并输入其代码.
4. 分配适当的楼层,如果需要的话,还要分配一个母体.
5. 在房间表格中填写租用方式的选择.
6. 添加实际的床家具,设施和库存信息.
7. 在定义列表中保存和检查单元以及相关操作视图.

## 租房或单人床?

| 选择   | 结果                      |
| ---- | ----------------------- |
| 整个房间 | 房间是预订单元;其实际床的家具描述了房间布局. |
| 个体床  | 连接的床位提供单独.              |

房间的租用模式也适用于后添加的床. 影响现有预订的变化可能会被阻止.

## 修改或删除定义

编辑记录,检查其地板和父母单位的任务. 如果结构变化会影响确认或活跃的预订,首先应适当地移动或考虑取消未登记的预订. 按照申请的验证,而不是绕过它.

对于批量操作,请查看所有选择的单元代码. 在对多个单元进行更改之前,检查过濾器和选定的行.

继续使用 [床和床](/zh-cn/zhu-su-she-shi-guan-li/beds.md) 和 [设施和库存](/zh-cn/zhu-su-she-shi-guan-li/amenities.md).


---

# 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.interaktifotel.com/zh-cn/zhu-su-she-shi-guan-li/structure.md?ask=<question>&goal=<user_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.