Start by separating work you want to keep from assets you have confirmed are no longer needed. An old last-updated date or a lack of recent pipeline use is a reason to investigate, not proof that an asset is unused.
1. Find the candidates
Open Workspace and use the sidebar search, Filter assets, and folder structure to focus on a project or asset type. Check the intended organisation and workspace before acting.
Look for experiments, duplicate outputs, superseded reports, and temporary imports. Open each candidate and identify its purpose, owner, and consumers.
You can ask Dawn for help with an inventory:
2. Check dependencies and recurring work
Before removing an asset, review pipelines, dashboards, reports, models, automations, and jobs that may use it. Include name-based references in SQL and any links shared with colleagues.
Pause or revise recurring work through its own controls before removing its inputs. Check active runs as well as future schedules. Do not assume removing a folder automatically retires every workflow that refers to its contents.
For pipelines, review their output datasets separately. A pipeline and the data it produced are distinct assets.
3. Organise the work you are keeping
Use Create → Folder to group related assets. Use descriptive names and bookmark frequently used work. An “Archive” folder can be a useful team convention, but it does not itself stop schedules, revoke access, or set a retention policy.
When moving or renaming assets, check downstream references. Dataset names used in SQL deserve particular care. Confirm any permission changes associated with a new location.
4. Move confirmed items to the Bin
- Right-click the selected item in Workspace and choose Delete.
- Read the confirmation dialog. Where the Bin is enabled, it describes Move to Bin.
- Check the items and underlying assets included, any folder contents, and any linked assets mentioned.
- Check the displayed permanent-deletion date, if there is one.
- Confirm only after the selection matches your intended cleanup.
Deleting a folder can include its contents. Linked promoted assets may also be affected; review any cross-environment warning in the dialog.
Read the action shown in your confirmation dialog. If it says Remove from workspace instead of Move to Bin, the underlying asset may remain and reappear after reindexing. Do not treat that operation as deletion of the underlying data or as a recoverable Bin operation.
5. Verify the remaining workspace
Open important downstream assets and check that they still work. Review the next scheduled run and confirm that removed work is not being recreated unintentionally.
For recovery or permanent removal, follow Bin and recovery. Revoking a source credential is a separate action from removing imported data; see permissions and credentials. 
