Confluence restrict user to a specific space

We are currently have one lcient with access to our confluence on demand, they are in the confluence-users group with changes made to confluence recently they can now see all spaces.
How can we restrict them to their own space.

They are also added to their own group.

5 answers

1 accepted

I had to go through each space and remove the confluence-users from the allowed groups. THe confluence-users are also not the within teh default group that gets assigned to any space so it has worked out ok. I had to follow

Nic Brough suggestion

3 votes

Hi Anthony,

You'll have to change the permission schema of all spaces and remove the confluence-users group from the ones you don't wish them to have access. You may want also to create a new group for these users and allow this group to access only the spaces they have to by changing the space permissions. I know this might take some time but it's necessary to change the permissions again.

Cheers,

Rodrigo

I don't think the solution is to take confluence-users off all spaces. Where are you setting this users groups? What happens if you remove just him from the confluence-users group?

If i remove from confluence-users they do not have access to confluence at all.

When we had it set it up there was no confluence-users group. Atlassian added that and know you must be part of that group to access confluence.

Apologies,

If you give this customer group you have created for this user the same global permissions as the confluence-users group he should be able to log in.

Yes he will be able to login but then he has permissions to all spaces. Hwo do i restrict the access to once space only?

Apologies,

Let me organize my thoughts a bit better.

1) permit the custom group he is in on the global permissions. This will allow a login.

2) remove him from confluence-users group to remove permissions on most of your site content.

3) add space permission for his group on the space you want him to be able to access

4) Access should be restricted to that single space and nothing else without having to juggle the confluence-user permissions on all spaces

I'm afraid Anthony is essentially correct here. Confluence-users is a group that says "can log in". If it's used in permissions to allow any more access, then all users in the group will get it. So you *must* unpick that if you want to restrict someone's access.

Daniel's solution is one approach, but has a significant problem - every new user you add from then on will be added to both confluence-users and the new group. So you may need to remove them from groups after creating them. The best solution is to slog through the hard work of separating "can log in" from all other permissions.

I do also agree with Nic, my idea was to separate the can use permission from other permissions. That may cause some hard work but it will work. :)

Let us know your thoughts Anthony

Apologies,

Let me organize my thoughts a bit better.

1) permit the custom group he is in on the global permissions. This will allow a login.

2) remove him from confluence-users group to remove permissions on most of your site content.

3) add space permission for his group on the space you want him to be able to access

4) Access should be restricted to that single space and nothing else without having to juggle the confluence-user permissions on all spaces

Apologies,

Let me organize my thoughts a bit better.

1) permit the custom group he is in on the global permissions. This will allow a login.

2) remove him from confluence-users group to remove permissions on most of your site content.

3) add space permission for his group on the space you want him to be able to access

4) Access should be restricted to that single space and nothing else without having to juggle the confluence-user permissions on all spaces

In case anyone else has a similar issue (like me) and the other answers don't solve it.

In my case, I don't know why, but Anonymous had been granted a number of permissions in Space Permissions. When I removed them (no current need for anonymous access) then the client's user group became restricted to the client space, as I hoped.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Kesha Thillainayagam
Posted Apr 13, 2018 in Confluence

We want to hear how your non-technical teams are using Confluence!

Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...

2,624 views 25 10
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you