Storage, old versions, and Trash

Open Settings → Storage & Trash to inspect storage and the available cleanup actions. Check the selected owner/workspace; organization and personal storage can have different limits.

Find what uses space

Inspect the breakdown and project entries before removing anything. Video, audio, images, documents, library assets, and brief attachments can contribute to usage according to their storage context.

An individual-file limit is different from total storage. A small upload can fail when the workspace is full, while a large file can fail its own size or content-type limit even when plenty of storage remains.

Clean up old versions

Use the cleanup action offered for eligible approved projects to move older versions to Trash. Review what the action will retain and what it will move before confirming.

Keeping the approved release is different from keeping every working iteration. Coordinate cleanup if the team still needs an old draft’s source file or review context.

Restore from Trash

Open the relevant project or brief attachment in the Trash area and use Restore when offered. Wait for confirmation and check that the restored material is available in its source context.

If restoring would exceed a limit or access is read-only, resolve that account condition first. A deleted external Dropbox or YouTube copy doesn’t return merely because a Stago version was restored.

Permanent removal

Emptying Trash or confirming a permanent-delete action removes the ability to restore through the normal UI. Read the confirmation, keep any needed delivery material, and verify the selected project or file.

Moving material to Trash may not immediately free storage; follow the usage and cleanup explanation shown by Stago. Don’t repeatedly delete more work because a usage summary hasn’t refreshed yet.

For reusable library files, remove their active attachments before deleting them in the File Library. Deleting a folder, a stage, and a project have different scopes.