You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi, I would like to have a way to restrict the creation of new pages to only some users, but allow the rest of the users to edit the pages by default. However, this cannot be done with current confluence settings, because the "creation" and "edition" of pages is under the same setting, so there is no way to achieve this. Would it be possible to split this in 2 different settings?
More info about the current permissions here, where you can see that "Pages" have only 2 settings "add" and "delete" and "add" means creation and edition of pages: https://confluence.atlassian.com/confkb/understanding-permission-in-confluence-979403839.html
I believe this is an important use case because for big organizations it is very complicated to organize and align all the information, and if everyone can create pages, the wiki may easily become a chaotic place, while restricting this creation would allow to have a more organized wiki. But we want everyone having the possibility of contributing to the wiki, so we would like to allow them to edit pages...
Thanks for the suggestion, James. Comala Document Management seems a very interesting software. However, I think it would be counter-productive for us to use it right now because we are using the confluence wiki only internally and we are trying to educate our community to use it more, and if we put some overhead to the process (such as reviews) it would be harder to spread the usage of the wiki. Maybe in the future we can move to that solution.
But for now, it would be great if the Atlassian could solve this. I found that this same suggestion was already done years ago: