The only exception to the above rules I can think of is when a user can never use a particular tool. Or when they can only use it should someone give them new permissions.
An example of this might be admin tools that only a site administrator needs, such as deleting posts on a forum, or a menu item that lets them handle user types. However, I also think a change like this should come with a new-first-run message saying why their interface suddenly changed. Another example of this might be very-large scale applications for big business, Custom suites where there may be hundreds of interfaces that a user -might- need, but it is easy as pie to know that someone in accounting isn't going to need the marketing screen, and neither of them is going to need the HR screen. However this leans more into the idea that different users need different software, and these different screens, even if part of the same overall system, are like different pieces of software. Kind of like how an office suite comes with several applications and most users never bother with most of them. The mosts they pick just so happen to be different. Will . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=36261 ________________________________________________________________ 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
