How can I limit the ability to modify a checkbox on a Confluence page?

[Danno]

I tried to create a fillable checklist in confluence. Unfortunately setting the page restrictions so that all can view and only some can edit does not prevent others from modifying the checkboxes. Even view only permission allows someone to check/uncheck the boxes. Is there a way to prevent this?

[Ivan Nikolov]

In my case the workaround is to use the 'Status' macro and change the colors based on "selected/not selected" (in scope or not) as adjustments here are only possible if in Edit mode versus accidentally checking or unchecking the tick-box for a server in View mode, which is what I what to avoid.

v1 - using checkbox and risking unexpected or accidental checks/unchecks after approved scope.

v2 - using the 'Status' macro and editing from e.g. Grey = out of scope to Green = In scope for the planned software release. (possible only in Edit mode hence no risk to accidentally or purposely change).

[Jen]

May I ask what is the goal you're trying to achieve?  We've adapted all sorts of workflows, due to the functional limitations.  Perhaps I could suggest a work around?

[Danno]

Hi Jen,

Thank you for replying. I was trying to use checkboxes where the document creator could check them off and still allow other people to view it while it was in progress but not be able to uncheck items. Setting the permissions to the page to keep others from editing doesn't lock out the checkboxes. Viewers can check or uncheck at any time.

Unfortunately, I am not able to acquire a lot of add-ons to my system nor am I a good enough programmer to build my own.

[Danno]

Jen, I just realized you mentioned workflows in your answer. If there is a way to implement some sort of tie in via Jira workflows to Confluence I'm all ears.

[Sven Schatter _Lively Apps_]

Hi @Danno,

Unfortunately, Confluence Tasks don't come with any permission system. An< user can check or uncheck them, there's no way to configure this.

Cheers,
Sven

[Danno]

Thanks for answering. I think what I have to do is make the actual checklist totally private to the user who created it and then "publish" a PDF version of it for others to view.

[Xandra Volkmann]

Dear all, I am facing the same issue you described here. Is there still no possibility in place to permit check or uncheck of the boxes? I am hoping that now (almost 4 years later ;-)) something was implemented to improve this issue?

Thanks

Xandra

[Ivan Nikolov]

Fully support the option to restrict unchecking already checked boxes.
This is an issue as for example, we document cross-cluster deployments in Confluence and the ability to mark which cluster has been updated with the latest service version and then suddenly uncheck the same server (by mistake or not) is not very helpful as this can be done on a published page (no need to be in 'Edit' mode)! You would always need to check the history which is time-consuming.
Please suggest a solution i.e., check-boxes can be checked if the page is published but only unchecked in 'Edit' mode so access rights can be restricted.

[Gherdan Dragos]

Any updates on this topic? :D 

[Vickie Scarffe]

Since everyone is just liking the question on updates, I'll assume there are no updates and take pdfs of the final procedures.

[Gherdan Dragos]

Could there be a workaround for this? 

Any idea would be appreciated here.