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 |
|
Admin Portal Navigation (default menu): Customization > Global Settings (Enabled tab) |
Enable the service type at the user’s hierarchy level, or above. |
|
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). |
|
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. |
|
Admin Portal Configure multi vendor FDP: Navigation (default menu) Customizations > Field Display Policies |
Clone and edit the default multi vendor subscriber field display policy (default name: |
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 |
|
Result |
The site admin logs in to a multi vendor subscriber enabled system, at the relevant site hierarchy, and:
|
Related Topics