When faced with something like this I usually start asking questions. (And the answers usually point to the need for some process change rather than new design ideas).
If user X does not have permission to edit the data, what is the benefit/need for them to know that someone else can edit it? i.e. Why indicate that it's editable for user X when it's not (for user X). Since the app already knows user permissions, craft the pages so that the permissions determine the presence (or absence) of the Edit Button next to the field. Users with permissions see the button, users without permission don't see the button. If there really is a need for user X to know that someone else can change the data (and user X has some dependency on others for making those changes)...and...if sensitivities are an issue...identify the users who have permissions anonymously and have the messaging contain a link to alert the permissioned folks. (ie: "Send change request to [this data field's] administrators") FYI - The grayed out concept may not be understood 100%. I worked on an app where the grayed out concept was used (not for permissions, but for indicating that a form was not complete/ready to be submitted) and tons of users thought it was just "broken" (due to low confidence in the app because of a myriad of other usability issues) and they constantly called the support folks to have it "fixed". . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=43209 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
