General space and sub-spaces
Asked by joris_monten_cegeka_com:

Hi all,

Is it possible to achive the following:

![customers.jpg](/t5/image/serverpage/image-id/82685i7C78812D418401C3/image-dimensions/530x272?v=v2 "customers.jpg")

What we want to do:  
- We're creating all the spaces  
- Create user groups (eg. customer1_users, customer2_users, ....)  
- Create the channels under the General Space page Tree  
- Add restrictions to those pages (restrictions on user groups)

So far we've got not really issues, but now the question:  
How can i make the pagetree like in 'General Space' visible into 'Space Customer 1' with the restrictions (so Customer 1 can only see in his space: 'Documentation Customer 1'.

I've tried to copy the pagetree from the 'General Space' but when new documents are created it won't flow through to the Customers.  
I think it needs a kind of 'link' so that if things are changed into the documents or page tree it automatically flows through for the customers.  

Anyone some experience with this on how to handle it?

Many thanks!


Answers:
author: James Conway
body: [@joris_monten_cegeka_com](/t5/user/viewprofilepage/user-id/3653928) I cannot offer a definitive answer, but it might be worth you exploring Space Categories.

A couple of reference pages:

<https://confluence.atlassian.com/doc/use-labels-to-categorize-spaces-136647.html>

<https://confluence.atlassian.com/doc/spaces-list-macro-139375.html>

You may also want explore apps in the marketplace with names like 'Space Creator' and 'Space Admin'.


author: JP _AC Bielefeld Leader_
body: Hi,

displaying pages from different spaces in one tree is afaik not possible. What you could try, is using page properties \& a page properties report.

The content pages for customer 1 are created below a restricted page in the general space. This parent page is restricted to the customer user group an the editorial staff. Create a parent page like this for the other customers restricting it to the specific customer user group.

Create an unrestricted parent page for common documentation.

You tag all content pages to be displayed to the customers with a common label eg. "customer". Use the same label for ALL customers. The content pages MUST contain a **page property macro** with a table defining the columns of the page property report, The page title is automatically part of the report table.

Then you create a page property report page in each customer space. You can create the page once \& then copy it to the other customer spaces. The page contains a **page property report macro.**The macro get some configuration parameters like the label to work on ("customer"). The space(s) to generate the report from (general space). You can filter on much more stuff, define the sorting, etc.

Now, when customer 1 visits his space \& opens the page containing the page property report, he will see all pages tagged with "customer" that are visible for him (the restricted ones \& the common documentation).

You even might not need separated customer spaces unless their is specific customer content handled directly in the customer space. This makes sense, when you want the customer create own pages in his space but not fiddle around in the general space.

Please check:

<https://confluence.atlassian.com/doc/page-properties-report-macro-186089616.html>

and

<https://confluence.atlassian.com/doc/page-properties-macro-184550024.html>

for a deeper step into page property reports.

Best

JP


Tags: confluence-server

customer

page-tree

server