Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can non-admin users easily block a group of users from a single Confluence page in a space?

Laura Bridges
Contributor
October 13, 2025

We have a large group of users that we don't want to access specific pages in a wiki space. Adding them all manually would be too time-consuming so for now, we prohibit them from accessing the entire space instead of just the dozen or so pages they should not be able to access. 

Is there a way to do this quickly, perhaps at the API level or by using the CQL? 

Thanks!

2 answers

0 votes
Calvin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 13, 2025

Heya, we do something similar, we provide access to the entire space, but for certain users we allow them to add "restrictions" to pages, this can be done via the "Share" button (formerly the padlock) on the confluence space.

That way the others users don't even know it exists.

Add restriction to a certain page so only certain users can view:

Screenshot 2025-10-14 171455.png

 

Allow certain users or groups to be able to add or remove that restriction:Screenshot 2025-10-14 171536.png

0 votes
Christos Markoulatos
Community Champion
October 13, 2025

Hey @Laura Bridges 

Here’s the straight answer: Confluence doesn’t have a quick “block this group from one page” feature unless you use page restrictions, and those require edit rights plus the “Restrict” permission in the space. So if you’re not a space admin (or don’t have that permission), you can’t do it natively.

Can you use groups?

Yes! Instead of typing names, use Confluence groups in the restriction dialog. That’s the easiest way to manage access consistently. If you don’t have a group for “allowed users,” create one and add only those who should see the page. Everyone else is excluded.

API or CQL options?

  • REST API (Cloud): You can automate restrictions with /wiki/rest/api/content/{id}/restriction endpoints. These let you set view/edit restrictions for users or groups programmatically.
  • CQL: It’s for querying content, not applying restrictions. So you can find pages but not change permissions with CQL alone.

In my opinion, the API approach is difficult because it involves scripting, authentication, and managing page IDs for every restriction, far more complex than simply using groups in the UI. A quicker alternative is applying a restriction to a parent page and using groups, so you only manage membership once instead of editing multiple pages.

Workarounds if you have many pages

  • Bulk update via apps: Tools like Panorama for Confluence or ScriptRunner let you apply restrictions to multiple pages at once.

Links that might help:

Hope this helps!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
TAGS
AUG Leaders

Atlassian Community Events