We also, would love to see the ability to inherit privileges automatically from a parent/ancestor page, similar to what Dan describes above. We could then assign privileges at a parent page level and not have to worry if people are applying the right privileges to pages created below it.

Page permissions are in Confluence 1.4, but blog permissions are not. I've moved blog permissions into CONF-3305 so I can close this issue.

It would also be good if it could browse Active Directory for a user or group to set the permissons instead of having to create the users and groups all over again.

This is quickly becoming a major issue for my organization as well. Not having page-level access controls means that we have to create tiny spaces for each distinct set of users that should be able to see protected content. It would be much nicer to have a single space called "Budget" and each department manager has control over one or more pages in the space, as opposed to spaces named "John's Budget", "Mary's Budget", etc.

Note also that CONF-1455 is pretty much a duplicate of this ticket.

I strongly support the page-level security support. Right now when organizing documents, decisions on where to place a page has to be made based on security which then might dictate a page has to be put into space x instead of the space where it would belong if grouped according to content.

An additional option to "take permissions from parent" would be useful too. So you a page would initally take global permissions, then override with space permissions, then override with parent permissions (which could cascade up the parentage tree), and then override finally with the page permissions.

The ability to put in + and - permissions (to give / take away permissions which may have been set further up in the permission branch) would be required to revolk a permission given in the space but not wanted on a page.