Block personal spaces for specific groups

[Sandra Meessen]

Hi, We have 2 big groups of users in our Confluence: groupA and groupB.  We want personal spaces of users of groupA only to be visible to users of groupA. Users of groupB are absolutely not meant to see the personal spaces of groupA. 

Can we use default permissions/restrictions settings for Personal Spaces restrictions? groupA can view, groupB absolutely not.

Thank you. 

[Shannon S]

Hi Sandra,

This would require you to go in manually to each space and update the permissions, similar to the process described here: 

• How to grant access to one space only to a user in Confluence

Otherwise, you'll want to either do this manually using the API or a scripting add-on, or something like this:

• Space Privacy - Extranet for Confluence

Let me know if you have any questions about that.

Regards,

Shannon

[Sandra Meessen]

Hi Shannon, Do I understand correctly that it is not possible to set default the permissions on Personal Spaces to "completely restricted"? 

When I create a new Personal Space to a user, I see that the default setting for the restrictions is "unrestricted". Can we change that on our complete Confluence instance to default "restricted with a specific group"? Thank you and regards,

[Zak Laughton]

Hi Sandra,

It's not possible to set default permissions for a personal space, but there is a feature request open for this functionality in Atlassian's public ticket tracker: CONFSERVER-36726 – ability to set personal/global space default permissions. You can watch the ticket to receive updates, and vote on the ticket to help prioritize implementation according to the Atlassian Implementation of New Features Policy.

In the meantime, there are also some 3rd-party workarounds suggested by others in the feature ticket comments that may work.

–Zak

[Thomas Øhrbom]

A personal space should of course by default be personal, and not open to everyone. That should be elementary!

Sad to see that nothing has happened with that ticket since 2015. BTW the corresponding Confluence Cloud issue is CONFCLOUD-36726. Vote and comment, people!