WenU wrote:Clearly defined responsibilities are a help but loose control of access leads invariably to unnecessary problems.
Clearly defined responsibilities are not just "a help" -- they are essential. No matter what MLS does with permissions (and you'll see in my next paragraph that I agree that the permissions implementation should be adjusted), it is appropriate and actually required that multiple people in a ward have permission to perform each of the MLS roles. Thus if you are looking to MLS permissions to avoid people stepping on each other's toes, you are bound to be disappointed. There is no substitute for good leadership and organization to define who has each primary responsibility, and who backs up the primary person when he or she is not able to perform a required task.
WenU wrote:I feel the Edit Membership facility should be disconnected from View Recommends. Those needing Edit Membership access can easily have that allocated in System Settings. For the record, I fail to see why viewing Move In/Out requires Edit Membership rights.
I agree that viewing recommends and editing membership should be disconnected. I would guess that this was an implementation oversight, but perhaps there is some technical reason why it was done this way. In either case, as a general principle, granting one permission should automatically grant another permission only when those permissions are inextricably connected (for example, it is impossible to do financial work in a ward if you can't see the members).
WenU wrote:All of these can be implemented on a discrete basis. So I am asking the rationale behind automatically linking access privileges . . . Why do they in fact have to be linked?
This would be a question for the product manager or developers of MLS; you're not likely to get a response to that question on this forum. As I said before, it's my opinion that they do not have to be linked, but the current MLS implementation simply makes that a requirement. It's good to raise this issue, and hopefully it will be refined in future releases (as has happened with many MLS features over the years).