The bin: undoing a delete

Nothing is destroyed by a single press. Deleting takes a copy of what the thing was made of and puts it in the bin; the thing itself goes, and it can come back. Because of that, Remove does not ask first: it happens at once, and "Removed. Undo" stands beside the list for ten seconds. Undo puts it straight back; after that, the bin is the way back.

It comes back whole

A restore puts back the rows the thing was made of, not an approximation of them: a module comes back with its people and its tasks, and an account with its files.

The bin holds a practice file, a task, a lesson, a resource, a module, a course, an account, a join link, a hand-in that was taken back, a VLE connection and a job. A deleted account is listed by its email address as well as its name, so you can tell two people of one name apart.

If something it belonged to was deleted too, the restore is refused whole and says so: put that back first, and then this. Each restore, and each Delete forever, is written to the admin log.

The access log and the admin log themselves are never in the bin and nothing removes a row from either, so deleting somebody’s work does not delete the record that it was looked at.

A few deletes ask first, in a box that names what will go, instead of offering Undo: deleting a cloud table, queue, row or message, a saved deployment, a passkey, a folder of resources or a whole cohort.

The bin can be searched: type part of a name, or of who it belonged to or who deleted it, and pick a kind from the list, which only offers kinds that are really in the bin. The result is an ordinary address, so a filtered bin can be sent to a colleague, and searching keeps you in the bin you were in.

The Deleted items page, listing a removed lesson with Put the lesson back and Delete forever beside it
Nothing is destroyed by one press. Put it back, or delete it forever on purpose.

Who may look is who could have deleted it

The bin cannot be a way round a permission: seeing an entry and restoring it ask the same questions the delete asked.

Nothing expires, and only a person deletes for good

Entries stay until somebody presses Delete forever, which is the second and final decision. Nothing sweeps the bin on a schedule.

Questions people ask

How long do I have to change my mind?
There is no time limit. An entry stays until somebody removes it deliberately.
Does restoring a module put the students back on it?
Yes, along with the tasks and who held them.