        HELP
        /
        PARTICIPANTS
        /
        TOTAL DELETE: WHAT IT REMOVES
      

Total Delete: what it removes

Total Delete strips a participant of every bundle enrolment, certificate, attendance record and course completion your dashboard holds for them — everywhere at your clients, not just one bundle. Read this before you confirm it: it cannot be undone.

        6 MIN READ
        UPDATED 4 AUG 2026
        DASHBOARD → PARTICIPANTS
      

BEFORE YOU START

Names aren't unique. Before confirming anything, check the email, phone number or guest code shown under the participant's name in the confirmation modal — it's the only reliable way to know you have the right person, especially if two participants share a name.

Start the confirmation flow

1

On the Participants list, choose the black Total Delete (Cleanup everything) button in the row's actions.

2

The Total Delete Confirmation modal opens and fetches a live impact report before you can confirm anything, showing "Calculating impact..." while it loads.

3

Under The following items will be removed from your dashboard:, the report lists — only for whatever actually applies — a registrations count with the affected bundles and courses named, plus counts of certificates, attendance entries and completions. If there's genuinely nothing on file, it says "No active registrations found."

4

Read the notice below the list, in full: "This includes certificates, attendance, and all progress. This action cannot be undone."

5

Choose Confirm Total Delete to proceed, or Cancel to close the modal without changing anything.

screenshot — Total Delete Confirmation modal, with the impact report and notice

The report is calculated fresh each time you open the modal, not cached from an earlier view.

What gets deleted

Everything below is removed for every client you own that this participant touches — in practice, since a participant record belongs to a single client, that's simply everywhere this person exists on your dashboard.

BUNDLE ENROLMENTS Every bundle participation record, along with its attendance log entries and its generated bundle certificate file.

COURSE SESSIONS Every course session, along with its completions (quiz results/progress) and its generated course certificate file.

CERTIFICATES The actual generated PDF files behind both of the above, deleted from disk.

ATTENDANCE Every check-in/check-out row tied to a bundle enrolment that's being deleted.

A COMMON MISTAKE

Expecting the participant to vanish from your list entirely. Total Delete removes their history — bundles, courses, certificates, attendance, completions — but not the underlying participant record itself. After confirming, they can still appear on the Participants list at this client, now showing no bundles and no completed courses.

Why this is different from removing one bundle

Assign and remove bundles only clears one bundle's own attendance and certificate; the participant, their other bundles, and their course completions stay exactly as they were. Total Delete has no such limit — it walks every bundle enrolment and every course session this participant has, at every client you own, and clears all of it in one action with no partial undo.

If something isn't working

"Error loading deletion details."

The live report failed to load. Close the modal, refresh the page, and open Total Delete again — it recalculates every time.

The report says "No active registrations found" but I can see them in a bundle

The report only ever counts clients your own admin account owns. If the bundle you're thinking of belongs to a client you don't have access to, it won't be reflected here.

The participant still shows up after Total Delete

Expected — see "A common mistake" above. Their history is gone; their identity record stays. Add them to a bundle again if you want them active, or ignore the empty row if you were only trying to clear their data.

What next

If you only meant to clear one bundle rather than everything, there's a smaller, reversible action for that instead.

Assign and remove bundles

Create a participant

Did this help?

Yes

Not really