Reputation: 1292
From what I can tell, if you ever use 'deny' to anything, it overrides EVERYTHING and denys access. For example, you have a 'contributors' group and you want to 'deny' them 'Manage Branch' to keep people from making branches.
Sounds good, but as an Admin, I happen to also be in that group, and even though I have set 'project collection administrators' group to 'allow' the 'deny' overrides it!
I'd like to change this behavior to grant access if any of my permissions grants it (like about every other security model I've worked with) as it is, it looks like I need to be sure that none of the admins are in ANY other groups - or we will be locked out of those!
This makes the 'deny' almost useless - only good for creating a 'former employees' group or something where you want them locked out of everything and want to be able to turn that on.
Oh, I'm using TFS 2012
Upvotes: 1
Views: 642
Reputation: 59073
That's correct. The Deny
permission trumps all other permissions.
Think of it like this:
Allow
means something is explicitly allowed.Not Set
means that something is denied unless it's overridden by an Allow
.Deny
means that something is denied even if it's Allow
ed elsewhere.It's worth noting that this is exactly the same as how Windows security works.
Upvotes: 6