.. _system-user-details: System User Details ---------------------- .. _20.1.1|VOSS-551|EKB-4798: .. _20.1.1|VOSS-551|EKB-7522: .. _21.4-PB5|VOSS-1261: .. _25.1|EKB-22116: .. _25.4|EKB-27248: .. tip:: :ref:`use-action-search-to-navigate-automate` Overview .............. The **System User Details** list view (``relation/User``) displays users at or below the current hierarchy node. Users can be created in the system in various ways, depending on your setup: * Synced in from LDAP and promoted to a user * Synced in from applications (for example, Voicemail or Conferencing) * Added to Automate when creating an end user * Added to Automate when creating an admin user User creation can also vary across different hierarchies in the system. .. note:: A system user can be associated with multiple vendor services, each of which may use a different username or identifier. Vendor-specific usernames (for example Cisco UCM, Cisco Unity Connection, Microsoft 365, Microsoft Teams, or Webex usernames) are maintained automatically by provisioning and import workflows based on the user's sync source and service associations. These vendor-specific usernames are read-only on the System User Details page. They reflect the authoritative identity values received from the associated vendor systems. Note the following user details: +-------------------------------+-------------------------------------------------------------------------------------------------------------+ | **Sync Source** | The source application of user data, for example: | | | | | | **LOCAL** indicates that the user has been manually created in Automate and has not been synced from LDAP | | | or from Cisco Unified Communications Manager (Cisco UCM). | | | | | | **UCM** indicates that the user exists on both Automate and Cisco UCM, and is not synced from LDAP. | | | The user may have been created first on Automate (top-down) or created on UCM and synced | | | into Automate (bottom-up). | | | | +-------------------------------+-------------------------------------------------------------------------------------------------------------+ | **Sync Type** | Identifies the user that was synced from a device as indicated by **Sync Source** according to a type. | | | The setting is read-only and assists in for example distinguishing LDAP sync users (bottom-up UCM-LDAP or | | | or top-down LDAP). Example values: | | | | | | * **UCM-Local**: if the sync source is **UCM** and user is synced from Cisco UCM | | | * **UCM-LDAP**: if the sync source is **UCM** and user is LDAP synced | | | * **LDAP**: if the sync source is **LDAP** and user is LDAP synced | | | * **LOCAL**: sync source is LOCAL | +-------------------------------+-------------------------------------------------------------------------------------------------------------+ | **User Type** | Administrators (**Admin**) who are users accessing the system in order to perform administrative activities | | | | | | End users (**End User**) that will be set up with services in the system. | | | | | | Users with multiple roles (**End User + Admin**) [#]_ | +-------------------------------+-------------------------------------------------------------------------------------------------------------+ | **Auth Method** | See: User Authentication Methods [#]_ | +-------------------------------+-------------------------------------------------------------------------------------------------------------+ | **License Audit Status** [#]_ | From release_21.4-PB5 onwards, the results of the last license counting | | | process can be viewed as a **License Audit Status** field | | | or when viewing a specific user. When viewing a | | | specific user, the linked services details will indicate the services | | | the user is consuming for further details. The license status field | | | will indicate if the user is: | | | | | | - Licensed - consuming a license | | | - Unlicensed - not consuming a license | | | - Unknown - status has not been determined yet - typically means the | | | user was added since the last calculation was run | | | | +-------------------------------+-------------------------------------------------------------------------------------------------------------+ .. [#] **User Type**: see: :ref:`role-based-access-admins`. .. [#] **Auth Method**: see: :ref:`user-authentication-methods`. .. [#] This column will only show after the first run of the license-audit-service. See the Licensing and Subscriber Data Export Guide. * Click on a user to view its details. See also: :ref:`check-user-provisioning-status`. * Click **Add** to add a user manually. * You can filter the **Users** list view via the toolbar **Filter** icon, then select the field (attribute), condition, and a filter value. The list view returns only those users matching the attributes you specified. For example, you may want to filter the list to display only users with authorized admin hierarchy set up. View a system user's details ................................ On the **System User Details** page (``relation/User``) you can select a UC vendor user (Microsoft, Cisco, or Webex) to view and manage their user details (including their authorized admin hierarchy and sync source), their account information, license audit details, their provisioning and hybrid status, their contact details, and their services. .. image:: /src/images/webex-user-services-system-user-details-view-user.png