File versions

What is this?

Chorilo automatically keeps a version history for each file in the choir file area, covering the last 7 days. Whenever a file is replaced with a new version, Chorilo saves the old state before it is overwritten. You can roll back at any time if someone accidentally overwrote your edit.

Typical use: you updated the rehearsal schedule, someone else uploaded an older copy on top — restore your version via the versions dialog.

How to use versions

1. Open your choir and go to Management > Files.
2. Right-click a file (or click the three-dot menu) → Versions.
3. You see the current version and every version from the last 7 days, newest first.
4. For each version you can:
   • Download — open that state without changing the current version
   • Restore — make that version the new current one; the previously current state moves into the history

Upload new version

You can replace an existing file with a new version directly in the WebApp — no detour via the desktop app:

1. Right-click the file (or use the three-dot menu) → Upload new version.
2. Pick the file from your computer. It is uploaded, and the previous state automatically moves into the version history.
3. The file keeps its name and location. You do not need to create a new upload.

Requirement: files.edit permission on the folder.

When a new version is created

A new version is only created on real content changes — i.e. when someone replaces the file with a new one. These actions do not create a version:

• Renaming the file
• Moving it to another folder
• Uploading an identical file (same checksum)

Permission

• View + download versions: files.view
• Restore a version: files.edit

Tips

• Versions are not a backup replacement — they protect against accidental overwrites, not against losses spanning multiple days. Back up critical documents elsewhere too.
• Check date and editor before you edit — the list view shows this directly in the "Created" and "Modified" columns.
• Retention is hard-capped at 7 days — keeping longer histories would needlessly inflate storage.