In Thrive, user deletion is designed to support data privacy by removing personally identifiable information (PII) while preserving completion and activity records for reporting purposes.
There are three ways to delete a user profile:
API: Use the standard user management API endpoint with a
user_deletedcall.SCIM: Automatically triggered by your Identity Management System (IMS), such as Azure or Okta, depending on your organisation’s SCIM configuration.
Zapier: Using the
user_deletedcall in our Zapier API integration.
What Happens When a User Is Deleted?
Deleting a user in Thrive triggers a process designed to balance data privacy with organizational record-keeping. Here is how the system handles a deletion:
Automatic account deactivation: The system automatically deactivates the account when a user deletes their profile, instantly revoking all access to Thrive.
Profile obfuscation (hard delete): Upon receipt of an API or SCIM request, all personally identifiable information (PII) is hard deleted and removed from the user profile. This includes first name, last name, email address, reference ID, and similar identifiers.
Separation of learning records: Thrive maintains completion and activity records separately from personal profile data. While the identity is obfuscated, all learning activity and completion data are retained for reporting purposes.
No new account association: When a user account is deleted, the link between the user and their data is permanently severed. Any newly created account for the same individual can't be linked to the deleted account or associated with their previous learning content completions.
This approach ensures compliance with GDPR and other data privacy standards, especially in cases where a user leaves the organisation and requests deletion of their personal data.
Important Notes
This process performs a hard delete of personal information.
Once a user is deleted, their profile cannot be restored or viewed.
The only way to link a deleted user to their historic activity is by using their internal Thrive ID (e.g.
602a3ca697f01147dd56f7b3), which we recommend storing securely along with the user’s reference.
Example: Provision and Manage User Accounts via API
