Scheduling jobs with Multi Tenancy

When the Multi Tenancy feature is enabled you cannot schedule the following operations:

• Clear amw

• Delete station

• Delete agent

• Delete announcement

• Backing up announcements

• Backing up all announcements

• Restoring announcements

• Restoring all announcements

• Moving announcements

• Broadcasting announcements

• Bulk operations including adding stations in bulk, deleting stations in bulk, adding agents in bulk, deleting agents in bulk, editing agents in bulk

• Global endpoint change

Tenant administrators cannot delete Communication Manager objects in System Manager. To assign delete permissions to a tenant administrator, the Service Provider Administrator must provide delete and scheduler permissions to the tenant administrator.

This will not impact the current implementation of Element Cut Through, notify sync, and adding Off PBX entries for a SIP station.

User Provisioning Rule and Multi Tenancy

When you assign a user provisioning rule to a tenant, the same Communication Manager element must be present in User Provisioning Rule and Elements tabs. If the Communication Manager element that you selected is available in the User Provisioning Rule tab but unavailable in the Elements tab, the tenant creation fails.

When you create a new tenant, the system validates the tenant number based on the Communication Manager that you selected. Depending on the tenant configuration in the Communication Manager you selected, you can choose a tenant number between 1 to 100 or 1 to 250.

User Management and Multi Tenancy

When you enable the Multi Tenancy feature, and you choose the tenant and site for a user in User Management, the system displays Communication Manager System in the endpoint agent communication profile sections based on the tenant and site values you selected in the Identity tab. The User Management values override the values selected on the Multi Tenancy dashboard.

The system displays the available extensions in the endpoint, agent communication profile sections according to the tenant and Communication Manager permissions.

Field level permissions and Multi Tenancy

Apart from the tenant permissions, object-level and field-level permissions are also valid for the tenant hierarchies. For example, admin A with access to Tenant Partition 1 can modify hunt-group 12 in Tenant Partition 1, but admin A cannot assign a station in Tenant Partition 2 to that hunt group.

• Do not provide Element Cut-Through access for a tenant administrator, because the administrator can bypass the tenant restrictions.

• In the Tenant Management web console, when the tenant administrator assigns a single number or a range in the Tenant Number field, the Communication Manager that the administrator selects is associated with the tenants.

  The Tenant Number field is autopopulated for the Communication Manager objects that you create through Communication Manager. In the Tenant Number field, you can specify only the values or range that you configured in System Manager. If you specify a range, the system uses the smallest value in the tenant range. This scenario is also valid when you create Communication Manager objects such as endpoints or agents using User Management or Directory Synchronization.

• When you create tenants, if you specify the location, then you can enter only valid values. Location can be a single number, a range, or blank. When you enable multi-location field in System-Parameters customer-options, the availabe values for the Location Number field are 1 to 250 for Communication Manager 6.0 and 6.2, and 1 to 2000 for Communication Manager 6.3 and later. You must type blank or leave the Location field blank to choose blank as a value for tenant objects. For example, to specify blank and the range 1 to 10, you must type blank,1:10 in the Location field.

• When you change or select a template, the Tenant Number in the template takes precedence over the smallest, default tenant value. This scenario is valid only if the tenant number present in the template is within the valid tenant range. Otherwise, the system uses the smallest value in the specified tenant range. The value in the Location field specified in the template also takes precedence over the default value. The system validates against incorrect and out of range values.