Hi Giuliano C., thanks for your attention!

I don't mind changing to watch this basic issue from here to CONFCLOUD-38722, but really hope to get the correct solution, creating separate permissions for editing and creating pages, as soon as possible since I was aware of this problem in 2018.

It’s unbelievable that this issue get nothing done since it was reported 16 years ago.

Hello, everyone!

For all users watching this request, thinking about a holistic solution for its implementation, aligned with the provided feedback, we have decided to close this one as a duplicate from the following suggestion, to create separate permissions for editing and creating pages (instead of updating the permission's name):

• Not possible to restrict users to edit page contents without grant add permission in all the space.

We have included all the Cloud cases from here to the suggestion.

Feel free to also add yourself as a watcher to receive updates on our progress and of course, share your thoughts through comments to help us to improve!

Wish you the best,
Giuliano C.
Atlassian Team

We faced also this problem in my company. To avoid chaos in the organization of our confluence wiki, we want to allow only some users to create pages, but we want everyone to be able to collaborate and edit pages. But with current confluence infrastructure we can only grant both permissions or none. It would be great to separate the "page edition" from the "page creation".

I would also like to have option 1). This is also related to this other issue: https://jira.atlassian.com/browse/CONFCLOUD-38722 

Vote for solution 1) This permission should be split up so that page creation and page editing are seperate.

Still nothing have done with this issue? 

+1

From 2005: 'The problem we have at the moment is that we are running out of horizontal space and therefore the button is called "create".'

What's the problem at this (2017) moment?

+1

Hi Guys,

This permission structure is causing some issues for our company as we have hundreds of contributors per space (of which we have over 100 spaces) however none of which we want to have add page access, we only desire them to be able to edit current page content. The absence of this permission separation causes hundreds of hours of unnecessary work throughout the company. This is an unnecessary financial bleed.

I also still miss this

When get this changed

Still missing this feature...

Our team would also like to see a separation in the create and edit page permissions. Any chance you will add it to your feature backlog and plan it on your roadmap ?

This feature would be very nice. We need this feature for our ITIL documentation of our infrastructure. So that we can assure a fix hierarchy of pages / layouts and users are only able to edit the content.

We have a public website and this feature would make our life easier. We want to allow external users to be able to edit specific pages on a space but we don't want them to be able to create new pages.

I just wanted to add support for create and edit page permissions to be split - this will give us the required control over permissions.

My group would also like to see a separation in the create and edit page permissions.

We would also really appreciate to split the create and edit page permission. It's really missing and current state is confusing.

For our shop, Solution #1 (splitting Page-Create and Page-Edit) would definitely be the right thing, giving us the granularity we were expecting when we started migrating our documentation material to Confluence. Anything planned for this year? (I see that priority level is 'Major')

Thanks for the suggestion. We will consider it when we re-design our permission page. The problem we have at the moment is that we are running out of horizontal space and therefore the button is called "create".