Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

Restrict a group from viewing KB that is linked to JSD


We have a KB (shared Confluence space) for ProjectA. Also, we have a set of licensed users from ProjectB that should have access to Confluence. The problem is that users from ProjectB can see ProjectA KB Confluence space.

How can we restrict ProjectB users from accessing ProjectA space?


Here was the similar question 4 years ago:

1 answer

1 accepted

0 votes
Answer accepted

Hi Alex,

I remember designing the original JSD knowledge base feature when I was still at Atlassian. We needed a way for portal-only users to view KB articles through the JSD portal without a Confluence license. To solve this, we created a new permission for Confluence spaces - ‘any active user can view’. This functions a bit like ‘anonymous access’ but requires the user to be logged in.

You can see on the space permissions screen when this is active for a KB space.

Screen Shot 2023-05-11 at 12.55.03 pm.png

Any user who can login to your Atlassian site (i.e. isn’t suspended) can view spaces that have this permission turned on, including portal-only users.

Confluence doesn’t allow users to be blocked from a specific space (although this would be a useful feature), so there are only two ways around the problem you have currently and both come with compromises.

  1. If the ProjectB users in your example only need access to one space, you can use the new Confluence guests feature (which is in beta) to limit them to one space in Confluence. This will block them from all other spaces, including KB spaces with the ‘any active user can view’ permission turned on (they then won’t be able to view these spaces through the JSD portal either). This is probably your best bet.

  2. If the users for ProjectA have Confluence access, you can change the KB space permissions to ‘only Confluence users’ in the knowledge base settings page for the JSD project and then use normal Confluence space permissions to restrict which spaces each group of users can view. I’m guessing this is not the scenario you're in, but worth mentioning.

Good luck! I know permissions can be a headache.

@Judd Garratt , thank you very much!!! Point 1 works like a charm! You saved me tons of time!

My pleasure! Glad to help :)

Like Alex Gavrysh likes this

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events