NOTE:	SourceSystemId is considered a permanent identification method. To avoid the possibility of user error occurrences by staff who may not understand the significance of the field, it is not displayed in the application UI. Once a SourceSystemId is set for a record, it can only be changed through a support request to InEight or using Users_UpdateSourceSystemID API. The Users_UpdateSourceSystemID API allows users to edit and change SSIDs in one or multiple records using External System programmatically or through APIM manually. This API impacts Users_Import and Users_Get only. There is no restriction on the number of SSIDs that can be updated through this API. We have not put any validation in place to ensure that any user cannot update their own SSID through this API. Quite simply, the reason for this is that the SSID update happens at the service account level and is agnostic of individual persons... This is further explained below: The External System integrations use a SVC Account (ClientId/Secret) for all transactions (import/GET). So, irrespective of the user (person) or automated system triggering the import, they are processed in the context of a svc account. Hence, the CreatedById and ModifiedById audit columns in the database tables will have "1" (System Admin) if the entities are imported from External Systems.

NOTE:

SourceSystemId is considered a permanent identification method. To avoid the possibility of user error occurrences by staff who may not understand the significance of the field, it is not displayed in the application UI. Once a SourceSystemId is set for a record, it can only be changed through a support request to InEight or using Users_UpdateSourceSystemID API.

The Users_UpdateSourceSystemID API allows users to edit and change SSIDs in one or multiple records using External System programmatically or through APIM manually. This API impacts Users_Import and Users_Get only. There is no restriction on the number of SSIDs that can be updated through this API. We have not put any validation in place to ensure that any user cannot update their own SSID through this API. Quite simply, the reason for this is that the SSID update happens at the service account level and is agnostic of individual persons... This is further explained below:

The External System integrations use a SVC Account (ClientId/Secret) for all transactions (import/GET). So, irrespective of the user (person) or automated system triggering the import, they are processed in the context of a svc account. Hence, the CreatedById and ModifiedById audit columns in the database tables will have "1" (System Admin) if the entities are imported from External Systems.