Missing functionality when restricting users permissions for wiki pages

[alex_carruesco_hp]

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...

[James Conway]

Hi @alex_carruesco_hp 

The ability to automatically separate creation and editing permissions is not a native capability of Confluence. An alternative approach would be to apply a document management workflow using an app from the Atlassian Marketplace. One option you could consider is Comala Document Management. 

You could then allow any user to create or edit pages but not make them available across your organisation one or more reviewers has approved the content. 

You may be interested in our article Tyler Technologies creates knowledge base for customer success with Confluence and Comalatech that we wrote in collaboration with @Libby Healy. 

Let me know if you have any questions.

Kind regards

James
Senior Product Manager at Comalatech

[alex_carruesco_hp]

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:

https://jira.atlassian.com/browse/CONFCLOUD-4087

https://jira.atlassian.com/browse/CONFCLOUD-38722