We need this as well, as we are automating the creation of pages.

I am (kindof) getting around this issue by including CSS on as many pages as possible that hide the "Create" buttons. This is not foolproof, as some pages will be missed, and some pages cannot be modified in this way. Space moderators also need access to the buttons, which requires "secret" pages where the Create button is enabled.

Automation may be put in place to detect pages not created using our system.

Obviously none of this is as good as being able to limit page creation in the first place.

+1

Are there any progress on this request? 

+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?

This is such a silly issue to be open for 11 years! It's the best mechanism we have for stopping chaos ensuing with 250 users - we want to tap into their knowledge regarding editing existing pages but we don't want them creating pages all over the place. So frustrating that this is still not possible.

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