> 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-tw/zhu-su-she-shi-guan-li/structure.md).

# 住宿設施、樓層、客房與公寓

開放酒店分公司 個人資料,地板和房間定義.

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

## 規劃結構

級別是酒店 →酒店分支/分支 →樓層和單位. 一個單位可能是公寓,房間,宿舍或床. 房間可以屬於公寓,床可以屬於房間. 物理地板和主體單位是單獨的關係;多層公寓內的房間可能位於不同層.

## 建立地板和單位

1. 選擇酒店分支,然後開啟地板和房間定義.
2. 設定地板程式碼,顯示名稱和順序. 不要在同一酒店分店內重複使用地板程式碼.
3. 在單元表格中,選擇公寓,房間或宿舍型別,並輸入其程式碼.
4. 分配適當的樓層,如果需要的話,還要分配一個母體.
5. 在房間表格中填寫租用方式的選擇.
6. 新增實際的床傢俱,設施和庫存資訊.
7. 在定義列表中儲存和檢查單元以及相關操作檢視.

## 租房或單人床?

| 選擇   | 結果                      |
| ---- | ----------------------- |
| 整個房間 | 房間是預訂單元;其實際床的傢俱描述了房間佈局. |
| 個體床  | 連線的床位提供單獨.              |

房間的租用模式也適用於後新增的床. 影響現有預訂的變化可能會被阻止.

## 修改或刪除定義

編輯記錄,檢查其地板和父母單位的任務. 如果結構變化會影響確認或活躍的預訂,首先應適當地移動或考慮取消未登記的預訂. 按照申請的驗證,而不是繞過它.

對於批次操作,請檢視所有選擇的單元程式碼. 在對多個單元進行更改之前,檢查過濾器和選定的行.

繼續使用 [床和床](/zh-tw/zhu-su-she-shi-guan-li/beds.md) 和 [設施和庫存](/zh-tw/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-tw/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.