Trash
Trash in Blueputto is a recovery workspace for deleted records, with restore and permanent delete options, plus automatic retention cleanup.
Grzegorz
Trash is the recovery workspace for removed records in Blueputto. Instead of deleting something permanently on the first action, the app moves it into a separate holding area where teams can review, restore, or finally remove it.
That separation matters because operational cleanup is often reversible. Someone may delete the wrong item, remove a whole collection too early, or need a short buffer before committing to destructive cleanup.
Soft deletion comes first
Trash is built around the idea that removal and destruction are not the same thing.
In the current implementation, the main app view is centered on deleted items. Records moved here can come from:
single-item deletes,
bulk item deletes,
and collection-level cleanup actions.
The table keeps enough context to make recovery decisions practical. Teams can review the item name, its original collection, and the deletion timestamp before acting.
Restore and permanent delete stay separate
Each row in Trash has two clearly different outcomes:
restore the item,
or delete it permanently.
That split is important because recovery should stay easier than destructive cleanup. The page also supports permanent deletion for selected batches when a team is sure those records should be removed fully.
There is one practical nuance here: restore depends on the original collection still existing. If the collection is gone, the row stays visible, but the item can no longer return to its previous place automatically.
Retention is handled independently from cleanup
Trash is not meant to be a permanent archive. The workspace exists as a safety layer, and items are automatically removed after the retention period allowed by the active plan.
That makes the page useful for both day-to-day mistakes and planned cleanup. Teams get time to reverse a deletion, but they are not forced to manage every old trash record forever by hand.
