> For the complete documentation index, see [llms.txt](https://quteng.gitbook.io/ke-hu-wen-da-ji/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quteng.gitbook.io/ke-hu-wen-da-ji/kai-shi-shi-yong/yi-jian-an-diao-zheng/ru-he-xin-zeng-fang-xing-ge-ju.md).

# 如何新增 房型 / 格局？

#### **路徑：**

建案管理 > 建案設定 > 房型/格局管理

***

#### **操作方式：**

1. 前往 房型/格局管理 頁面：選擇建案後，進入 **建案管理 > 建案設定 > 房型/格局管理**。<br>

   <div align="center"><figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2F1TWa8xOEwHyh8IEA8T17%2Fimage.png?alt=media&amp;token=ff780fef-c08f-4191-a75e-dfd2e667ce34" alt="" width="563"><figcaption></figcaption></figure></div>
2. 在「房型/格局管理」頁面的左上方，點擊綠色的 **+ 新增房型格局** 按鈕。

   <div align="center"><figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FlovmKtoQ6317NxjssWqR%2Fimage.png?alt=media&amp;token=534ac357-1290-4a2b-a329-a9da9c4f62b5" alt="" width="375"><figcaption></figcaption></figure></div>
3. 填寫房型詳細資料：在彈出視窗中，依序填寫以下欄位，並上傳平面圖，
   1. 房型名稱：為此格局命名，例如 「兩房一廳」或「A2戶」。
   2. 坪數資訊：分別填入權狀、主建坪、附屬建坪、共有坪數。
   3. 平面圖：點擊「上傳圖片」按鈕，選擇格局圖檔。

      <div align="center"><figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FUppzO6hQatEAZMP3FGmX%2F%E6%88%AA%E5%9C%96%202025-09-09%2011.42.46.png?alt=media&amp;token=255c872c-4ac6-4cc0-b851-3a6e182c0087" alt="" width="458"><figcaption></figcaption></figure></div>
4. 確認所有資料填寫無誤後，點擊視窗底部的 **儲存** 按鈕，即可完成新增。


---

# 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://quteng.gitbook.io/ke-hu-wen-da-ji/kai-shi-shi-yong/yi-jian-an-diao-zheng/ru-he-xin-zeng-fang-xing-ge-ju.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.