so many things is missing in both Jira and Confluence and this one of it...

Do we have any updates on this?

I have been pointed out by support to add a few lines in here:

It's quite a shame you have quite decent Permission system in Jira (you can set it up for almost infinite number of use-cases), while permission system in Confluence is pretty limited.

I have stomped on use-case, where I want to make administrators able to administrate all spaces without seeing the content in them. At first, I have experienced, that without a view permission, whole group/person gets deleted from permissions. So you always need at least a view permission to make it work with other permissions too. Support told me to use page restrictions. I would have no trouble using them, but the problem is you can't set them by default for new spaces as same as permissions. And we all know where it will end, if I jus tsay ot people "hey, remember to set up page restrictions every time you create new space...".

Is there any chance, this got reviewed and reconsidered?

Really disappointed that this is set to "won't fix". It would be extremely useful and people keep coming back to this so it's not a one off request.

We are using Confluence exactly as per the comments above:

Create as private -> Review -> Publish

Confluence is intended to be a collaborative platform so we don't want to restrict the ability to create content, but admin/management still need to be able to filter what's published outside the team. But at the moment, to ensure that filter, I have to either disable creating documents for non-admin, which immediately diminishes that value of Confluence as a collaborative platform. Or else I have to run two separate spaces, with one of them set so that only admin can create content, and manually move over every reviewed document. Multiple spaces is not the best way to do this, aside from the extra steps that take time, add no value, slow the process, and introduce more room for error, we don't want our Space Directory cluttered with a duplicate of every space, just so that we can isolate "work in progress" documents. This is really, a ridiculous work around.

So to use this tool (Confluence) to its highest value, I want to be able to control the properties of the documents that users are able to create, within a given space. But without depending on the users themselves, to set the properties manually, and correctly, every time they create a document. I really can't believe I have to argue the value of that?

Please, please re-consider this.

I also would find this useful.  Our current solution is two spaces, one for public consumption and one for private consumption and we move pages from the private to the public.  Much better would be allowing me to set the default permission for new pages in a space to private, allowing my team to keep all of our content in one space.

Just checking in to see if this feature was considered/created. It would be very valuable to have a way to set default restrictions on a page and space level. This would help prevent people from creating duplicate material or putting incorrect material into Confluence.

If this is not going to be created then is there a workaround that is known?

Thanks for the help!

We need this. Space Permissions are a complex mess.

There should be a simple way to set the "Default" permission for any newly created page in a space.

The use cases for this feature are infinite. I would prefer to have the default setting to be restricted to ensure no information is made public unintentionally. 

Develop this feature Atlassian! 

I know this is C/WF, but figured I'd +1 and add my use case anyone can point me to a workaround/related issue. We want to make a Confluence space to manage our career review documents. Each document has custom permissioning, so we want every document in the space to be created as Private to only the author by default so that there is no way some accidentally forgets to permission a document and it is available to everyone.

Use Case 1:

I'm looking for the following:
1.) I want to use confluence to create public content.
2.) I want to have content authors have the ability to create and edit pages, but no publish them to be viewable by annonymous users.
3.) After a simple review process I want to be able to make pages viewable to annonymous users individually on a page by page basis.
Is this possible with Confluence?

Use Case 2.

1.) I want to have an internal space the client can't see
2.) I want to give access to one page from the space so the client can comment directly on it
3.) After the client has commented we may remove the page from being visible.

why do we want this... because
1. its super painful to PDF the page, send it the the customer and have to collate all the feedback manually and put it back in the space
2. copying files between spaces seems cumbersome