I have a simple interface for managing a user's account in a web app. Clicking each button in the interface performs the action immediately:
This is what it looks like when an account is disabled:
Sign outbutton is only displayed when the account is online.
I know the icons are a bit odd, but I couldn't find any suitable ones in the Balsamiq editor. I am using suitable ones in the actual application though.
Disabling an account immediately signs it out as well.
If the account is logged on:
Disable Accounttriggers a modal to confirm that we will disable and log off the account. If the user proceeds,
Disable Accountfades out and a button called
Enable Accountfades in.
Sign outbutton display a modal to confirm that the account will be logged off and he will lose any unsaved changes. If the user proceeds, the
Sign outbutton fades out.
If the account is not logged on (
Sign outbutton is not displayed):
Disable Accountfades out the
Disable Accountbutton and the
Enable accountbutton fades in, in its place.
Delete accountbutton pops up a modal to confirm as this is impossible to reverse. We then redirect the user back to the list of accounts.
I am considering displaying a flash message when
Sign out is clicked:
However there are some problems:
Is it necessary to display the flash message when
Enable accountare clicked? These 2 behaves like a toggle button and perhaps the buttons fading into one another can provide adequate feedback.
The flash message fades in and pushes down the buttons (which are also fading in). There seems to be too much going on. Is there a better way to do this? Studies/testing reports that talks about when too much feedback is too much would be helpful with this situation.