> 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/shang-ye-ban-fu-wu/zoom-contact-center/zoom-customer-experience/admin-experience/roles.md).

# Zoom 呼叫中心角色

Zoom 呼叫中心支持特定于该服务的用户角色，使账户管理员能够根据需要为用户提供访问 Zoom 呼叫中心功能的精确权限级别，而无需授予公司账户其他部分的更高访问权限。

{% hint style="warning" %}
**重要**\
最初，只有 Zoom 账户 **所有者** 将有权访问 Zoom 呼叫中心设置。每位用户 **必须** 先 [被分配一个 Zoom 呼叫中心许可证](/technical-library/zh/shang-ye-ban-fu-wu/zoom-contact-center/zoom-customer-experience/admin-experience/managing-and-assigning-user-licenses-entitlements-and-information.md) 之后才能获得该产品的角色访问权限。
{% endhint %}

默认情况下，有三个不可自定义且使用默认设置的角色；不过，如有必要，Zoom 呼叫中心管理员可以创建具有更精细访问权限的自定义角色。下表概述了该服务提供的默认角色：

<table><thead><tr><th width="200.13336181640625">角色名称</th><th>访问级别</th></tr></thead><tbody><tr><td>管理员</td><td>可在网页门户中访问或更改所有 Zoom 呼叫中心功能和设置，包括设置、分析、管理和角色成员资格。</td></tr><tr><td>主管</td><td>拥有部分用于访问和管理 Zoom 呼叫中心的权限；具体而言，对设置和分析的访问权限较低，除呼叫录音外无管理权限，并且不能更改用户的角色成员资格。</td></tr><tr><td>坐席</td><td>可以访问 Zoom 呼叫中心的核心交互功能，但没有管理、更改或编辑 Zoom 呼叫中心设置的权限。</td></tr></tbody></table>

\
更多信息，请参阅 Zoom 支持中心中的 [使用 Zoom 呼叫中心角色管理](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0061941).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://library.zoom.com/technical-library/zh/shang-ye-ban-fu-wu/zoom-contact-center/zoom-customer-experience/admin-experience/roles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.