Delete content and folders

Delete removes content you no longer need. Use Archive for a Guide, Form, or Course you may need to restore later.

Deleted folders, Guides, files, and templates have no Library Restore action. Export or copy what you need before deleting. Check the item's identity and location carefully: an eligible empty folder can be deleted immediately.

Access requirements

Deletion checks your folder permissions and the operation's requirements. A read-only workspace does not necessarily prevent supported cleanup, but viewing an item alone is insufficient. Root folders cannot be deleted.

Delete a file or template

1. Choose Delete from the item's actions menu.
2. Review the confirmation.
3. Select Delete file or Delete template.

Deleting a reusable template does not delete the original Guide tree it came from. Retained history and assets still referenced elsewhere can remain; deletion does not guarantee that every associated stored byte disappears.

Delete a Guide

1. Open its actions menu and select Delete.
2. Wait for the impact check.
3. Review Blocking impact and the other deletion and audit effects.
4. Select Delete if the impact permits it.

Submitted Reports are retained. Unsubmitted Reports and sessions without a retained Report are removed. Retained sessions lose live runtime state; remaining active sessions are ended. A person's Next Guide reference to this Guide is cleared. Guide-owned assets are queued for background cleanup according to remaining use. Guide deletion can finish before that cleanup completes; it does not confirm that every stored file has already been removed.

A linked schedule can block deletion. Resolve the listed dependency before trying again; archiving has different consequences.

Delete a folder tree

An eligible empty folder disappears immediately after Delete, without a second confirmation. A nonempty folder opens an impact review:

1. Review the nested items, retained history, and blocking dependencies.
2. Select Delete recursively only if that impact is acceptable.

The job removes nested folders, Guides, files, and templates and cancels active uploads. Forms and Courses are archived and moved to the surviving parent folder. Submitted history is retained; referenced assets can also be preserved.

The dialog shows background progress. Closing it does not cancel deletion. While the app continues observing the job, completion refreshes Library and returns you to an available parent if your current folder was removed.

If deletion is blocked or progress fails

Follow the impact list. Schedules and a person's Next Guide reference can block recursive folder deletion; the latter differs from deleting one Guide.

If progress monitoring reports a connection error, do not assume the job stopped or rolled back. Reconnect and refresh Library to inspect the result before starting another deletion. If the job itself fails, read its error, resolve the listed dependency or access problem, and review the impact again.