• 6
    • 5
    • 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.

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

      Currently, users can create a template to be used across Confluence to ease the creation process. This allows for a number of pre-configuration but appears to be missing the ability to restrict the resultant page. A great addition would be the ability to specify a set of permissions which are associated with a template. Below is an example user story to clarify.

      Problem situation/ User story
      Bill is the finance guru at company X and needs to flesh out his quarterly report for which he uses a template. This information needs to remain confidential to himself and the finance team until the end of the quarter. However, there is no option to restrict the page prior to saving it when using a template which means that upon saving, anyone who is a watcher of the finance space will now that bill has started the report and potentially see what information is there if Bill forgets to add the additional restrictions.

      What would alleviate the above would be either the ability to add restrictions when creating a page from a template. Furthermore, the ability to specify that this finance template is restricted to Bill and the finance team by default ahead of time would ensure that Bill could not forget to restrict said page.

      Atlassian Update, October 29 2018

      Hi all,

      Thanks for providing your thoughts and votes on this suggestion. I'm sorry it's been a while since we last provided an update.

      Unfortunately, this suggestion isn't currently on our roadmap. This is because we're instead focusing on making a number of other improvements to Confluence permissions over the coming 6-9 months. We’re yet to finalise exactly which suggestions will be implemented as part of this work, but we’re strongly considering CONFSERVER-5095 and CONFSERVER-7089.

      We do understand the value specifying permissions via templates would bring, and will reconsider this suggestion at a later date.

      Best,

      Jenny | Confluence Server Product Manager

            [CONFSERVER-30812] Ability to Specify Permissions For Pages via Templates

            Michael van den Dool added a comment - - edited

            I don't understand that a 'basic' request like this from 2017 is still on the 'wish list' in 2024 ??

            Regards,

            Mike

            Michael van den Dool added a comment - - edited I don't understand that a 'basic' request like this from 2017 is still on the 'wish list' in 2024 ?? Regards, Mike

            EDV SCKAT added a comment -

            Promotion expired

            EDV SCKAT added a comment - Promotion expired

            KC Integrations added a comment - - edited

            Hi All,

            I have added this feature to the plugin, Blog, Page and Template Tools for anyone interested. I am giving readers on this post a 75% discount on the purchase of this plugin, please use this link to purchase: https://promo.atlassian.com/SZVTN1.

            See the Page Restrictions and Restricted Template macros.

             

             

             

            KC Integrations added a comment - - edited Hi All, I have added this feature to the plugin, Blog, Page and Template Tools  for anyone interested. I am giving readers on this post a 75% discount on the purchase of this plugin, please use this link to purchase: https://promo.atlassian.com/SZVTN1. See the Page Restrictions and Restricted Template macros.      

            It's quite silly to not enable administrators to restrict editing of important templates. Not a big deal if new templates are created but restricting change to critical templates is a no-brainer. Lack of ability to provide secure templates adds an unacceptable level of risk when utilizing vendors in the space.

            Benji Kauth added a comment - It's quite silly to not enable administrators to restrict editing of important templates. Not a big deal if new templates are created but restricting change to critical templates is a no-brainer. Lack of ability to provide secure templates adds an unacceptable level of risk when utilizing vendors in the space.

            Hi all,

            Thanks for providing your thoughts and votes on this suggestion. I'm sorry it's been a while since we last provided an update.

            Unfortunately, this suggestion isn't currently on our roadmap. This is because we're instead focusing on making a number of other improvements to Confluence permissions over the coming 6-9 months. We’re yet to finalise exactly which suggestions will be implemented as part of this work, but we’re strongly considering CONFSERVER-5095 and CONFSERVER-7089.

            We do understand the value specifying permissions via templates would bring, and will reconsider this suggestion at a later date.

            Best,

            Jenny | Confluence Server Product Manager

            Jenny (Inactive) added a comment - Hi all, Thanks for providing your thoughts and votes on this suggestion. I'm sorry it's been a while since we last provided an update. Unfortunately, this suggestion isn't currently on our roadmap. This is because we're instead focusing on making a number of other improvements to Confluence permissions over the coming 6-9 months. We’re yet to finalise exactly which suggestions will be implemented as part of this work, but we’re strongly considering  CONFSERVER-5095  and  CONFSERVER-7089 . We do understand the value specifying permissions via templates would bring, and will reconsider this suggestion at a later date. Best,
 Jenny | Confluence Server Product Manager

            +1 It would be great to have this feature! I need it ASAP

            Victoria Reggiardo added a comment - +1 It would be great to have this feature! I need it ASAP

            Patricia added a comment -

            We definitely need this to protect templates from various groups in the organization. Creation of individual pages without the templates is really time consuming for the team at this point.

            Patricia added a comment - We definitely need this to protect templates from various groups in the organization. Creation of individual pages without the templates is really time consuming for the team at this point.

            Jason Hughes added a comment - - edited

            I especially agree that this feature is needed for global templates.  As far as I can understand at this point, your only options for visibility of a template inside of Confluence is to a single space or to everyone.  There are so many use cases that fall in between, "group access only", "specific user access only", "admin access only".  There is no way to control that so it this is a gap in Confluence permissions right now.

            Jason Hughes added a comment - - edited I especially agree that this feature is needed for global templates.  As far as I can understand at this point, your only options for visibility of a template inside of Confluence is to a single space or to everyone.  There are so many use cases that fall in between, "group access only", "specific user access only", "admin access only".  There is no way to control that so it this is a gap in Confluence permissions right now.

            +1 - need this feature urgently!

            Jan-Niklas Staffa added a comment - +1 - need this feature urgently!

            would be great to see this feature in a future release!

            Uwe Richter added a comment - would be great to see this feature in a future release!

            awmiller added a comment -

            Bump most necessary.

            awmiller added a comment - Bump most necessary.

            Agreed. This would be very helpful for us. This would also provide a 'draft' functionality for pages before release.. which would be more elegant that having to create the page from a template, move it to the user's (restricted) personal space for editing, then 'moving' to a public space when it's ready.

            Doug Robinson added a comment - Agreed. This would be very helpful for us. This would also provide a 'draft' functionality for pages before release.. which would be more elegant that having to create the page from a template, move it to the user's (restricted) personal space for editing, then 'moving' to a public space when it's ready.

            Adding my vote of interest for this feature.

            Lucinda Stroud added a comment - Adding my vote of interest for this feature.

            This function would be very useful. Is there a chance to get this with a later release?

            Maximilian Peter added a comment - This function would be very useful. Is there a chance to get this with a later release?

            jnunez added a comment -

            we are interested in the solution

            jnunez added a comment - we are interested in the solution

            We would really appreciate this functionality too. Watching with interest.

            Atlassian Administrator added a comment - We would really appreciate this functionality too. Watching with interest.

            Any chance to get this in near future?

            Alexander Schätzle added a comment - Any chance to get this in near future?

            In our case, we are creating a page for each project. For the different kind of projects we are using the blueprints and each blueprint has a different permissions scheme.
            So it is quite annoying to restrict every project page manually.

            Alexander Schätzle added a comment - In our case, we are creating a page for each project. For the different kind of projects we are using the blueprints and each blueprint has a different permissions scheme. So it is quite annoying to restrict every project page manually.

            Best would be the possibility to inherit restrictions from the page where the template is created from. Same as it is done with blank pages.

            Martin Dusch added a comment - Best would be the possibility to inherit restrictions from the page where the template is created from. Same as it is done with blank pages.

            Definitely worth developping

            Lionel CONFORTO added a comment - Definitely worth developping

            Please develop it!

            Alexander Schätzle added a comment - Please develop it!

            This would be very useful!

            Tatu Hautala added a comment - This would be very useful!

            Daniel Sokolowski added a comment - - edited

            That would help us in many situations! +1

            Daniel Sokolowski added a comment - - edited That would help us in many situations! +1

            We would need this too!

            Herbert Stadler added a comment - We would need this too!

            That would be great feature!

            Jakub Tkaczuk added a comment - That would be great feature!

            We have a similar need for Release notes being created, That page should not be visible at time of creation, but when the product is published would we remove the restriction. +1

            Filip Vande Kerckhove added a comment - We have a similar need for Release notes being created, That page should not be visible at time of creation, but when the product is published would we remove the restriction. +1

            I just encountered a need for this today. +1!

            Ross Westerbur added a comment - I just encountered a need for this today. +1!

              Unassigned Unassigned
              acampbell AndrewA
              Votes:
              141 Vote for this issue
              Watchers:
              86 Start watching this issue

                Created:
                Updated: