Anonymization checklist

To ensure that anonymizing a user does not adversely impact your system, you must remove all references to the user. 

Before you anonymize a user, review the checklist and complete the required investigations and actions:

Is the user an owner of request offerings? The owner will need to be reassigned, otherwise, requests will fail.

Is the user the creator of an integration? You will receive the following message when archiving an integration user: You are not allowed to archive the user participating in Integration configurations. Update the integration user before proceeding.

Is the user being retrieved in an integration? In this case, the user could be created again. Make sure to delete the user in the target system.

 Is the user referenced in workflows? For example, if the user's email was added as a recipient to a notify, scheduled report, or decision block, this will need to be updated as this information is not anonymized. 

Is the user a Point of Contact for a stockroom or the Approver of an audit? These users will appear as anonymized when viewed in Oomnitza. Make sure to update this information to maintain data quality. 

Hard coded references to the user are still visible. For example:

If the user is referenced in a saved search.

 If the user is referenced in a workflow block, such as an Update block, or text field, such as a Description.

If the user is listed as a software or contract user, they are automatically removed from the users page.

An API token assigned to an anonymized user will no longer be valid. References to the user are anonymised in the API token list view. However, you will need to delete the token to remove it from the view. 

Does the user have any accessories or assets that need to be returned? If the user is anonymized while they are assigned an asset or accessory, the asset or accessory is not returned to the stockroom, and the stockroom count isn't updated.

To anonymize users, you must have add, edit, archive, and delete permissions for users. See Granting role permissions.