Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Can i restrict editing in columns of a table?

Devo November 18, 2017

I would like to create a table, which uses task-lists and checkboxes.

I need the ability to protect some columns/lines from editing by all except the owner. 

 

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 19, 2017

Permissions are done at a page level in Confluence.  If you can edit a page, you can edit all of it.  Also, Confluence doesn't have the concept of roles like "owner", permissions are by group or individual.

Robert Reiner _smartics_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 19, 2017

Adding to Nic's answer: If each user has write access on their pages, but can read everyone else's, you can use excerpt / transclusion macros to render information from these pages on other pages.

Maybe the Page Properties Macro and the Excerpt Macro may support your use cases out-of-the-box. If not, there are third party add-ons to support multi-excerpt or other handy features to grab information from one or more read-only pages to render it in another page.

One solution could be the Display Table Macro from the commercial projectdoc Toolbox for Confluence server. Every line of a table would be stored in a properties table (using the Document Properties Marker Macro) on its own page (for instance tasks with some metadata like owner, short description, and due date). The Display Table Macro allows then to list all (matching) pages on one table (such as the overview over tasks that selects information from all matching task pages).

Two things (at least ;-)) to consider:

  1. Having each table row as a separate document may sound unfamiliar. But it may be quite natural if you think of tasks and list of tasks. Each task, since it is on its own page, can be referenced individually (which would be harder if one would need to reference a row in a table).
  2. If you want to change a table row a user would need to navigate to the document that is the source for that line and edit it there.

Biased alert: I'm one of the authors of the projectdoc Toolbox (which is available on the Atlassian Marketplace). The online manual provides more information about the tools of the projectdoc Toolbox.

Devo November 29, 2017

Thanks, but this is not what i asked for.

I would like to create a table, where:

1. Some columns can be modified only by the originator, and

    other  users can only read them.

2. Other columns are writable by any permitted user. 

Robert Reiner _smartics_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 1, 2017

You need to find a solution, where the data for the restricted columns is not stored as part of the page. This is because - as Nic explained - a user either has certain privileges on a page or not.

Therefore the mentioned solution using transclusion/excerpt is a valid approach. If this does not fit your requirements I suppose you need to find or write a plugin that stores column data apart from the page. I do not know of such a tool.

Katerina Rudkovskaya _Stiltsoft_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 27, 2020

Hello,

You can do it with the help of the Table Transformer macro of Table Filter and Charts for Confluence and standart Excerpt (Include).

You need to divide you data into two pages. The first one should contain data which are available for public editing. And the secound one should include only those data which other users can't edit. Here on the second page you need to apply appropriate restrictions for it and wrap data with the Excerpt macro.

Screenshot_1.pngScreenshot_5.pngScreenshot_6.png

Then you should insert Excerpt Include on the page with data available for editing and merge data of both tables with the help of our Table Transformer macro.

Screenshot_2.pngScreenshot_3.pngScreenshot_4.png

Thus, other users won't be able to edit restricted columns on both pages.

Katerina
StiltSoft

Like # people like this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events