> 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/hu-bie-yu-she-ding/yuan-gong-app-tong-zhi-zi-ding-yi-tong-zhi-dui-xiang-she-ding.md).

# 員工App通知 - 自訂義通知對象設定

#### **路徑：**

建案管理 > 通知設定 > 通知信管理

***

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

1. 前往 通知信管理 頁面：登入系統，選擇建案，進入 **建案管理 > 通知設定 > 通知信管理** 頁面。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FOfWLc4cccnR5RG0ndMk3%2Fnote_v2.jpg?alt=media&amp;token=b8563bb0-5588-415a-a2f4-1d78cbedb737" alt="" width="563"><figcaption></figcaption></figure>
2. 針對個別通知設定通知對象（以驗屋通知為例）：點擊畫面右上方綠色 **編輯** 按鈕，
   1. 選擇 驗屋系統
   2. 選擇 員工通知
   3. 編輯 App通知對象，通知對象皆可複選。

      <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FQWNAMMMqViG0uen3p5yv%2Fimage.png?alt=media&amp;token=1ce766b0-18af-4eb7-95c8-5f9043f6751e" alt="" width="563"><figcaption></figcaption></figure>
3. 通知對象範圍說明：
   1. 通知部門：該建案內所有部門員工
   2. 通知員工：該建案內所有員工
   3. 通知負責人：該建案負責人，包含建案、工務、售服。
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/hu-bie-yu-she-ding/yuan-gong-app-tong-zhi-zi-ding-yi-tong-zhi-dui-xiang-she-ding.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.