.. _user-sync-source:

User sync source
-------------------

.. _20.1.1|VOSS-551:


Overview 
..............

VOSS provides a list of applications from which to sync user data
and internally maintains a sync precedence hierarchy of these applications
in order to determine the master sync source.

Application:

* MS_LDAP              
* OPEN_LDAP            
* LDAP                 
* CUCM                 
* CUC                  
* AVAYA_SYSTEM_MANAGER 
* BROADWORKS                            
* MICROSOFT            
* MS_365               
* PEXIP                
* UCCX                 
* WEBEX_TEAMS          
* ZOOM                 
* MS_TEAMS             
* LOCAL                


Users are typically added or updated on VOSS from the sync source, such as LDAP, Cisco UCM (CUCM), or CUC. 

.. rubric:: Sync source precedence 

Sync source precedence may override user input. If you update a user on VOSS and the following 
conditions exist, mapped fields are updated from the sync source (the fields are read-only in VOSS): 

* Exists on a sync source
* Has mapped fields
* Has a higher precedence than LOCAL (Automate) data 


Updating and then saving a user in VOSS triggers a sync with the application highest on the *User Sync Source* precedence, and 
according to the field mapping for that sync source.

* :ref:`add-user-sync-scenarios`
* :ref:`update-user-sync-scenarios`
* :ref:`ldap-add-sync-scenarios`
* :ref:`ldap-update-delete-sync-scenarios`


.. image:: /src/images/view-user-sync-source.png 



.. rubric:: Related topics

* :ref:`user-field-mapping`
* :ref:`add-user-sync-scenarios`
* :ref:`update-user-sync-scenarios`
* :ref:`ldap-add-sync-scenarios`
* :ref:`ldap-update-delete-sync-scenarios`