> 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-meetings/securing-zoom-meetings-explainer.md).

# Zoom Meetings 安全说明

## 概述

通过原生的 Zoom Workplace 桌面应用程序、移动应用或 Zoom Room 体验 Zoom Meetings 效果最佳，但你也可以通过网页参加 Zoom 会议，作为拨入用户（通过电话拨入会议），或通过第三方会议室设备参加（Zoom 的会议室连接器允许基于 SIP/H.323 的视频会议设备）。本文档全面概述了你可以使用的可用设置和会议中功能，以帮助保护 Zoom Meetings，防止不受邀请的自动化会议工具。

Zoom App Marketplace 是你的资源，可用于访问并下载能够增强你的会议或事件 & 活动 &直播体验的应用和集成。其中的一些应用是机器人；借助某些集成和第三方服务，它们构成了自动化的会议工具。尽管自动化的会议工具旨在扩展并增强 Zoom Meetings 的体验，但它们的存在可能会通过对会议内媒体的录制引发不必要的数据访问。以下许多安全功能都具有逐个用户的控制选项，使 Zoom 用户能够管理自己会议的安全性；同时，你也会找到一些管理员级配置，供账户所有者和管理员使用，以便让整个账户中的会议更加安全。

您还可能会看到使用 Zoom Realtime Media Streams (RTMS) 的应用与传统应用并用或取而代之。Zoom Realtime Media Streams 是一款可供开发者在线使用的工具，可让他们创建的应用访问来自 Zoom Meetings 的实时视频、音频、转写文字和屏幕共享流。虽然 Zoom Realtime Media Streams 消除了对第三方机器人的需求，但管理员仍可使用 RTMS 专用的 设置 和会议中工具来优化安全性。

{% content-ref url="/pages/bb3fc6c5edb13ed71032e55591beaeb426c1dad6" %}
[以安全有效的方式使用自动会议工具](/technical-library/zh/zoom-workplace/zoom-meetings/securing-zoom-meetings-explainer/using-automated-meeting-tools-in-a-secure-and-effective-manner.md)
{% endcontent-ref %}

{% content-ref url="/pages/6c5d95293a0be458f7c2ea91cb6dac738216d437" %}
[自动化会议工具的管理设置](/technical-library/zh/zoom-workplace/zoom-meetings/securing-zoom-meetings-explainer/administrative-settings-for-automated-meeting-tools.md)
{% endcontent-ref %}

{% content-ref url="/pages/52d2d6f7929aa097e9a5a50fb1feacf1d7b8abf3" %}
[在您的 Zoom Meetings 中管理自动化工具和参会者](/technical-library/zh/zoom-workplace/zoom-meetings/securing-zoom-meetings-explainer/manage-automated-tools-and-participants-in-your-zoom-meetings.md)
{% endcontent-ref %}

{% content-ref url="/pages/96f2e8b9a1319ee5d8cb89a73b8eaa2dc29351c6" %}
[通过账户设置阻止未受邀请的自动会议工具和参会者](/technical-library/zh/zoom-workplace/zoom-meetings/securing-zoom-meetings-explainer/prevent-uninvited-automated-meeting-tools-and-participants-with-account-settings.md)
{% endcontent-ref %}

{% content-ref url="/pages/6afd843622e51837cef75ab959b60258d41915ee" %}
[会议的额外安全措施](/technical-library/zh/zoom-workplace/zoom-meetings/securing-zoom-meetings-explainer/additional-security-measures-for-meetings.md)
{% endcontent-ref %}

{% content-ref url="/pages/012a7d98dbc6e8bf4cc728ebb4a044a60fa6c0b9" %}
[Zoom 实时媒体流](/technical-library/zh/zoom-workplace/zoom-meetings/securing-zoom-meetings-explainer/zoom-realtime-media-streams.md)
{% endcontent-ref %}


---

# 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-meetings/securing-zoom-meetings-explainer.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.
