Remove a module with its consequences visible

A compliance trainer at a pharmacy chain must retire a module on paper log reconciliation now that the process is digital. Three learning paths still point to it, and more than a hundred technicians are mid-course. She needs to see every consequence before anything disappears, and she cannot lose anyone's history.

A removal proposal identifies the obsolete module and the learning paths that would need revision.

• Open the module in Creation Studio and choose Remove.
• Elvina lists the contained lessons, active assignments and every learning path that references the module.
• Read the recovery terms, then confirm as an authorized owner; the module moves to the trash.
• The Learning Platform keeps learner history and awards no completion for the removed content.

A fictional chain, Maple Street Pharmacy, operates 45 stores and a course called Controlled Substance Handling. The trainer removes the Paper Log Reconciliation module, which holds four lessons, appears in three learning paths and has 120 technicians in progress.

• The removal proposal named four lessons, three paths and the in-progress count before asking for confirmation.
• Two paths were revised to skip the module before the removal was confirmed.
• Technicians who had completed the old lessons kept those records.

Require an authorized confirmation; explain recovery. Do not silently remove learner history or award completion for deleted content.

• Every referencing learning path is listed.
• The in-progress learner count is shown.
• The recovery window is stated before confirmation.
• No completion is awarded for deleted content.
• The audit log records who confirmed and when.

Removal is never silent and never automatic. Elvina does not rewrite learning paths for you; it shows what would break so you fix it first. Learner history stays intact. Confirm your retention rules and who holds removal authority in a live workspace, and check whether a regulator expects the old module archived.