Comment 10 for bug 700724

I can understand the security ramifications, but I am not fond of the chosen solution. I do admit I am unaware of the internal plumbing so my idea may not be possible. I am curious if it is possible to:

1. have a 'flag' for the parent team to prevent inheritance of permissions?
2. add a level of member that has no permissions to perform teams tasks; many CMS systems have this 'reader' level vs. 'contributor', 'admin', and 'owner'.

I hope we can all work towards a solution that works for both sets of needs.