Resource Manager Operations Guide Working within a Multi-Tenancy Environment
494 Polycom, Inc.
You will need to use only local RealPresence Resource Manager system
users. To save time, you can import users into your RealPresence Resource
Manager system.
• Software updates cannot be assigned to an area.
• You must use dynamic provisioning when areas are enabled. Other
methods of endpoint provisioning are not supported. See “Using User
Group Provisioning Profiles” on page 243
• Polycom DMA systems, Polycom VBPs, and SBCs (Acme Packet Net-Net
Enterprise Session Director) are not area-aware, which means they cannot
be assigned to an area.
• Resources can belong to only one area, with the exception of DMA Pool
Orders. If you want to share network devices between areas, you can leave
them in no area.
• You can assign an area user an area role according to the tasks the user
needs to perform in the RealPresence Resource Manager system. Area
roles restrict user tasks to the area or areas in which they are allowed to
manage.
• Some system-wide administration tasks cannot be delegated to users with
only area-specific roles. These include site topology and conference
templates. System maintenance and set up must also be done by a user
with a system role.
Working within a Multi-Tenancy Environment
When using the RealPresence Resource Manager system’s area feature, most
aspects of the system become “area-aware” which means that management of
the system and conferencing tasks may become different according to the role
of the user.
The following aspects of the area feature are discussed in this topic:
• “User Roles within a Multi-Tenancy Environment” on page 495
• “Area Address Books” on page 497
• “Area User Groups” on page 497
• “Area Users, Rooms and Associated Endpoints” on page 498
• “Area Conference Guests” on page 498
• “Using the Common Pool in a Multi-Tenancy Environment” on page 498
• “Area Conference Templates” on page 498
