Remove a participant from your organisation when the person should no longer have organisation-level access to Knowly. This is different from removing someone from one learning journey.
Organisation removal or journey removal
Remove someone from a learning journey when they should only leave that journey. Their organisation account and other learning journeys can remain.
Remove someone from the organisation when they have left the company, were added by mistake at directory level, or should no longer have Knowly access at all.
If your organisation uses directory sync
If your organisation uses SCIM or another directory setup, your identity provider controls who has Knowly access — so remove or unassign the person there. Knowly picks up the change from the directory and removes their access.
While directory sync is on, you can't remove a directory-managed person from inside Knowly; that's handled by the directory. See Directory sync with SCIM for how directory sync manages access.
Personal data and GDPR requests
Removing a participant from the organisation is an access change. It is not always the same as deleting personal data.
If the person has asked for their personal data to be deleted, use Deleting personal data on a participant's request instead. That helps you handle the right-to-erasure request rather than only removing access.