Comment 66 for bug 1073087

It appears that this thread was started in October 2012. Is the "Bug fixed" by now?

Fundamentally the concept is like a Cascading Style Sheet, but it is a Cascading Rights Matrix.

However, there appears to be no way for a general user (except for Admin) to be assigned or have confidence in being a "Super Admin".

One can, in a small operation, logout then login as Admin, to assign problematic rights, but even on that level being confronted with Error messages and forcing this action is irritating and during a evaluation period is enough, it seems to me, to discourage using the program.

Make a simple CHECK BOX that Says "ADMIN" (say for a application or a company or spelled out set of companies, and "SUPER ADMIN" rights that simply allows everything needs to be simple to set and comprehensible.

If a User has access to the "Access Rights" Panel there is a assertion that they ca control that. Beyond that though there needs to be logic associated with what it means to set "Sharing" "Admiistration" "Multi-Companies" and "Technical-Features".

Error Messages need to be more fine grained. If something is not allowed it should be explained why. Some Features do not show up when not given access to them. Otheres are given access but then return errors.

The logic of this needs to be (and I a sure it is thought to be) Top Down. But as a user the full interface of "User Settings" and "General Settings" is not as completely logical to the user and feedback of rights meaning is not as clear as it could be.