Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,296,746
Community Members
 
Community Events
165
Community Groups

Sharing (only particular) pages with individuals

Hi there, 

 

Is it possible to share some particular pages in confluence with individuals without sharing all the Space info? 

 

For e.g. we have freelance employees and we would like them to collaborate in particular pages without seeing all the context in our Space.

 

 

Looking forward to hearing from you

1 answer

You can go about this in a number of ways. Here are two.

Summary

These methods assume you're not doing any fancy coding or behind the scenes work to separate content and that you don't have any special plugins

  1. Create a separate space for the freelancers
  2. Create two main header pages in your page tree
    1. Restricted pages - for your main team
    2. Shared pages - for everybody (with space access)

Method 1

Pros

You've got clear separation

  • No worrying if you've got pages under the right heading page
  • No worrying about setting individual page restrictions
  • You can have separate blog posts, templates, side panel, etc.
  • You could link to the freelancer space from the main team space to make navigation a little easier

Cons

Content is not centralized

  • If you your main team uses the content as much as the freelancers,
    • they have to go to a separate space, or
    • you'd have to recreate pages and use the Include page macro for everything in the other space (really not feasible), or
    • you'd need to create a page showing the page hierarchy for the other space
  • You have to setup page restrictions for the Restricted pages page and maintain them for each new/removed main team user
  • You'll have to re-enter permissions for your main team in the freelancer space
  • Space watchers would need to watch two spaces

Method 2

Pros

Content is centralized

  • You only have to maintain one space, one set of permissions, watchers, etc.
  • It's easier for the main team to see at a glance what the Shared content is without having to go to another space or to a page

Cons

Risk of content exposure

  • You have to be sure that users create pages under the right headers
    • Some pages may get misplaced and content may be seen by those who shouldn't
  • Blog posts, templates, side panel, etc. would be for all users

Conclusion

In the end, it really will depend on your use case, how important it is to separate the content, and the skill level of your users as to which method will work best for you.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase
Published in Confluence

Confluence: Where work and wellness meet

Feeling overwhelmed by the demands of work and life? With a 25% increase in the prevalence of anxiety and depression worldwide during the pandemic, for most of us, it’s a resounding yes . 🙋‍♀️ ...

1,052 views 19 29
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you