.. _task-configure-multi-vendor-subscribers:

Enable multi vendor users
-------------------------------------

.. _21.4-PB2|VOSS-1214|EKB-15985:


.. tip:: 

   :ref:`use-action-search-to-navigate-automate`



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.


.. rubric:: Related topics

*
  .. raw:: latex

     Manage users in the Core Feature Guide

  .. raw:: html

     <a href="manage-users.html">Manage users</a> 

*
  .. raw:: latex

     Global Settings

  .. raw:: html

     <a href="concepts-global-settings.html">Global Settings</a> 

* :ref:`configure-qa-for-mv-subscriber`



Step 1: Enable multi vendor users in global settings
............................................................


1. Log in to the Admin Portal.

#. 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. 

#. Go to **Global Settings**. 
#. On the **Enabled Services** tab, enable services, as required.
#. 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: :ref:`manage-users` and :ref:`quick-add-subscriber-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.