.. _associate-disassociate-devices-to-application-users:

Associate / disassociate devices to application users
---------------------------------------------------------

.. _19.3.4|EKB-6098:


High level admins can make available a utility to associate and disassociate devices to CUCM application users
so that it displays on administrator menus on the GUI. 

.. important::

   The utility is available only at site level, so that only devices and device profiles
   at that level are available for management.

The utility simplifies the association and disassociation of a large number of
Phones, CTI Route Points, or Device Profiles to app users (``device/cucm/AppUser``).
This would for example be in the case of large contact center deployments.

The model to expose on the administrator menu layout is ``view/AddRemoveDeviceAppUser``. 
Access Profile updates are needed for the default administrator access profiles.






1. Select an **Application User** to manage.

   The list of application users are those at and above the current site hierarchy.

   You can associate **Devices** and **Device Profiles** with the same application user by
   means of side-by-side transfer boxes.
2. Choose the **Action**: either to associate or disassociate devices or device profiles.

   * When associating, only devices or device profiles not associated to the user
     at the current hierarchy are shown in the **Available** transfer box.
   * When disassociating, only devices or device profiles associated to the user
     at the current hierarchy are shown in the **Available** transfer box.
3. Optionally, add a substring filter in the **Filter Devices** or **Filter Device Profiles**.
4. Manage the items in the **Available** and **Selected** transfer boxes.   

   .. note:: 

      The transfer boxes support up to 5000 initial results. More items may be available. In this case, 
      specify a case-insensitive *contains* search to filter results, even if the list contains more than 
      5000 results. 

5. Save your changes.

   Inspect the transaction log to verify the action. The **Detail** message
   includes the username of the app user.

.. note::

   A database lock is used in the resulting transaction in order to ensure parallel
   transactions do not conflict.
 

.. rubric:: Related topics 

.. raw:: html

   <p>For details on customizing menu layouts, see <a href="concepts-menu-layout.html">Create a Menu Layout</a>.</p>

.. raw:: latex

   For details on customizing menu layouts, see *Create a Menu Layout* in the 
   Core Feature Guide.