Page Restrictions
You can restrict view and edit permissions on a page by page basis...
Requirements
Step 1 - Add, Edit or Copy a Page
You can set view and edit restrictions when:
Step 2 - Set the Permissions
The page restrictions panel will usually be hidden as shown below:
Click the EDIT link to display the restrictions options:
By default, there will be no restrictions in place so viewing and editing of the page will be controlled by the settings in [USERGUIDE:Space Privileges].
To change either privilege, simply choose the desired option for the view and edit restriction:
- No Restriction — Permissions for this page are taken from the settings in [USERGUIDE:Space Privileges].
- Me — Only you can view and/or edit the page
.
- Group — Restrict view and/or edit privileges to a specific user group. You can click the search icon to select a group from a list.
Step 3 - Save the Changes
Once you've finished editing the restrictions, click the Save button to save your changes.
Hints and Tips
You can create private pages on your website or intranet simply by restricting the view to "Me".
Pages that are attached to a parent page which has specific page level permissions defined do not inherit those permissions. For example, if you have a page called "My Curriculum Vitae" attached to a private page called "My Stuff", the "My Curriculum Vitae" page would still appear in search results, etc., unless you also apply the relevant page level permissions to it.
When you restrict viewing of a page to yourself or a specific user group, anyone who cannot see the page will not see it's children listed in the [USERGUIDE:Site Map] even though they will still have access to those child pages (unless you add restrictions to them). They will still be able to get to the child pages using the search, [USERGUIDE:Alphabetical Index] or Links to the page, etc.
Restricting the view of the [USERGUIDE:Space Home Page] is not a very good idea! Anyone who can't view the page would get an error message as soon as they enter the space and, well, just don't do it...
Space Administrators and System Administrators can bypass your page level permissions, enabling them to see and edit your content.
Frequently Asked Questions
| Q |
If someone does not have access to a space, will they be able to see my page if I set it's restriction to either "No Restriction" or their particular user group? |
| A |
No. Space level permissions take priority over page level permissions. Furthermore, Global permissions take priority over Space permissions so for your page level permissions to work the user must be able to use Confluence and be able to view the Space that contains your page. |
See Also
Added by
In trying to use page restrictions with groups, when we click on the search icon to select a group, the only groups to show up are confluence-administrators, confluence-powerusers, and confluence-users
None of the other groups we have defined show up in the list.
thanks.
steve
Same problem here! I checked the groups listed in the permissions for the space and all my groups are listed there but don't show up when I try a Page Restriction.
Kerry.
Sounds like a bug in Confluence - please open a support request with Atlassian
Is there any way to automate the setting of page restrictions? For example, via a macro or by setting the restrictions on a live template?
I'll be importing numerous wiki text pages with {html:script} tags pointing to external content stored in a CMS. I don't want users to be able to edit these pages and potentially break the link or muck up the content with stuff other than what's on the other side of the link, and I'm dreading having to set each page's Edit permissions manually.
Is there any hope?
The easiest way would be to use space permissions to prevent users from editing the pages. However, if users are required to alter other content within that space (not the content from the CMS) you would probably need to develop a macro or XML-RPC plugin...
From memory the Confluence API doesn't allow page permissions to be set (this may have been added in Confluence 2.3 since the last time I investigated this) - an XML-RPC plugin would allow you to extend the Confluence API to allow remote setting of page-level permissions.
The macro approach would likely be quicker and easier, however the permissions would only get set when someone first views the page. Should someone with sufficient privileges later edit the page and remove the restrictions, they'd also have to remove the occurrence of the macro on the page otherwise the premissions would be reinstated as soon as the page was viewed after saving.
If you have a critical need for this, please contact our sales team to enquire about plugin development. Alternatively, if you have in-house Java developers they could develop the plugin on your behalf.
Thanks for the quick reply! My first step will be to check the feasability of putting this content into its own space. If that doesn't work, we may be contacting you