Adding is_forgotten to the user payload for the user_profile_changed event.
While unfortunately not in the API docs for the user_profile_changed event, there are two steps for removing a user from a workspace:
"Deactivate" (in the UI) - sets the profile to deleted=true, admin can reactivate the profile later
"Delete" (in the UI) - sets the profile to is_forgotten=true and overwrites all PII fields of the profile with placeholder values like "Deactivated User" (for GDPR-related reasons)
It does not actually delete the user object, and you will see the is_forgotten flag set to true which is part of the GDPR system used to ensure that the user can't be re-activated by an admin and that their accounts and profile are permanently gone.
Otherwise, if a user has just been deactivated, but not had their profile scrubbed, they will show up as "deleted: true".
Adding
is_forgotten
to the user payload for theuser_profile_changed
event.While unfortunately not in the API docs for the
user_profile_changed
event, there are two steps for removing a user from a workspace:deleted=true
, admin can reactivate the profile lateris_forgotten=true
and overwrites all PII fields of the profile with placeholder values like "Deactivated User" (for GDPR-related reasons)Confirmed with Slack support:
Examples event payloads: Deactivate:
Delete: