Uploaded image for project: 'Confluence Server'
  1. Confluence Server
  2. CONFSERVER-2841

Provide locking for attachments



    • Type: Suggestion
    • Status: Not Being Considered
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Editor - Attachment
    • Environment:
    • Feedback Policy:
      We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.
    • Support reference count:
    • UIS:


      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Atlassian Update, October 29 2018

      Hi all,

      Thanks for providing your thoughts and votes on this suggestion.

      As you’re probably aware, we made significant improvements to our editing files experience in our 6.11 release, allowing users to both edit any file type, and do so without having to manually download the file and reupload their changes. For more information on these improvements, please see our documentation.

      However, as part of these immediate changes we decided not to implement attachment locking. There is an add-on available (Cenote Lockpoint) which offers the ability to lock documents while they’re being edited.

      We do though understand the value attachment locking would bring, and will reconsider this suggestion at a later date.

      Jenny | Confluence Server Product Manager

      The new attachment edit feature in 1.4 is helpful but we would benefit more from being able to lock individual attachments. This would allow a user to indicate an attachment is being edited so that another user does not initiate changes to the same attachment.


          Issue Links



              Last commented:
              42 weeks, 4 days ago
              PM Reviewed: