Limit Guests to part of a space
Asked by Brian Trahan:

We have a space with several pages under it and each of those has child pages as well. Is there a way to limit a guest so they can only see one page and its children? If I try restrictions to default to deny it doesn't look like I have access to add the guest to the appropriate pages.

Right now this is all internal but when we want to start giving people access to view/contribute on their own sections I don't want them able to see anyone else. Am I going to be forced to make every page its own space and not have an easy consolidated site for my internal team?


Answers:
author: Kristian Klima
body: [@Brian Trahan](/t5/user/viewprofilepage/user-id/4377740) It would be possible, I think, thru cross-space page inclusions but I can't imagine the nightmare of maintaining that.

**Guest** always have access to precisely ONE space. Not more (not more spaces), not less (not just a selection of the given space)

Here, I'd rely on apps here.

**Solution 1 - Scroll Viewport and Scroll Documents by K15t**

Scroll Docs allow you to segment a space into 'documents'. Let's say that you have 5 sections (top level parent pages) in your space. You want your Guests Group A to access the Section 1 and Section 5 only.

Create 5 documents in the app.

Then, using Viewport, you create a site with Documents 1 and 5 (corresponding to your sections 1 and 5). Set up that site with the SSO / token based authentication to give access just to the selected user group.

You can create as many sites as you need and mix and match content as you need.  

This approach is passive and doesn't allow to contribute.

**Solution 2 - Use Refined for Confluence.**

Refined builds directly on Confluence and relies on Confluence permissions but you might be able to build sites with specific content (don't know the app that well but there might be a solution). Refined site would act as front showing just the selection of the content that you define. And because you can edit pages directly from Refined, it does offer active participation.  

**Solution 3 - Use Space sync for Confluence**

Create separate spaces for individual guest groups. So you'd have, for example, 5 spaces instead of 1. There, you give access to your guests as they need.

Use Space Sync to push content from individual spaces to the Master Space which would be an amalgamation of the five individual access spaces.

Then use Refined or Viewport to allow everyone see the final document.

comments: author: Brian Trahan
body: I will look at these apps and see if they can achieve the results I want.


author: Linh Pham_Ricksoft_Inc
body: [@Brian Trahan](/t5/user/viewprofilepage/user-id/4377740) I agree with Michael's suggestion. Otherwise, you can set page restrictions individually.

In addition, there are several ways you can cross-publish content from your original space to the guest space, so you don't have to manually duplicate pages and maintain them.

- [Use the Include Page macro](https://support.atlassian.com/confluence-cloud/docs/insert-the-include-page-macro/)

- [3rd party app to sync content](https://marketplace.atlassian.com/search?product=confluence&query=sync%20page)

I hope this is helpful!

Disclaimer: I'm with the team that developed one of the apps called Space Sync for Confluence :)


author: Michael Yaroshefsky - Visor for Jira
body: Hi Brian,  

I wonder if Confluence's single-space guest access would be helpful to you?  

With single-space guest access, you can allow guests into a single space without worrying about their access to spaces you don't want. In either case, I found two articles that may be helpful for you:

1. This article from the Atlassian team explains more about **Single Space guests** details: <https://community.atlassian.com/t5/Confluence-articles/Single-space-guests-now-on-Confluence-Cloud/ba-p/2121527>
2. Also, there's a way to **give guests individual guest access** . See this support article here: <https://support.atlassian.com/confluence-cloud/docs/invite-guests-for-external-collaboration/>

Let us know if this helps,  

Michael

comments: author: Brian Trahan
body: The issue is that the guest sees the entire space. I have things for other people in that space that they don't need to see. I'm testing with individual guest accounts and it is very all or nothing.


author: Farhan Sarwar
body: Agreed. Presently there is no easy way to give guest access to certain pages in a Space, while having everyone else in the internal team be able to see everything.


Tags: cloud

confluence-cloud