Include Page from a Restricted Space

[Hadar Maoz]

Hello,

I'm managing permissions for my company's confluence and I've run into a bit of a problem.

I have one space that's for Development (DEV) and I've recently restricted it to only Developers.

I have a page in there that a Customer Relations rep has been referencing and the developer created and updated there and they can no longer access it.

So, I wanted to create an Include Page macro in a page in a space the CR rep has access to so they can continue to use that content without removing it from the dev's working Space.

But because CR doesn't have access to DEV, the Include Page macro doesn't work - they get an error when viewing it.

I can't give CR viewing access to the DEV space - is there some macro or alternative solution where I can source content from a restricted space to an unrestricted space?

[Kristian Klima]

Hi @Hadar Maoz , welcome 

You can try enabling a public link on that only page from the Dev space. On the page, click Share and there's the Public Link option.

If it's grayed out, you have to enable Public links on the space level (settings, global permissions, public links)

Whoever on the internet with that link will be able to access it. Which I guess would not be an issue if it's something your Customer Relations rep link to and share.

Hope this helps.

Kris

[Marc - Devoteam]

Hi @Hadar Maoz 

Welcome to the community.

No there is no alternative solution.

You will need to grant the CR at the minimal view rights on the space and restrict all content for viewing and editing not applicable to the CR.

[Hadar Maoz]

Hi @Marc - Devoteam , thanks for your answer.

So, I need to give the CR view to the DEV space and then go page by page and lock them out of all of the irrelevant pages?

That's not feasible - this is a space that's existed for years with dozens of pages...

And there's no way to include view permissions for that single page?

[Marc - Devoteam]

Hi @Hadar Maoz 

View restrictions are inherited editing is not.

So it depends on the structure in the space how much effort you need to apply.

So only the top page, where the readable content is placed, needs to be viewable and edit restricted for the person, but all pages underneath need to be restricted as well for edit and view. Where view will be inherited by sub pages of the main page you view restrict.

See, add-or-remove-page-restrictions