Content access requests now live in Share

[#1]

Hi Confluence Community,

I’m excited to announce a major upgrade to how you manage content access requests: Content access requests now live in an item’s Share dialog!

We’ve heard your feedback — reviewing and approving access requests via scattered notifications and emails was slowing you down and sometimes blocking collaboration.

With this release, we’re centralizing all your content access requests in one place, right inside the Share dialog. Now, content owners and editors can easily review, approve, or deny requests — no more hunting through notifications or missing urgent asks.

What’s new

A dedicated “Requests” tab in the Share dialog

Instantly see all pending requests for your content. Grant view or edit access, deny when necessary, and easily scroll to see all requests.

As you action requests, the people you grant access to get added to the specific access list. If there are no pending access requests, the tab will disappear to keep your sharing experience uncluttered.

More than just the owner can action requests

Anyone who can change access to the content item can step in to approve requests, keeping work moving.

Say goodbye to duplicate requests and scattered side-channel chats asking for access. With all access requests now centralized and visible in one place, your team can quickly review and take action.

Learn more about how content access requests work.

What’s next

We’re not stopping here! We’ll soon bring even more power to access requests, like “approve all” for bulk requests and deeper integrations with notifications.

As always, your feedback will help us shape what comes next.

Happy collaborating,

Marie & the Confluence Permissions team

[Rune Rasmussen]

1.
Will we be able to modify the "You've stumbled upon restricted content" message, and adjust the behaviour of the "Request access" button?
Our dream scenario allows us to set a global default message that can be overruled by a Space specific message.

2.
And is there any considerations about having separate messages for licensed and unlicensed users?

For us all accesses to systems must be requested through Jira, but once you're in access to the individual spaces can be managed by the space owners or admins.
There are exceptions to this for certain Spaces.

We often get requests along the lines of "A colleague sent me this link, but it doesn't work. I get this message [SCREENSHOT]" and then we have to spent extra time figuring out of they have a license or not.

So having configurable messages for licensed and unlicensed users would let us make a generic "Submit an access request here [LINK TO PORTAL] and a [You don't have access to this Space/Page, please contact {{space.owner.DisplayName}}", or something along those lines would save everyone involved a lot of time and make for a smoother experience.

And for Space Owners/Admins to be able to override those default messages with a Space specific one would save us a lot of head aches for those Spaces that has a special process or unique requirements.

Bonus points if we also get to configure the behaviour of the "Request access" button.
It could be used to trigger Jira automation (Triggered by web request for instance).
That could allow us to auto-create an access request and fill it with information about what space/page it was triggered from, by whom, and we could chain it together with other automation rules.