Page & Content permissions

[Gianluca Romanin]

Hi all,

we have an issue with permissions and content sharing.

We use 2 different trees of pages:

A (private tree: only Vimar specific users are allowed)

- page 1

- page 2

B (external supplier tree: Vimar and External supplier users are allowed)

- page 3

- page 4

we would like to share a specific content from page 1 to external suppliers.

We would like to have another page (let's say page 6) tracking part of or the whole page 1.

So the situation should look in this way:

A (private tree: only Vimar specific users are allowed)

- page 1

- page 2

B (external supplier tree: Vimar and External supplier users are allowed)

- page 3

- page 4

- page 6 -> tracks page 1

We tested "Include page macro" and "Excerpt Include Macro" to do the thing, but

the external supplier should be allowed to see also the original contents to

see page 6. This is a nonsense for us: we would not like to share all the infos

of out pagetree, but we would like to share only some specific infos.

What's the right path to do that?

Is this possible only with fine grained permission management?

Thank you,

Best regards,

[James Conway · Accepted solution]

@Gianluca Romanin If i have understood correctly, you want page 6 to include content from page 1, but page 1 is restricted.

I suggest that you restructure your hierarchy so that open content from page 1 is on an unrestricted page (either page 6 or a separate page), and you use an include macro to show it on page 1 (and page 6)

Hope that helps

James

[evanbartlett]

@Gianluca Romanin what did you end up doing in this situation?  did you move that page somewhere else?

[Gianluca Romanin]

Hi @evanbartlett !

As stated from @James Conway there are few solutions:

- you can have a public space and both page 1 and page 6 can include a page from this space

- you can use the less restricted page (in my example page 6) as common source to be included in page 1.

We decided that this approach is not useful to us, and we redesigned all the content structure to use the permission as thinked by Confluence: all is public to team members and only the nodes that need some permissions are restricted to the required team.

If you have external team members you can deal with it in different ways. We decided to use:

- Scroll PDF exporter, to export a full PDF document for them, without requiring a Confluence access

- External share, to expose a dynamic tree of pages to non Confluence members, for a quick share with comments and password

Best regards,

Gianluca

[evanbartlett]

Thanks!