> 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-analytics-and-reporting.md).

# 分析和报表

审查组织模式并为报告工作流程准备汇总洞察。

使用 Zoom Whiteboard 分析来了解组织内的采用情况、协作和活动趋势。

### 使用情况和参与度

#### <mark style="color:蓝色;">监控并分析白板使用情况和参与度</mark>

管理员可以通过 Zoom 管理员门户访问 **白板管理员仪表板** ，监控其组织内的使用指标和参与度。该仪表板可展示白板创建率、活跃协作者以及整体参与度趋势，帮助管理员以数据为依据管理协作计划。

#### <mark style="color:蓝色;">跟踪参与和活动指标</mark>

白板参与度分析会展示用户参与模式，例如编辑频率、对象创建情况和团队协作密度。管理员可以导出汇总分析数据以便深入审查，也可以将其集成到内部报告系统中，用于跟踪生产力。管理员可以通过 Zoom 管理员门户访问白板使用分析和仪表板，以监督采用情况和参与度趋势，但须遵守适用的数据隐私法律以及 [Zoom 隐私声明](https://www.zoom.com/en/trust/privacy/privacy-statement/).

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

分析数据反映汇总的协作活动，不会显示个人内容或白板数据。管理员可以通过 Zoom 的账户级别隐私控制来管理可见性。
{% endhint %}

### 报告

#### <mark style="color:蓝色;">参与报告用于跟踪参会者和贡献者之间的互动情况</mark>

白板所有者和共同所有者可以生成参与报告，以跟踪白板协作会话中的参与情况。报告可通过看板活动日志和历史记录查看。

每份报告包括：

* **概览：** 汇总指标，包括参会者总数、有效贡献者人数和白板操作总数
* **参会者：** 按用户细分，区分有效贡献者（进行过更改的用户）和仅查看的参会者（打开白板但未执行任何操作的用户）
* **分析：** 使用趋势时间线视图，并提供可配置的排序选项

跟踪的操作包括添加对象、编辑内容、评论、删除项目和反应——每项操作都有时间戳。这让看板所有者和共同所有者无需单独的分析工具，就能了解谁在贡献以及如何贡献。


---

# 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-analytics-and-reporting.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.
