> 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/zoom-workplace/zoom-whiteboard/zoom-whiteboard-admin-experience.md).

# 管理員體驗

在整個組織中管理 Zoom Whiteboard 裝置、分類標籤和參與報告。

Zoom 白板為組織提供治理與可視性工具。本頁涵蓋裝置管理、分類標籤和參與報告。

### 裝置管理

#### <mark style="color:藍色;">使用 Zoom Admin Portal 管理使用者的白板啟用裝置</mark> <a href="#of09a02dub65" id="of09a02dub65"></a>

裝置管理功能可透過 Zoom Admin Portal 集中管理，為您提供強大的系統監督工具。這包括可遠端設定與更新組織內已啟用白板的裝置。此平台也提供細緻的存取與權限控制，可在帳戶與群組層級進行管理，為不同使用者族群啟用適當的安全性與功能設定。

### 資料分類標籤

#### <mark style="color:藍色;">資料分類標籤可為您的白板組織提供更強化的管理</mark>

管理員最多可以為貴組織中的所有看板建立及管理 30 個自訂資料分類標籤（此數量可能變更；詳情請參閱 [Zoom 支援](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0088264) ）。每個標籤包含：

* 敏感度層級與排名
* 以顏色區分的徽章，便於視覺識別
* 說明
* 可選的連結，指向您組織的資料處理準則

{% hint style="info" %}
**注意**

Zoom 對分類標籤中連結的任何第三方或客戶提供之準則內容不負責任。
{% endhint %}

分類徽章會直接顯示在儀表板與畫布上的白板中，因此團隊無需開啟白板即可快速識別其敏感度層級。

{% hint style="info" %}
**注意**

分類標籤由使用者套用，僅作為組織輔助工具。它們不構成技術存取控制，也不會強制執行資料安全政策。
{% endhint %}

白板擁有者、共同擁有者以及具有內容編輯權限的管理員，可透過白板標題列中的下拉選單套用標籤。管理員也可設定預設標籤，自動套用至所有新白板，並附帶可供團隊參閱的連結準則文件。


---

# 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/zoom-workplace/zoom-whiteboard/zoom-whiteboard-admin-experience.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.
