.. _audit_user_data:

Audit
-----

Use this procedure to audit user data for SyncTo, User Type, LDAP and CUCM Audit,
and Subscriber at the selected hierarchy node. The following checks and corrections
are performed:

1. Check for duplicate usernames. Warning messages are logged in
   **User Management > Log Messages**. For more information about duplicate
   usernames, see :ref:`managing_duplicate_usernames`.
#. Check SyncTo settings. If the SyncTo setting is incorrect and the user is not
   a duplicate, the SyncTo setting is updated.
#. Check SSO User settings. If the SSO User setting is not correct based on the
   SyncTo setting and the user is not a duplicate, the SSO User is updated.
#. Check User Type settings. If the User Type is incorrect, it will be updated.



Provisioning Status (CUCM, LDAP and SyncTo)
...........................................

Use this procedure to identify if the right SyncTo value is set for a given user,
and to identify scenarios where the user provisioning status has invalid values.

1. Log in as a provider, reseller, or customer administrator.
#. Choose **Audit > Audit User Data**.
#. Choose a Hierarchy node.

   We recommended to run at Site hierarchy for a better performance.
   
#. In the **Provisioning Status (CUCM, LDAP and SyncTo)** area, from the **Options**
   drop-down, choose either Off, Report Only or Report & Fix.
#. Select the **Log to Transactions Only** check box to get audit data only in
   transaction logs not as Audit Report.
#. Click **Save**.


User Type
.........

Use this procedure to identify if the right user type is set for a given
user and fix if required.

1. Log in as a provider, reseller, or customer administrator.
#. Choose **Audit > Audit User Data**.
#. Choose a Hierarchy node.

   We recommended to run at Site hierarchy for a better performance.
   
#. In the **User Type** area, from the **Options** drop-down, choose either Off,
   Report Only or Report & Fix.
#. Select the **Log to Transactions Only** check box to get audit data only in
   transaction logs not as Audit Report.
#. Click **Save**.


Subscriber
..........

Use this procedure to get report to identify scenarios where the
subscriber is found with no corresponding user.

1. Log in as a provider, reseller, or customer administrator.
#. Choose **Audit > Audit User Data**
#. Choose a Hierarchy node.

   We recommended to run at Site hierarchy for a better performance.

#. In the **Subscriber** area, from the **Options** drop-down, choose either Off,
   Report Only or Report & Fix.
#. Select the **Log to Transactions Only** check box to get audit data only in
   transaction logs not as Audit Report.
#. Click **Save**.


Audit Report
............

If you have not selected the **Log to Transactions Only** check box, then the Audit
Report gets created per user basis if there is any discrepancy.

You can view the reports under **Audit > Audit Report**.

You can also export the report to ``.xls`` and ``.json`` format.

Choose **Administration Tools > Transaction** to view the transaction log.
Click the **Hcs Audit User Sync To View** transaction to open it. For example, the
message indicates:

* The number of users found at or below the hierarchy node.
* The number of duplicate users detected.
* The number of SyncTo corrections made.
* The number of SSO User corrections made.