← Back to Blog

How to Remove a Version File (“Delete file”) in Version History

In ISMSVision, Delete file in the version history table does not erase the fact that a version existed. It removes the stored file for a non-current version from storage so Open, Download, and Restore can no longer retrieve that binary—while the row stays in the history for traceability.

Why this exists

Organisations hit storage limits or adopt retention policies that allow dropping cold binaries while keeping metadata for audits. ISMSVision separates “there was a version 1.2” from “we still host the 1.2 bytes,” so you can reclaim space without pretending the semver never happened.

Who can do it

Actions in version history respect your document-management permissions and API rules. If you cannot see Delete file, ask an administrator to confirm your role and whether the version is eligible (for example, not the current version).

Steps

  1. Open Version history from the document row.
  2. Find a non-current version that still shows a file in storage.
  3. Click Delete file and confirm the prompt—it explains that history remains but file access ends.
  4. The row updates to show that the file was removed; preview and download buttons are disabled for that version.

Deleting the whole document

To remove a logical document (the library row and its policy record), use Delete document from the main table when your role includes delete permissions—not the per-version Delete file action.

Manage retention in ISMSVision

Log in to balance storage, evidence, and policy in one controlled library.

Log in to ISMSVision