New issue
Advanced search Search tips

Issue 714205 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

Log-in from account switch event?

Project Member Reported by k...@chromium.org, Apr 21 2017

Issue description

Description:
It would save a lot of steps and confusion if the user could log-in to a second account when they hit ctrl-alt-. and it isn't logged in yet.

Use case:
The user reboots the ChromeOS device, due to an upgrade most likely, selects an account from the ones present, and logs in. The user then hits ctrl-alt-., selects another account (or perhaps it defaults to the only remaining one), and logs into that one.

Motivation:
After the user reboots a ChromeOS device and logs into one of the accounts on it, the only way to log into a second account is to dig around the menu in the bottom left.

Worse is that there is no obvious indication whether a second account is already logged in, so if the user doesn't immediately, on power up, log into that second account, they may forget if it's logged in, hit ctrl-alt-. and sit for a couple seconds wondering if the device is just slow. After giving up, the user can go dig around the menu to verify that the other account isn't logged in.

I'm calling this an enterprise issue because many corporate or academic users also have their personal account on the device, and didn't see a general feature request category. Feel free to correctly categorize.

Existing workarounds:
If there is another keystroke to take the user back to the very helpful log-in screen, I'm unaware of it. The only workaround known to me is to go dig around the menu. An indicator on the main screen whether a second account is logged in might save the user a step.

 
Components: -Enterprise UI>Shell>StartScreen
This probably is not pure enterprise. Removing "Enterprise" label.

Comment 2 by pbe...@chromium.org, May 12 2017

Owner: zalcorn@chromium.org
Status: Assigned (was: Untriaged)
Please review whether this is something you want to do.
Status: WontFix (was: Assigned)
Agree this would be nice for our current implementation, but we're examining a major overhaul of multi-profile for later this year and would prefer to invest energy there. Closing as wontfix in anticipation of new implementation solving this and many other multi-profile issues.

Sign in to add a comment