How can I pre-define restrictions of a new page created with a template?
Asked by Manuel:

Hi everyone,

we would like to create new pages based on a certain template and restrict permissions in the same step. We want to avoid that the creator has to click on the restrictions ("lock") symbol to set the restrictions.

The creator shall later be allowed to read again his page. Then one user group should be able to comment and one group should administrate.

Is it possible to define the restrictions when loading the template or directly saving them in the template? I am wondering if there is a command that can be used in a link or the information can be saved in the template. (Confluence Server 6.15)

Any ideas?  
Thank you in advance!


Answers:
author: Manuel
body: Hey everyone,

Thank you all for your prompt responce and your helpfull suggestions. Funnily enough situations changed a bit by now. It seems, sometimes the answer is simply just in front of you, you just have to pick it up:

++So here comes my solution, I just implemented:++

Apart from Confluence we recently started to use **JIRA Core**. Therefore it was no problem, to handle the content as an issue or ticket. After some struggeling with permissions and restrictions, configurations and schemes we now have a beautiful new issue type that works perfect for us.

Hope I could inspire others to do the same. If there are questions to this solutions please feel free to ask!

Kind regards  
Manuel

comments: author: Matthias Gaiser _K15t_
body: Thanks for sharing your solution, [@Manuel](/t5/user/viewprofilepage/user-id/2571195)!


author: Matthias Gaiser _K15t_
body: Hi [@Manuel](/t5/user/viewprofilepage/user-id/2571195),

unfortunately there is no standard way to do that. The feature request also is not very promising: [CONFSERVER-30812](https://jira.atlassian.com/browse/CONFSERVER-30812).

However, someone at that page suggested that his app [Blog, Page and Template Tools](https://marketplace.atlassian.com/apps/1213130/blog-page-and-template-tools?hosting=server&tab=overview) is capable of doing that.

Cheers,  
Matthias.

comments: author: Mario Carabelli
body: [@Matthias Gaiser _K15t_](/t5/user/viewprofilepage/user-id/853318)

Didn't knew about this app, but it actually sounds pretty useful even besides the restricted template functionality. Thank you for the link.

With kind regards,

Mario


author: EPS Software Engineering AG
body: Hi everyone,

Manuel found an other solution. But maybe some of you are looking for an answer to the original question.

You can use the Page Tree Creator to restrict individual pages. For example, in an employee dossier: Individual pages will be public here. Others only for the employee, the personnel department and the superior.

You can find the [Page Tree Creator](https://marketplace.atlassian.com/apps/1214062/page-tree-creator-blueprint-creator?hosting=server&tab=overview) on the Marketplace.

Regards,  
Stephan (CEO of EPS Software Engineering AG, the vendor of the Page Tree Creator)


author: Mario Carabelli
body: Hi [@Manuel](/t5/user/viewprofilepage/user-id/2571195)

I am thinking that you somehow mixing up page restrictions and space permissions, because their is no way to "administrate" a page. Either you can edit and read or just read the page. The permission to comment pages, adding or deleting pages etc. are set on a space level by the administrator of the space (<https://confluence.atlassian.com/doc/space-permissions-overview-139521.html>)

So if you want only specific groups to do some of these actions with a page then you will have to define a space with the correct permissions and add the template to this space (<https://confluence.atlassian.com/doc/create-a-template-296093779.html>).

But even If you just want to set edit/read restictions on newly created page based on the template this isn't possible without some app/javascript/custom-macro-magic (some informations can be found here:<https://community.atlassian.com/t5/Confluence-questions/Can-I-set-default-page-restrictions-for-all-new-pages-within-a/qaq-p/244683>)

I would advice you to rethink your business case and try to either work in a less restricted space (always remember every change is in site history and content can easily recovered, so the data loss risk is pretty low and it helps transparancy and teamwork if people actually see what other people work on and can comment!) or structure your spaces in a way that they seperate people with different permission settings (customer info space, internal space, etc...).

Hope I could help a bit and best of luck with your task.

With kind regards  
Mario Carabelli


Tags: confluence-server

server