Welcome!
-
-
- Learn Home
- Core Concepts
- Companies and Departments
- Courses
- Course Status and Visibility
- Modules
- Video Activities
- Reading Activities
- Document Activities
- Enrolling People in a Course
- Bulk Enroll With CSV
- Roles in a Course
- How Progress Is Tracked
- Course Reports
- Knowledge Base Overview
- Libraries and Folders
- Uploading Content Items
- Library Visibility
- AI Agent per Library
- My Courses
- Platform People
-
- Project Structure Template
- Table of Contents (TOC)
- Content Folder
- Introduction to Markdown
- Markdown Basics
- Markdown Lists
- Markdown Links
- Markdown Images
- Markdown Code
- Markdown Tables
- Markdown Equations
- Markdown Videos
- Markdown Embedded HTML
- VS Code Snippets
- Introduction to Styles
- Framed Narrations
- Markdown Configuration
- Editor Setup
-
-
-
Purge
TL;DR; Purge is permanent deletion with no restore path — different from the trash, which always has one. It's platform-owner only everywhere it appears, and both Knowledge Base purge and course purge require a deliberate step first: the item has to already be in the trash, or the course already archived.
Before you start
For Knowledge Base content, see Trash, restore and the 30-day window — a library, folder, or file has to be in the trash before it can be purged.
Steps
Purging a library, folder, or file only works on something already sitting in the trash — purge refuses anything still live. Delete permanently is the button; each confirmation names exactly what's about to happen and ends with "It cannot be undone." — for a library, it also reminds you that "only soft-deleted libraries can be purged." Purging a file also removes its blob from storage and drops it from the AI search index, on top of removing the database row.
Purging a course requires two things first: the course must already be Archived, and it must have zero enrolled learners. If people are still enrolled, the refusal names how many, because purging would erase their progress, quiz attempts and certificates for good, and tells you to move them to another course first. The confirmation shows the real course title so you're confirming against the name, not just an ID, and warns plainly: "This permanently removes the course and everything inside it — modules, lessons, activities, transcripts, enrollments, progress and chat history."
Purging a course removes, in one pass: every enrollment, every quiz attempt and answer, every activity-progress record, every issued certificate, the course's own audit trail, its modules, lessons and activities, its chat history, and any course-scoped role assignments — then the course row itself. Files that were uploaded as activity assets are cleaned up afterward.
What this doesn't do
Purge is not the same action as the everyday Delete most people use — that one is the soft-delete described in Trash, restore and the 30-day window, and it's always reversible within its window. Purge is what happens after that, or what a platform owner does directly when something needs to be gone immediately.
Neither Knowledge Base purge nor course purge has an undo, a trash, or a restore path once it runs. There's no confirmation beyond the one dialog — there's no second warning, no "are you really sure," and no audit record that lets anyone bring the content back.
Common issues
Purge is refusing to run. — For Knowledge Base content, it isn't in the trash yet; delete it first. For a course, it either isn't Archived yet or still has enrolled learners — the message tells you which, and moving learners to another course is required before a course with any enrollment can be purged.