My issue is that I have a space that I use to store documents for various applications that I help support. The people that I give access to shouldn't be able to view (not relevant) the other branches. Yet, if I give someone view/edit rights to a child article, they also need view rights to the parent branch. I guess my expectation is that view/edit right on a child branch will override whatever rights are inherited. Think of it as child rebellion going against parent wishes.
I see this as a pro.
Is there a downside to this that Atlassian decided this is how inherited rights should work? Is it a matter of trying to communicate security rights in a simple manner that doesn't allow for this flexibility? I certainly understand that.
Because it is up to the space administrators to decide who can see something. Your system would enable anyone to grant access to anyone. The reason it's done this way is simple - there's no coherent permissions if you don't do it this way, you might as well just grant view to the whole world automatically.
I am the space administrator and set the permissions. I gave someone access to view/edit a child wiki article, but I had to first them view access for the parent. I just tested and that person can adjust the security rights on the parent nor child article.
Are you perhaps referring to a different situation than what I'm describing?
I feel like I have to open up access to more people on the parent level just to child wiki article open correctly, let alone be editable.
Maybe you can explain in more detail where I am misunderstanding your point?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, imagine you are the space admin, and you have a space you do not want shared with everyone.
I'm one of your page authors, I have no idea about your rules on sharing, and so I can now let my friend in another department see it, without your knowledge? That's what you've just described - a complete loss of any level of security.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.