On this page

Role-based Access for Multi Vendor Subscribers

Overview

Role access profiles define the permissions that allow subscribers to access services and resources.

Validation Checks

When provisioning multi vendor services, the system runs validation checks for multi vendor subscriber against each of four tiers in the system, at the relevant hierarchy. The service must be enabled at each tier before the system allows access to the service:

Validation

Interface

Description

  1. Global Settings

Admin Portal

Navigation (default menu): Customization > Global Settings (Enabled tab)

Enable the service type at the user’s hierarchy level, or above.

  1. Entitlement profile

Admin Portal

Navigation (default menu): Entitlement > Profiles

Enable the service in the entitlement profile assigned to the subscriber, at the relevant site. Services can only be provisioned to a subscriber if their entitlement profile allows those services. The entitlement profile lists the provisioning vendor (per service).

  1. Device management

Admin Portal

Navigation (default menu): Apps Management > Servers

The relevant servers must be installed and configured before a service can be provisioned. For example, a CUCM server must be installed before CUCM services, such as phones, can be provisioned. If you have two or more vendors provisioning devices, VOSS Automate verifies that the required servers and devices are configured and available for your system.

  1. Field display policy

Admin Portal

Configure multi vendor FDP:

Navigation (default menu) Customizations > Field Display Policies

Enable multi vendor in the Business Admin Portal profile:

Navigation (default menu) Customizations > Business Admin Portal Profiles

Clone and edit the default multi vendor subscriber field display policy (default name: MultiVendorFDP).

Enable multi vendor in the Business Admin Portal profile (Base/Details tab, and Subscribers tab), and select the multi vendor FDP to define the services the subscriber can view and manage in the Business AdminPortal lists, dashboards, and service management screens.

Multi Vendor Subscriber Access Validation Example

In this example scenario, a customer admin (or higher) provides a user with site admin role with the ability to view and edit subscriber voice services. The customer admin wants to control the actions the site admin may perform.

  • Only the Cisco Voice service is enabled for this site admin

  • The site admin may edit subscriber services

  • The site admin may not add or delete subscriber services

The table describes the configuration steps to set up this scenario, and the result:

Configuration steps

  1. Ensure the system has multi vendor subscriber functionality installed.

  2. At customer level or above, in the Global Settings (Enabled Services tab), enable CUCM only.

  3. In the Entitlement Profile for this user, enable CUCM Voice Service only.

  4. At site level, select Multi Vendor Enabled for the Business Admin Portal access profile for subscribers, and choose the multi vendor subscriber field display policy (default name: MultiVendorFDP)

  5. At site level, configure the multi vendor subscriber field display policy for the profile:

    • Remove all service cards except Voice.

    • Remove Add/Delete fields from the Quick Actions panel.

Result

The site admin logs in to a multi vendor subscriber enabled system, at the relevant site hierarchy, and:

  • Can view subscriber voice services in the Business Admin Portal.

  • Is unable to add or delete services. Only Edit is available in the Quick Actions

Related Topics

previous

Configure Multi Vendor Subscribers

next

Multi Vendor Subscriber Field Display Policy