-
Notifications
You must be signed in to change notification settings - Fork 9
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
Should additional methods always be indicated as not completed? #302
Comments
Ideally we have as many factors configured on an account. However, we also received feedback during a walkthrough that the "x"'s icons were intense. |
Perhaps a non-red icon could be used to indicated |
We could move to the |
I like those explorations. Thanks for the thoughtful takes. I think the timing may not be right to make such a drastic change as most of our communication has gone out (recently) and it includes many screenshots of the current UI. I think the options you've presented do add some subtle and interesting improvements, but I think for now I would prefer we implement minimal changes while we help the remaining users configure their 2fa. I'm inclined to just change the color and use a friendlier icon for now. @pkevan Thoughts? |
A smaller change can work. I don't know the color change is really meaningful, though, I'd hade to see a red splotch next to a security key if I'm never going to add one. |
I somehow wonder if we're attempting to do this wrong by putting everything on the same screen when in fact we want users to have 2 out of 3 setup? Should 2 Factor methods (key, totp, backup) be it's own screen? Either way, we need it to be clear what is or isn't required, and anything with red or a |
That's a good point, see #291. |
In the above screenshot, it would appear like it's expected (by the user) to have TOTP and backup codes - pretty sure it's expected that an additional backup method is set, but not two.
The text was updated successfully, but these errors were encountered: