[Index]

Model: relation/MultiVendorSubscriber

Manage Users

Full HTML Help

Overview

VOSS supports multi vendor users, which allows you to provision and manage services from one or more vendors on the VOSS platform. For example, to use both Microsoft meeting and collaboration tools and Cisco tools.

Related topics

Enable multi vendor users in the Core Feature Guide

Global Settings

Role-based access for multi vendor users in the Core Feature Guide

Entitlement in the Core Feature Guide

• User Call Settings
• Microsoft Exchange
• User Voicemail Settings
• Access Profile Permissions and Operations
• Reserve a Number for a User

Single vendor and multi vendor users

VOSS supports provisioning for a number of categories of user, representing either a single or multi vendor deployment:

Example: Multi vendor user with Cisco services

Example: Multi vendor user with Microsoft Teams

Example: Multi vendor user's user calling and voicemail settings

Example: Multi vendor user's headset settings

Example: Multi vendor user - Cisco Webex App User with Webex Calling Professional license, showing Cisco Webex App User Calling Settings

Update multi vendor users

This procedure displays the summary list view of users (Microsoft, Cisco, Webex) and updates users and their services.

1. Go to Users & Services, then, choose an option:

   • User Overview: A dashboard displaying a summary of totals for users in the system.
   • User Details: A dashboard displaying a summary of services, and service details by vendor (Microsoft, Cisco, Webex, as relevant for your system).
   • Microsoft User Services: A dashboard for viewing and managing Microsoft users, if relevant for your system.
   • Webex User Services: A dashboard for viewing and managing Webex users, if relevant for your system.
   • Cisco User Services: A dashboard for viewing and managing Cisco users, if relevant for your system.

2. Go to Manage Users. Choose an option:

   Note

   The list view uses an [OR] condition to filter users: End User[OR]End User + Admin

   For details on the filter, see: Ordering Lists.

   • Microsoft users: Go to Microsoft User Services, then, in the Quick Actions, select Manage Users.
   • Webex users: Go to Webex User Services, then, in the Quick Actions, select Manage Users.
   • Cisco users: Go to Cisco User Services, then, in the Quick Actions, select Manage Users.

   Note

   Quick Actions for multi vendor user are defined via the Multi Vendor FDP (MultiVendorFDP) in the field display policy (FDP) for the page. See Enable multi vendor users.

   For details around the available quick actions for multi vendor user, the user type they apply to, and the impact of changes via the Quick Actions, see:

   • Configure Quick Actions for multi vendor users
   • Quick Actions for multi vendor users

3. On the Manage Users [username] page, you can view and update the user details and services, or delete the user.

   Note

   • To add a user, see System User Details.
   • To move a user, see Move user and services.

   • Delete users: You can delete one or more users from the list view, or delete the user from their management page.

     • Non-Microsoft multi vendor user: deletes the user along with their services
     • Microsoft multi vendor user: deletes the user along with their services, and offboards the user (removes their license)
     • If applicable, the user's hybrid status is updated
     • LDAP or MS365 users: The system user is retained.
     • Hybrid multi vendor user with MS365 elements: Moves the user and their Microsoft models to the customer level. See Hybrid Cisco-Microsoft Conversion.
     • Bottom-up LDAP multi vendor user: Deletes device/cucm/User and data/User
     • Top-down LDAP user: Deletes the user, retains data/User and device/ldap user instances
     • Microsoft provisioned user: Retains data/User if there is an associated Microsoft user

   • Update user:

     • Choose an entitlement profile

     • View and manage phones and lines

       Note

       For users with associated softphones, the phone product model name displays below the Phone icon on the cards. This is useful where the user has multiple phones and you need to easily distinguish between different phone models.

     • View and manage the user's existing, enabled services, which may include Microsoft user calling settings, Microsoft voicemail settings, Microsoft Teams, Cisco Webex, Cisco Voicemail, and other enabled services.

       • For users with multiple remote destinations associated to their single number reach (SNR), the Cisco Single Number Reach card on the management page displays only the first associated SNR remote destination profile and the first associated remote destination to that SNR.

       • For users licensed with a Webex Calling Professional license, the following cards display:

         • Webex Devices: Devices available to the user
         • Webex Voicemail: If the Voicemail setting is enabled, options for sendAllCalls, sendBusyCalls, sendUnansweredCalls, edit link to Voicemail
         • Webex Calling Settings: Barge In, Caller ID, Call Forward, Call Recording, Call Waiting, Intercept, edit link to Calling Settings

         The image shows users with Webex App, and how they show up in the list view and on their configuration details page:

