User Management; User Roles (Authorization Levels) And Permissions; Managing Users - Polycom RealPresence 1800 Administration Manual

User Management

This section provides an introduction to the user management options, functionality, and operations
associated with the RealPresence Collaboration Server. It includes these topics:
● User Roles and Permissions
● Managing Users
User Roles (Authorization Levels) and
Permissions
The RealPresence Collaboration Server (also called the MCU) includes a default set of user roles or
authorization levels. Each role is associated with a unique set of permissions that allow a user with that role
to perform a set of tasks.
This following table identifies the default system user roles or authorization levels.
Role
Administrator
Administrator Read-only
Operator
Chairperson
Auditor

Managing Users

Only users assigned the administrator role can manage RealPresence Collaboration Server users. Some
of these management tasks include:
Polycom, Inc.
Description
A full administrator can define and delete other users and perform all configuration and
maintenance tasks.
The RealPresence Collaboration Server ships with a default Administrator user called
POLYCOM, whose password is POLYCOM. However, once you have defined other
authorized Administrator users, it is recommended to remove the default user.
An administrator with read-only permissions has the same viewing and monitoring
permissions as a full administrator and a read-only administrator can create system
backups. However, a read-only administrator cannot perform any other configuration-
or conference-related operation.
An operator can manage meeting rooms, profiles, entry queues, and SIP factories. An
operator can also view the system configuration, but cannot change it.
A chairperson can manage active conferences and participants in both single and
cascading MCU scenarios. The chairperson does not have any access to the system
configurations and utilities.
An Auditor can only view Auditor Files and audit the system.
98