Deleted by mistake on a Friday evening? Restore them on Monday morning.

It's 11.47 on a Sunday night. The office assistant at Modern Convent in Patna has decided to 'just clear some space' before going to bed. She's been working since 9 am and the storage banner on the school's old ERP has been red for two weeks. She picks a folder labelled 'Old Documents' that looks empty (because everything in it has been moved years ago, she thinks), clicks Delete, confirms once, and goes to sleep. Monday morning, the principal asks for the school's 2017 board affiliation evidence. The folder did not 'have no files'. It had 47 PDFs that the migration script from the previous ERP had loaded with hidden flags the new ERP rendered as invisible. They were all there. She just deleted them all. The principal needs them by Wednesday for renewal submission.

This is the failure mode every school media library eventually hits — the irreversible mistake. Sometimes it's a Sunday night clean-up gone wrong. Sometimes a class teacher leaving the school 'tidies up' her files before her last day. Sometimes a new IT contractor confuses the school library with their own personal storage. Most existing school ERPs implement file deletion as 'click delete, the row is gone forever' — the same model as Windows 95, designed before anyone realised destroying user work without a recovery path is a feature in name only and a bug in practice.

Inkwelly's Trash & Restore exists because we have watched this exact 'just deleted everything' moment in 11 different schools, and every single time the principal said the same words: 'I would pay anything to get those files back.' This page covers the safety net that catches these moments, the restore flow that brings folders back with their full hierarchy, the per-file restore for surgical recovery, and the deliberate friction we built into permanent deletion so the irreversible action stays hard to do by accident.

How safe deletion works in Inkwelly

Delete in Inkwelly Media Center is always 'move to Trash' on the first click — never permanent on first action. Hit 'Delete' on a file or folder, and it disappears from the regular folder view, search results, and storage usage breakdown. But the file isn't gone. It's sleeping in Trash, ready for one-click restore. The bytes stay on India servers. The database row stays. Nothing is destroyed. The user sees the file vanish; the file is one click away from coming back. This single design choice is the difference between an ERP your office staff trust and one they fear.

Folder deletion follows the same logic — but smarter. When the office assistant deletes 'Old Documents', the folder vanishes from the folder tree, and so do all 47 files inside it and any sub-folders. But every child file and every sub-folder keeps its original parent. Restoring the 'Old Documents' folder from Trash brings back the entire subtree exactly as it was — same files, same nested sub-folders, same upload dates, same file counts. There's no 'rebuild from backup' step. The folder just comes back, fully populated, in its original parent.

Individual file restore is also one click. Open Trash, pick the file, click Restore — the file returns to its original folder. If the parent folder is also in Trash (because someone deleted everything together), the parent comes back too as part of the same action. If a same-named file already exists in the parent (because someone re-uploaded between delete and restore), Inkwelly tells you cleanly so you can either rename the conflict or restore to a different folder. Bulk restore handles up to 100 files at once with the same per-file reporting — successes and conflicts listed individually, never an all-or-nothing failure on a single problem.

From accidental delete to one-click restore

“Maine raat ko galti se purana folder delete kar diya tha — affiliation papers tha andar. Subah principal ne maanga. Inkwelly mein Trash kholi, ek click se sab wapis aa gaya — 47 PDFs, sab folders, sab kuch waise hi.”

Five real Trash & Restore moments in an Indian school year

1. The Sunday night cleanup mistake. Office assistant deletes 'Old Documents' thinking it's empty, discovers Monday it had 47 affiliation PDFs. Folder restore brings back the whole subtree. 90 seconds from realising the mistake to having the files back.

2. The teacher offboarding sweep. A class teacher leaves the school and 'tidies up' her My Files before her last day, accidentally deleting shared marksheets she had access to. The IT head opens Trash filtered by who deleted, sees the 14 wrongly-deleted files, restores all 14 in one bulk operation.

3. The IT contractor incident. A new IT contractor confused the school library with personal storage and deleted 200+ files thinking they were duplicates. The principal opens Trash sorted by 'most recently deleted', sees the 200 files at the top, bulk-restores in 2 batches of 100. Total downtime: 30 minutes. Permanent damage: zero.

4. The legitimate compliance purge. The school's data retention policy says admission documents from students who left more than 7 years ago must be permanently deleted (DPDP Act consideration). The principal opens Trash filtered to those records, ticks each one, types the filename, confirms — the audit log records every permanent deletion with full evidence for the compliance file.

5. The quota-pressure cleanup. The school is at 92% of its 50 GB plan. The IT head runs a quarterly audit: open Trash sorted by file size, identify the largest files genuinely no longer needed (test videos from a phased-out feature, duplicate event photos), permanent-delete each one. Storage drops 8 GB in a 20-minute session. No upgrade needed for another quarter.

See Trash & Restore live with a folder we'll delete on demand

20-minute walkthrough — we delete a folder, search Trash, restore it, then permanent-delete and show the typed-name confirmation friction. No real data harmed.

What every principal asks before saying yes

The first question is always: 'How long do deleted files stay in Trash?' Forever, by default. Inkwelly never auto-deletes from Trash, regardless of how long the item has been there. A file deleted in 2024 is still recoverable in 2030 unless someone has explicitly permanent-deleted it. We made this choice because Indian schools often need access to records of past students 1 to 3 years later for TC re-issues, board verifications, RTE audits and parent enquiries. Auto-delete would create more problems than it solves. The trade-off — soft-deleted files do count toward the school's storage quota — is handled with a quarterly Trash audit rhythm we recommend. Most schools recover 5 to 15 GB per quarter through this rhythm without ever needing a quota upgrade.

The second question: 'Can we permanent-delete things we genuinely no longer need?' Yes — and the friction is intentional. Typed-name confirmation, irreversibility tick-box, 5-second cooldown. The dialog shows the file's full path so you know exactly what you're removing. After confirmation, the file is gone forever — bytes removed, database row hard-deleted, the action fully recorded. There's no undo. This is the right contract for irreversible actions: deliberate, slow, audited. Schools that need a 'pause-the-deletion' state for legal-hold reasons can contact Inkwelly support to set a hold flag on specific files.

The third question: 'Who can restore files in Trash?' Trash respects the school's role-based permissions. Users with view access on a folder can see deleted items from that folder in Trash; users with manage access can restore them. The principal typically has full access to school Trash. Class teachers see only Trash for folders they had view access to. Personal My Files have their own per-user Trash, isolated from school Trash — only the user themselves can see and restore their own personal Trash. The super-admin can configure custom permission grants for IT heads who need broader access. Same boundary as the rest of Inkwelly: roles defined once, applied everywhere.