When you're cleaning up many old participants for GDPR housekeeping, "delete" can mean two different things. Decide which one you need before you start:

They're separate actions with separate tools.

​

If you don't use directory sync, you can erase people straight from the organisation's people list. Select the people you want to remove, and a Delete button appears for the selected rows. Knowly asks you to confirm — Really delete {count} participants? — and warns that the participants and all their data are removed from every learning journey they're in and it can't be undone. Confirm with Yes, delete.

This erases the selected people and their data across the whole organisation, so it's the right path when the goal is to remove people for good.

If your organisation uses SCIM or another directory sync, the Delete button isn't there — Knowly hides it and blocks account deletion, because your identity provider owns those accounts. Remove or deprovision the people in your identity provider, and Knowly erases or suspends their data on the next sync. See directory sync with SCIM.

​

This is a different job: taking people out of the learning journeys they're enrolled in, without deleting their organisation account. It's the bulk version of removing a participant from a learning journey, not an account erasure.

If you enrolled the group through a dynamic list, you can do it by deleting that list. When you delete it, choose Delete list and remove participants which are added to learning journeys only via this list. That takes those people — and their answers in those journeys — out of the journeys they joined through the list, but only the ones who joined only through it. Anyone also enrolled another way stays put, and everyone keeps their organisation account.

​

Neither path is the same as deleting a learning journey. Deleting or archiving a journey does not necessarily erase all participant data across Knowly.

For a single named participant request, use deleting personal data on a participant's request.