Deleting an experience moves it to the **Bin** rather than destroying
it. From there you can restore it whole — scenes, pins, contexts,
versions and all.

## Files go there too

Deleting a picture, a video or a sound from the asset library bins it
the same way, and restoring puts it back in your library with its file.
Deleting one used to take the file off the disk in the same action, and
since an upload is re-encoded on the way in and the original is not
kept, that was the only copy of it anywhere.

The two halves of the Bin are scoped differently, and the page says so:
**experiences belong to the workspace you are in**, so another
workspace's deletions are in its own bin, while **files belong to your
organisation's library** and are all in one place. A binned file does
not count towards your storage while it waits.

## Nodes go there too

Deleting a **scene**, a **cover** or a **page** bins it as well, and
restoring puts it back with everything that was on it — its pins, the
content on those pins, its own blocks, its pin groups and the links
other nodes made to it. Nodes are listed under their own heading, each
naming the experience it came from, because "North wall" on its own is
not something anybody recognises.

> Only whole experiences and library files reach the Bin. Everything smaller is deleted there and then, and version history is the only way back.

## ⚠️ Pins and blocks are a different way back

A **pin**, a **block** or a **pin group** does not appear in the Bin,
and that is not because it is gone. Press **Ctrl+Z** in the editor and
it comes back — a pin with its content, a group with the pins that
were in it. See [Undo a change in the
editor](/support/articles/undo-a-change-in-the-editor).

The difference is where you would look. A pin you deleted a moment ago
is an editing mistake, so the answer is in the editor; a node or an
experience is something you might notice tomorrow, so the answer is a
page that is still there tomorrow.

⚠️ **Undo does not survive the tab.** Close the editor, or open a
different node, and both arrows empty. If you deleted a pin yesterday,
the way back is restoring a version you published before you deleted
it — which replaces the whole draft, so it is a heavy answer to a small
problem. **Publish early**, even a half-finished experience nobody has
the link to, and you always have one.

## How long it stays

Your organisation has a retention window. It can be a number of days,
or "keep indefinitely". Once the window passes, a nightly job removes
binned experiences permanently, along with their published files.

The window is set for your organisation by Panova rather than on your
own settings screen, so ask us if you need it changed — this is not a
control you will find on your settings page, even as an organisation
admin. Where nothing has been set for you, the platform default
applies.

## What restore brings back

Restoring returns exactly what deleting took, and nothing else. An
experience comes back with everything that was inside it when it went
in, and a node with everything that was on it. Anything you had already
deleted separately, before you binned the thing above it, was gone at
that point and does not return with it — a pin you removed and then a
node you removed are two decisions, and restoring the node only undoes
the second.

⚠️ **A node whose experience is also in the Bin is not listed.**
Restore the experience first and its nodes come back on it; putting a
node back into a deleted experience would give you something nothing
can open.

## Permanent deletion

Deleting from the Bin is final. There is no second bin, and for a file
it is the point at which the bytes go. If you have emptied it by
mistake, tell us the same day.