hard to understand launchpad permissions in the ui

[Martin Pool]

People have a lot of trouble understanding Launchpad permissions, including:

 * not knowing whether they don't have access or they're just not looking in the right spot
 * not knowing just what access in granted by membership/owner/registrant etc
 * not knowing who to ask or what to do when they should have access to a particular object

When you don't have permission to use a particular control in the Launchpad web ui, it would be nice if

1- Launchpad showed it greyed out and/or with a lock icon, rather than hiding it entirely. (At least in some cases; perhaps obscure or admin controls should always be hidden.)

2- The tooltip for the lock icon described the permissions that guard that interface, eg "only for bzr project admins ~bzr"

Thread about this https://lists.launchpad.net/launchpad-dev/msg02157.html

[Matthew Paul Thomas (mpt)]

One example of this is bug 179587 (explaining why you don't have permission to access a bug report). The privacy considerations there might extend to other entities.

[Gary Poster (gary)]

This sounds important to me for the Launchpad project. We need to have someone other than myself triaging ui bugs, and responsible for them. I will pursue this. However, if this is in the Foundations team's queue, it is a low priority for us specifically.