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


Permissions and inherited permissions are confusing on Confluence. I need help determining who has access, how to grant access, and restrict access for a site that I created for our Department.

1 answer

0 votes

I'm old and have been here for a long, long, long time, so I do not find them confusing.  I will try not to bore you too much, but it is very complex nowadays.

A user can log into Confluence

  • The space permissions say they can see things
  • The space permissions say they can do other things
  • Pages within those spaces may stop them seeing pages, and/or editing them
  • If the space is set up as a "knowledge base" then Jira customers can also (sort of) view it, without any other permissions.  And they don't need a Confluence login either.
  • There is an "anonymous" option - never give that anything other than "read pages"
  • Atlassian introduced "guest" accounts a while ago - single space, can do whatever your space admins allow

I'm sticking with "it is complex".  But start at the top of the list I gave.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events