Attachment version control in Confluence
By Jake Marsh · Updated
Confluence Cloud keeps a version of an attachment every time someone uploads a file with the same name to the same page, so older versions are never lost. What it doesn't track is who is working on a file right now, so two people can each download version 3, edit it and upload, and the second upload becomes current without either person knowing. Dibs adds that missing layer: check-outs that show who has a file, a record of every upload made over a check-out, and in Restore mode the holder's version put back on top.
How Confluence numbers attachment versions
Uploading budget.xlsx to a page that already has budget.xlsx adds a new version rather than a second file. The page always shows the newest version, and the attachment's version history keeps the earlier ones with who uploaded each and when. That is the version control Confluence has, and for files that only one person ever touches it's enough.
Where it breaks down
The trouble is parallel edits. Version history records what happened, after it happened:
- Ana downloads version 3 of
budget.xlsxon Monday and starts updating the Q4 sheet. - Ben downloads the same version 3 on Tuesday and fixes a formula.
- Ben uploads first: version 4.
- Ana uploads on Wednesday: version 5, which has her Q4 work but not Ben's fix.
Nobody was told at any step, and the page now shows a file missing a change. Someone has to notice, open the history and merge by hand.
The same week with Dibs
- Ana clicks Dibs: check out files on the page, ticks
budget.xlsx, writes "Updating Q4 totals" and picks a 3-day expiry. - Ben opens the page on Tuesday and sees the banner: checked out by Ana, until Thursday. He clicks Tell me when free instead of downloading.
- Ana uploads version 4 with Check in: release when I upload a new version ticked. The file is released and Ben is mentioned in a page comment.
- Ben downloads version 4, which already has Ana's work, and makes his fix.
If Ben had uploaded anyway in step 2, Dibs would have logged it, posted a page comment mentioning both of them and, in Restore mode, uploaded Ana's version again as the newest. Ben's upload stays in the version history, so nothing is deleted.
What gets recorded
| Event | Where it shows |
|---|---|
| Check-out, release, extend, expiry | The page banner and the Dibs dialog |
| Someone else uploads over a check-out | A page comment mentioning both people, and the admin Activity log |
| A restore | A new version uploaded by Dibs with the comment "Restored version N: this file is checked out." |
| A checked-out file moved to the trash | Logged and announced; not undone |
Confluence admins see the latest 50 events in Confluence settings > Dibs > Activity and can export a CSV of up to 5,000, kept for 365 days.
Limits
- Automatic restore works for files up to 100 MB.
- Pages and blog posts only; attachments on other apps' custom content aren't covered.
- Dibs can't stop an upload from happening, because Confluence saves it before any app is told. It shows the check-out before and reacts after.
Dibs starts with Atlassian's 30-day free trial; prices are on the Dibs page. To check a file out step by step, see how to lock a file in Confluence.
What it costs
Dibs is From $21.50 a month for up to 10 users. Every plan and the install link are on the Dibs page.
Dibs: Attachment Check-out for Confluence
Check out Confluence attachments before you edit them. See who has each file, get told on overwrites, restore the right version. From $21.50 a month for up to 10 users.
Questions
Does Confluence keep every version of an attachment?
Yes. Each upload of a file with the same name to the same page is a new version, and earlier versions stay in its history.
Why does Confluence show Dibs as the uploader of a version?
That's a restore. Dibs uploads the holder's version again so it becomes the newest, and Confluence records the app as the uploader.
Can I turn off automatic restore and only get told about overwrites?
Yes. A space admin switches the space to Record mode: both people are told and the new upload stays current.
Does a restore change the file's name or page?
No. It adds a new version of the same file on the same page.