Users are created in a synchronization with LDAP or Cisco Unified CM, or they are created manually in the VOSS Automate. All users are created according to these duplicate username guidelines:

Quick Add Subscriber and Subscriber Management create Subscribers and users, while Manage Users and the Auto Push feature convert existing users into Subscribers.

Original source of the existing user	Action
LDAP	Simple user update, if the user is coming from the same LDAP server
Cisco Unified CM	Update user, update provisioning status with LDAP server and SyncTo info
Manually created	Update user, update provisioning status with LDAP server and SyncTo info

Original source of the existing user	Action
LDAP	User is not synchronized
Cisco Unified CM	Simple user update, if the user is coming from the same Cisco Unified CM server
Manually created	Update user, update provisioning status and SyncTo info with Unified CM server

Original source of the existing user	Action
LDAP	Update user, update provisioning status with Unified CM server (keep SyncTo info the same)
Cisco Unified CM	No action or updates are necessary
Manually created	Update user, update provisioning status with Unified CM server and update SyncTo to the Cisco Unified CM hierarchy if the current SyncTo is below it

Note

If a user cannot be created or updated during an LDAP or Unified CM synchronization, a log is created in User Management > Log Messages and the synchronization succeeds. If a user cannot be created or updated manually, an error message is generated.
If the duplicate user check fails, the transaction fails, and the user is not converted to a Subscriber.
If a user's SyncTo value is updated, SSO User updates can result. The SSO User's IDP is set to the IDP configured at the new SyncTo hierarchy node. If no IDP is configured at the new SyncTo hierarchy node, the SSO User is deleted, if it existed. If an IDP is configured at the new SyncTo hierarchy node, but no SSO User exists, an SSO User is created at the user's hierarchy node.
An update is blocked if two duplicate users are from the same source but originate from different servers.

Model Details: data/HcsUserManagementLogDAT

An asterisk * in the title indicates the field is mandatory.
If a field has a default value, it is shown in the Description column.
If the field type is an array, the Field Name has a .[n] suffix, where n is the array index placeholder.
Object and array field names are listed to provide context. If a field belongs to an object or an array, the full field name is shown in dot separated notation.

Title		Description	Details
Timestamp *		When the event occurred.	Field Name: timestamp Type: String MaxLength: 1024
Level *		Log level.	Field Name: level Type: String MaxLength: 1024 Choices: ["ERROR", "WARNING", "INFO"]
Component *		The name of the component.	Field Name: component Type: String MaxLength: 1024
Identifier *		An identifier that can be used to link this log with other entities in the system.	Field Name: identifier Type: String MaxLength: 1024
Message *		Message indicating why the log was generated.	Field Name: message Type: String MaxLength: 1024
	Recommended Action(s)		Field Name: actions.[n] Type: Array
	Details		Field Name: details.[n] Type: Array

Model: data/HcsUserManagementLogDAT

Log Messages

Model Details: data/HcsUserManagementLogDAT