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

# 管理员体验

管理您组织中的 Zoom Whiteboard 设备、分类标签和参与报告。

Zoom Whiteboard 为组织提供治理和可见性工具。本页面介绍设备管理、分类标签和参与情况报告。

### 设备管理

#### <mark style="color:蓝色;">使用 Zoom 管理员门户来管理用户的启用白板的设备</mark> <a href="#of09a02dub65" id="of09a02dub65"></a>

设备管理功能通过 Zoom 管理员门户集中化提供，为您提供强大的系统管理工具。这包括您可远程配置并更新组织内支持白板的设备。该平台对您的访问和权限提供细粒度控制，可在账户和群组层面进行管理，以便为不同用户群组选择合适的安全性和功能。

### 数据分类标签

#### <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/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.
