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,024
Community Members
 
Community Events
165
Community Groups

User access permissions

Edited

Hello Community,

We now have a scenario where there are external users added who require edit access to specific pages and/or on our confluence. We have the core group of users who it'd be fine to access most spaces but not this group of external users. I've read that confluence is inherently designed for all-access content (default confluence-users has edit as default across any space). But it now seems as though I'd need to reverse engineer the access permission in order to accomplish this restricted access requirement. 

If I'm not mistaken I would have to: 

  1. Create a similar group to confluence-users, such as: core-team
  2. Go through every space we have and edit permissions to remove access to confluence-users and add replace those permission for core-team.
  3. Any external users added would then need their own group such as: external-company-x and this added to the specific space or page for restricted access

From what I can see this would be the way to get a handle on access permissions within confluence. Would I be correct? 

I've done quite of bit of searching and wondered if there's someone who could shed a bit more light on this for me or give me some advice. 

 

Many thanks 

1 answer

1 accepted

0 votes
Answer accepted

Hi @Solomon John-Addey ,

In principle your approach should work.  However I would do it slightly different:

  1. Add all external users to the group "external-users"
  2. Make sure external users are not in "confluence-users"
  3. Make a new space "external-space" and add edit permissions to the group "external-users"

By using a space as a boundary it is much easier to keep overview of who has access to what.

Thanks for the reply, I have a couple questions. 

 

From my experience turning off "confluence-users" blocks users from accessing confluence at all. Is that incorrect? 

 

Adding them to an external space would simply mean sharing the relevant pages into that space? Currently, these external users need to access a handful of pages in a larger space already populated...

 

Many thanks 

To answer your follow up questions:

From my experience turning off "confluence-users" blocks users from accessing confluence at all. Is that incorrect?


Yes, by default.  You would need to give the new group explicitly product access.

Adding them to an external space would simply mean sharing the relevant pages into that space?

Yes, the pages would have to live in separate spaces.

Like Solomon John-Addey likes this

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 . 🙋‍♀️ ...

987 views 16 27
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