- Open or Restricted: the two starting points
- Restricting a page, step by step
- What child pages inherit, and what they don't
- Why some names won't appear in Specific access
- What restricted pages look like to others
- Handling access requests
- A note on Notion access
- My advice for restricting Confluence pages
- Frequently asked questions
To restrict a page in Confluence, open it, select Share and change General access from Open to Restricted, or keep it Open and lower everyone to Can view. Then add people or groups under Specific access with Can view or Can edit, and save. View restrictions pass down to child pages; edit restrictions don't.
Open or Restricted: the two starting points
Every page in Confluence has a General access state. Open means anyone in the space can view it, with editing either open or restricted. Restricted means only specific people can view or edit. Which one you choose depends on what you're trying to stop: people seeing the page, or people changing it.
| You want to | Set General access to | Then |
|---|---|---|
| Let everyone read, but only some edit | Open, with anyone in the space changed from Can edit to Can view | Add editors under Specific access with Can edit |
| Hide the page from most of the space | Restricted | Add people or groups with Can view or Can edit |
| Keep it to yourself | Restricted, or select Remove all | Leave nobody else in Specific access |
Restricting a page, step by step
1. Open Share
Open the page you want to restrict and select Share.
2. Change General access
Set General access to Restricted, or keep it Open and change anyone in the space from Can edit to Can view. You need to add a restriction to General access before you can give anyone specific access.
3. Add people or groups
Use the search bar to add individual people or groups to Specific access. Teams aren't supported in the unified sharing experience yet, so use groups instead.
4. Set their permission and save
Give each person or group Can view or Can edit, and select Save.
5. Check the child pages
Look at any pages nested under this one. As the next section explains, only view restrictions carry down.
6. Undo if needed
To remove someone, open Share, find the person or group, open their dropdown and select Remove. Remove all clears everyone at once.
What child pages inherit, and what they don't
| Restriction | Inherited by nested content? |
|---|---|
| View restriction on a parent page or folder | Yes, down to all nested content |
| Edit restriction on a parent page | No |
| Edit restriction at space level | Applies to all content in that space |
Atlassian Support flags this as the trap. Restricting editing on a parent page doesn't stop people editing its children, whereas view restrictions flow down to everything nested beneath. If you're locking down a whole section for editing, restrict each child page as well, or restrict editing at the space level.
Why some names won't appear in Specific access
People only appear in Specific access when they have greater access than General access gives them. If General access is Open with anyone able to view and edit, nobody can be listed, because there's nothing more to give. That's why you change General access first.
What restricted pages look like to others
Content with view restrictions doesn't appear in the content tree or in macros for people without permission. A shared link still shows the page title in its URL, though, so don't put anything sensitive in the title itself.
Restrictions don't hide a page from everyone. Organisation admins on Premium and Enterprise plans can view and change access to any content with admin key, and space administrators can see which pages exist and change restrictions.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Handling access requests
People without access can request it. Requests go to the content owner, then the creator, then the last editor, then the space admin, and you can Approve or Deny them from the notification flags or the Share dialog. Check requests promptly, or colleagues end up asking you in chat instead.
A note on Notion access
Notion handles access differently. Its SAML SSO page notes that guests in a SAML-enabled workspace can't use SSO, which is a separate control from page sharing. If you're comparing wikis on how they handle permissions, my guides to Confluence alternatives and wiki software for teams cover the options.
My advice for restricting Confluence pages
Decide whether you're protecting reading or editing, because Confluence treats them differently. For read-only pages, keep General access Open, drop it to Can view and add a few editors. For confidential pages, set it to Restricted and add people by name or group. Then always check the child pages, since edit restrictions don't carry down. For wider habits, my guide on improving your business security is worth a read.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
How do I make a Confluence page private?
Set General access to Restricted and remove everyone else from Specific access, or use Remove all.
Do child pages inherit restrictions?
View restrictions are inherited; edit restrictions aren't.
Can I restrict editing but not viewing?
Yes. Change anyone in the space from Can edit to Can view, and add editors under Specific access.
Can I add a team?
Teams aren't supported in the unified sharing experience yet; use people or groups.
Can admins still see it?
Space admins can see which pages exist, and org admins on Premium or Enterprise can use admin key.


