How does "Request access" work in Confluence?

When user accessed a restricted page, user can send a request to the last editor to get access to the page.

Can the request be sent to space owner since that user is the owner of the space and decides who can access and who can't

3 answers

As far as I found out, there is only the chance to disable the Plugin completely.

Therefore you need to go to "manage addons" > "Show all addons" > "Confluence Request Access Plugin" then hit the disable button.

Anyway I would prefer a solution where I can define who will get the request for access.

It would be nice if it could be tied to the administrator permission set in space permissions. But here is the Confluence documentation regarding this plugin:

http://blogs.atlassian.com/2013/09/new-in-confluence-request-access-to-view-restricted-pages/

Per the documentation at https://confluence.atlassian.com/display/DOC/Assigning+Space+Permissions the space administrator can grant users and groups to have permission to restrict (edit and view) pages.  Note that permission to Add pages (and edit content) is not the same as the permission to restrict pages.

Hope this clarification helps!

0 vote

Hi everyone, 

A quick note to let you know that in Confluence 6.8 we've improved how request access works under the hood.  When a user requests access to a restricted page, Confluence will send an email to up to 5 people. It chooses people in the following order:

  1. people who have contributed to the page in the past, can see the page and have 'Restrict' or 'Admin' space permission (sorted by last edit date)
  2. space administrators who can see the page (sorted alphabetically).

This means that the request should be actioned quickly, as it prioritizes the people who have been interacting with the page most recently. 

So this has created an unfortunate scenario where some of our jira/confluence admins - people who really have nothing to do with the space are getting all of the request for access emails.

We have to have one group that has admin on every space, but we have no way to designate another group as the ones who should be receiving these emails as they both have space admin.

Right now one of our jira/confluence admin's name starts with Aa so he gets every single email from all spaces.

Anyway to delegate a specific group to always receive these emails?

Hi Chad,  

Thanks for letting us know, I can see how this would be problematic.  I'll raise it with the dev team. 

 

We had hoped that in most cases, the request would be sent to someone who has been interacting with the page itself, but sounds like in your case that few people have the 'Restrict' space permission? 

Ooooh wait a second.

So I can remove the restrict permission from the space admins and they won't receive these emails anymore - that fixes my routing issue.

I just submitted a ticket for a similar issue with us not receiving emails at all.  But I'll wait for their response.

Thank you for the quick response!

Sorry, that workaround won't work - as Space Admins are always able to restrict and remove restrictions / grant access (regardless of whether they've explicitly been given the Restrict permission). 

The only workaround I can think of is to actually grant more people Restrict permission, so that the pool of non-admins that can grant access is larger - but that may not work for your organisation (as these people would be able to restrict content as well as grant access). 

Same problem exists at our site. Most of the time there are not that many editors or contributors to a page. So the space admins (and in our case the system admins as they are always space admins) will receive a mail. I've got no great idea how to solve that problem: I like the request being delegated to more persons than just the editor/ last author, including the space admins seems to be the right thing for most use cases.

Maybe a configuration switch or a default delegation email address could ease the problem...

Here is what I did that I think is working from spot checking all my spaces.

Create one global "space admin" or just use "site-admin" either or.

Create a space specific admin group. IE: admin-product

Add the users who should receive requests and manage the space to admin-product.

Give all permissions to space admin group ( or site admin ) but remove the restrict permission.

Doing this changed the routing of emails to go to the admin-product group and not our site admins or space admins.

Hope this helps.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Kesha Thillainayagam
Posted Apr 13, 2018 in Confluence

We want to hear how your non-technical teams are using Confluence!

Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...

359 views 20 10
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you