When a participant asks for their personal data to be deleted, treat it as a GDPR right-to-erasure request. Removing access is not always enough.
Confirm the scope of the request
First identify the participant and the email address they used in Knowly. Then clarify whether the request is about:
one learning journey
all learning journeys in one team
the whole Knowly organisation
every Knowly organisation your company uses
The deletion path depends on that scope.
Deletion is different from removal
Removing a participant from a learning journey stops their participation in that journey. Removing them from the organisation stops organisation-level access.
Deleting personal data is broader. It should remove or anonymize the personal information covered by the request according to your organisation's GDPR process.
If the person is still provisioned from your directory
If your organisation uses SCIM or another directory sync, update the identity provider first. Otherwise, the person may be added back to Knowly after you delete or remove them.
Bulk cleanup is a separate task
If you need to delete many old participants for GDPR housekeeping, use Bulk-deleting old participant data for GDPR housekeeping instead of handling each person as a separate one-off request.