> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/technical-library/zh-tw/guan-li-yuan-zhuan-qu/account-and-endpoint-management/new-groups-and-settings-management-experience-explainer/considerations.md).

# 考量事項

檢視 SAML 與 SCIM 對應、API 支援，以及目前細項設定選擇限制等主要考量事項。

### 關於新的群組與設定管理體驗，需留意的事項

#### <mark style="color:藍色;">SAML 對應具有權威性，並會在每次登入時將使用者從未匹配的群組中移除</mark>

當設定了 SAML 對應時——無論是否啟用多重對應——它都會成為群組成員資格的權威來源。每次登入時，SAML 斷言會決定群組指派，而使用者會從任何未被該斷言匹配的群組中移除。對同一位使用者，無法同時混用手動與基於 SAML 的群組指派。若組織使用 SAML 對應來管理群組，則應將其套用於所有 SAML 對應使用者的群組指派。

#### <mark style="color:藍色;">SCIM 和 SAML 多重對應不應設定為互相衝突的群組資訊</mark>

雖然 SCIM 群組推送與 SAML 多重對應可以在同一帳戶上共存，但不應設定為互相衝突的群組指派。如果 SCIM 和 SAML 將使用者指派到不同群組，這兩種機制就會發生衝突。SCIM 更新會在身分識別提供者變更後的一小時內發生，而 SAML 則需要使用者再次登入。就時間順序而言，如果兩者都在處理同一項變更，SCIM 很可能會優先。

#### <mark style="color:藍色;">Groups API 仍完全相容</mark>

現有的 Groups API 與新的體驗在舊版作業上仍完全相容，包括使用者指派、群組建立與群組清單。新體驗中新增的功能，包括群組複製、優先順序管理與細緻的設定組態，目前僅能透過 Admin console 網頁 UI 使用。

#### <mark style="color:藍色;">多個主要設定區域皆可使用逐項設定選擇</mark>

目前可在下列主要設定區域中，針對產品類別進行個別設定選擇：

* AI 助理
* 音訊會議
* 一般
* 會議
* 錄音與逐字稿
* 網路研討會


---

# 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://library.zoom.com/technical-library/zh-tw/guan-li-yuan-zhuan-qu/account-and-endpoint-management/new-groups-and-settings-management-experience-explainer/considerations.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.