Access to Chrome via the System Tray should go through the User Manager.

chrome/browser/ui/browser_dialogs.h

Index: chrome/browser/ui/browser_dialogs.h
diff --git a/chrome/browser/ui/browser_dialogs.h b/chrome/browser/ui/browser_dialogs.h
index 4720070747b9d002ac71066eb9889c0c8f488735..9c853808ed0760d1bc08759cdf9b8d0466ab5759 100644
--- a/chrome/browser/ui/browser_dialogs.h
+++ b/chrome/browser/ui/browser_dialogs.h
@@ -105,6 +105,12 @@ void ShowUserManager(const base::FilePath& profile_path_to_focus);
 // Shows the Desktop User Manager with a specific |tutorial|.
 void ShowUserManagerWithTutorial(profiles::UserManagerTutorialMode tutorial);
 
+// Shows the Desktop User Manager and Task Manager with the chosen profile.
+void ShowUserManagerThenTaskManager();
+
+// Shows the Desktop User Manager and About Chrome page with the chosen profile.
+void ShowUserManagerThenAboutChrome();

[Peter Kasting, 2014/09/11 20:35:02]

In general, I think this whole header was a mistake.  We decided a while back to
get rid of the chrome:: namespace, and these are basically global functions at
that point.  So I'd try to avoid adding to it.

I'd prefer to just expose public static methods in relevant classes.  For
example, you could perhaps replace UserManagerView::Show() with these two
methods.  Or you could have callers just call Show() directly with the right two
arguments.

[Mike Lerman, 2014/09/12 14:26:42]

I addressed most of this in the CL reply. This is differentiated because there
is also UserManagerMac::Show(), and we need a point that can direct both ways. I
can create a UserManagerBase class in chrome/browser/ui with static methods and
#ifdef's implementation that calls UserManagerMac::Show or UserManagerView::Show
as appropriate. Is that the direction you're thinking this should go?

+
 // Hides the User Manager.
 void HideUserManager();