Related topics

• Hybrid Cisco-Microsoft Conversion
• Single Number Reach
• Voicemail
• User Call Settings (Microsoft users)
• System User Details
• Move user and services
• Configure Quick Actions for multi vendor users
• Quick Actions for multi vendor users

Multi vendor user service icons

The table describes caveats for icons in the Services column of the multi vendor user list view:

Merge two users into a single multi vendor user

VOSS provides a merge tool for consolidating duplicate user accounts from two different vendors (two data/User instances with the same email address) that have been imported from different vendors, into a single, Cisco-Microsoft multi vendor user.

This case is required where you have imported two user accounts from different vendors, for example, Cisco and Microsoft, and you add or update their email addresses to the same email address. In this case, the merge tool workflow (Merge_Relation_User workflow) is triggered when it finds the duplicate email address for the two data/User instances.

You can use the view for the merge tool (view/ConsolidateUsers) to define the primary user (which is retained once merged), and the secondary user (which is deleted once merged). The services of the secondary user will then be merged into the primary user.

When consolidating these two accounts, the default provisioning workflow of the merge tool (ConsolidateUsers) copies details of the secondary user into the primary user, and moves any device models associated with the secondary user to the hierarchy of the primary user:

• Copies the username (Cisco or Microsoft) of the secondary user to the primary user
• Copies the Zoom username of the secondary user to the primary user
• Copies the email address of the secondary user to the primary user
• Copies the email address to the Cisco user, if the primary Cisco UCM user is local
• Deletes the secondary user (the data/User instance of the secondary user

Once successfully merged, a log entry is added to data/HcsUserManagementLogDAT, and the primary user is assigned a system username, as a multi vendor user.

Quick actions for multi vendor user

Quick actions allow you to easily access frequently used activities, for example, to reset a PIN or password, or to add a user. Multi vendor user includes a set of quick actions that are configured via the multi vendor user field display policy (MultiVendorFDP; fallback FDP is default).

Quick actions added to the MultiVendorFDP field display policy (FDP) appear as links on the Quick Actions card on the management page of the selected multi vendor user.

While some quick actions are also available as stand-alone features or functionality that can be accessed via a menu or dashboard link (or via the Search bar), other quick actions, such as Update User (Cisco UCM), are only available as a quick action.

The availability of a quick action also depends on the user type or the environment, for example, Cisco or Microsoft, multi vendor or hybrid. You'll also require appropriate permissions on your access profile to have some quick actions available to you. By default, the access profiles that ship with the system (except for Operator access profiles) have read, write, and export permissions on all multi vendor user quick actions and service card actions that are views, for example, view/DeleteCucmHuntGroupAllMembers (quick action, Remove from all Hunt Groups), view/DeleteSubscriberService (quick action Delete all services), or view/AddExtensionMobility (service card action, Add Extension Mobility).

Quick action links trigger the following behavior in the system:

• Some quick actions, such as Update User (Cisco UCM), are only available as a quick action link that launches a dialog (or overlay) on the current page, and allows you to perform a specific action (related to the quick action).

• Some quick actions are shortcuts to a menu or dashboard for the feature, such as the Cisco Quick User or Microsoft Quick User link, which opens the Quick Add User page directly from the quick link.

• In some cases, the quick action launches a dialog (or overlay) on the current page for performing a specific action related to the quick action, such as Add to Hunt Group or Remove from All Hunt Groups, while the full functionality for the feature is also available via a menu or dashboard.

  In this case, you may also access the functionality via the menu (or fill out the feature name, for example, Hunt Groups, in the Admin Portal Search bar, and press Enter to locate the page).

Related topics

• Access Profile Permissions and Operations

Enable multi vendor users

Full HTML Help

Overview

This procedure enables and sets up multi vendor users, and involves the following tasks:

• Enable relevant Global Settings.
• Configure the multi vendor field display policy (MultiVendorFDP).
• Configure entitlement profiles.
• Verify that you have appropriate servers installed and configured.

Related topics

Manage users in the Core Feature Guide

Global Settings

• Configure Quick Actions for multi vendor users

Step 1: Enable multi vendor users in global settings

1. Log in to the Admin Portal.

2. Select the hierarchy.

   Note

   The global setting to enable multi-vendor is typically defined at the customer hierarchy, although it may be enabled/disabled at any level.

3. Go to Global Settings.

4. On the Enabled Services tab, enable services, as required.

5. Save your changes.

   Note

   For new installs of Automate, once a Cisco UCM is imported and a customer hierarchy and some sites have been created, UCM services are enabled by default at system level; other services must be enabled, as required. The Global Settings are retained on upgrade.

Step 2: Configure multi vendor user field display policy

1. In the Admin Portal, go to Field Display Policies.

2. Click on the default multi vendor field display policy (MultiVendorFDP) to open its editing screen.

3. Click the toolbar Clone icon to create a copy of the default FDP.

   Note

   • It is recommended that you clone default templates rather than overwriting default settings.
   • The multi vendor FDP is associated with the model relation/MultiVendorSubscriber.

4. Edit the cloned multi vendor FDP for your requirements:

   • To add a new card, click the Plus icon (+); then, configure the card.

   • To delete a card, click the Minus icon (-).

   • To edit a card, click the down-arrow on the card to display editing options:

     • Click Move Up or Move Down to rearrange the position of cards.

       Note

       It is recommended that you leave the User Details card and the Quick Actions in their default positions at the top of the dashboard.

     • Change card titles.

     • Choose whether to display the card as a fieldset with columns.

     • Define the actions you require in the Quick Actions.

     • Add fields to a card by selecting and moving fields from Available to Selected.

     • Remove fields by selecting and moving fields from Selected to Available.

     Important

     Select valid fields for the model (allowed services). Only valid fields will display on the service cards once you apply the FDP.

     The view/DeleteSubscriberService access profile entry controls Delete quick actions across all subscriber service panels. If you intend to hide a specific Delete quick action in a given service panel, do not remove view/DeleteSubscriberService from the access profile since that will hide all related Delete actions. Instead, remove the corresponding Delete field from the MultiVendorFDP (model: relation/MultiVendorSubscriber) in Field Display Policies. This hides only that specific Delete action on the user's Quick Actions/service card while preserving other Delete actions.

     Check the field naming convention when choosing fields, for example:

     • Field names prefixed account_information are valid for the User Details card.

     • Field names prefixed cisco_webex are valid for Webex.

     • Multi vendor field name formats, such as mvs_user_qa, where:

       • mvs is the alias for multi vendor user*
       • _qa is Quick Action

       For example, the mvs_user_qa.qa_update_group_membership field allows for the Update Group Membership quick action which opens a transfer box containing a list of MS 365 groups that can be assigned to or removed from the user. If the MS 365 groups have licenses assigned to them, these will then also respectively be applied to or removed from the user. See also the Quick Add Group assigned to the user: Manage users and Quick Add Groups.

       If a service or action is disallowed in the global settings, entitlement profile, or if required servers are not installed for the service, the system verification check does not allow display of the service or action on the User management dashboard (defined via the FDP), and the user cannot be provisioned with this service. For example, if the Microsoft service is disabled in Global Services, then Microsoft-related quick actions such as Quick Add, User Staging, and Offboard User are not available.

5. Save your changes.

Step 3: (Optional) Configure entitlement profiles for multi vendor

1. In the Admin Portal, go to Profiles.
2. Click on the relevant entitlement profile to open its editing screen.
3. Select the services you wish to enable for the profile.
4. Save your changes.

Step 4: Verify servers

To verify that you have the appropriate servers installed and configured:

1. In the Admin Portal, go to UCM Servers.
2. Select the relevant server.
3. Repeat this step to verify the presence of all required servers.

Multi Vendor Subscriber Edit Relation

Model Details: relation/MultiVendorSubscriber