Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permssions UI #1702

Closed
petervo opened this issue Jan 21, 2015 · 5 comments

Comments

Projects
None yet
3 participants
@petervo
Copy link
Contributor

commented Jan 21, 2015

We need to decide on a standardized UI for what the interface should look like when the user doesn't have permission to perform certain actions.

@petervo petervo added the needsdesign label Jan 21, 2015

@andreasn andreasn self-assigned this Jan 21, 2015

@stefwalter

This comment has been minimized.

Copy link
Contributor

commented Jan 22, 2015

Current UI:

screenshot from 2015-01-22 12 13 23

Possible UI working with disabling buttons, links etc:

screenshot from 2015-01-22 12 11 47

@andreasn

This comment has been minimized.

Copy link
Contributor

commented Jan 22, 2015

UI looks good. The other option would be to hide the controls, but I think this is better.
Should it mention that you need to talk to another sysadmin to get permissions?

@stefwalter

This comment has been minimized.

Copy link
Contributor

commented Jan 22, 2015

Lets put the user name in the message, instead of 'You', so that it's clear that it's a problem with that user account.

@andreasn

This comment has been minimized.

Copy link
Contributor

commented Jan 22, 2015

So there are two different cases here:

  1. Scruffy is the single sysadmin on the server, but logged in as 'scruffy' instead of 'root'. The solution for him/her would therefore be to log out as 'scruffy' and log in as 'root' and either perform the 'Add Bond' action, or go into Administrator Accounts and make sure that 'scruffy' are allowed to do things like that for now and in the future.
  2. Scruffy is a junior admin in a team of 5 people led by a senior sysadmin, lets call him Alfred. Alfred have for perhaps good reasons decided to restrict Scruffy's network admin rights. So Scruffy needs to get in contact with Alfred in order to sort this out.

If we change the help text to "The user 'Scruffy' is not allowed to modify network settings" it would help usecase 1, and to some extent 2, even if it makes 2 feel a bit less natural.

@andreasn

This comment has been minimized.

Copy link
Contributor

commented Jan 22, 2015

I really like the disabled UI over the dialog in general. The dialog is very surprising with no indication that the action is impossible to do and cuts you off from the rest of the UI until you close it. I would in general advice against dialogs when there is only one action to perform (to close it in this case). This is also what is recommended by the GNOME HIG and by the book Designing Interfaces (by Jenifer Tidwell)
https://developer.gnome.org/hig-book/2.32/hig-book.html#windows-alert
http://designinginterfaces.com/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.