> 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-she-ding-jian-an-de-jin-jie-zi-liao-jian-an-ming-cheng-zhi-zhao-qu-de-ri-jie-dai-zhong-xin-di.md).

# 如何設定建案的進階資料（建案名稱、執照取得日、接待中心地址等）？

#### **路徑：**

建案管理 > 建案設定 > 基本資訊

***

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

1. 前往 基本資訊 頁面：選擇建案後，進入 **建案管理 > 建案設定 > 基本資訊** 。

   <div align="center"><figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2F9pKo3qHPzek58JozAGYa%2Fnote%20(1).jpg?alt=media&amp;token=84a627ee-15b2-467a-af0f-c3377b9daba4" alt="" width="563"><figcaption></figcaption></figure></div>
2. 填寫與上傳建案資料：請依序填寫或上傳以下資料，
   1. 建案封面：點擊 **上傳圖片** 按鈕。（建議尺寸為 400 x 600 px，支援 jpg, jpeg, png, tiff 格式。）
   2. 建案名稱：輸入此建案的完整名稱，例如：「文華寓所」。
   3. 使用執照取得日：點擊日曆圖示，選擇建案取得使用執照的日期。
   4. 建築執照取得日：點擊日曆圖示，選擇建案取得建築執照的日期。
   5. 接待中心地址：輸入建案接待中心的詳細地址。
   6. 接待中心電話：輸入可供聯絡的電話號碼。<br>

      <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2Fa56aJkGUlB5Iu0GAhp4M%2F%E6%88%AA%E5%9C%96%202025-09-09%2015.37.26.png?alt=media&amp;token=8cebca67-51a8-4f93-9c73-e7053dfa5c65" alt="" width="563"><figcaption></figcaption></figure>
3. 確認所有資訊都填寫正確後，點擊右下方，綠色的 **儲存** 按鈕，即可完成所有設定。


---

# 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-she-ding-jian-an-de-jin-jie-zi-liao-jian-an-ming-cheng-zhi-zhao-qu-de-ri-jie-dai-zhong-xin-di.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.