Using Chrome to connect to multiple Salesforce orgs - at the same time!

I’ve been using 3 browsers to be logged into each of my Salesforce orgs (environments). I was doing this because any time you logged into a new org, all the tabs and windows would start using that new org. You could only be logged into one org at a time in each browser.

I was shown a way to do multiple connections using Chrome.

In the upper right corner of the Chrome window, next to the URL bar, there is a button with three lines. If you left-click on it, a menu pops-up. Select the “Settings” option.

This will take you to a new page. About halfway down the page is a section called People.

There will be 1 entry in it if you haven’t done this before – it will say: Person 1 (current)

If you select this entry, the Edit button is accessible below it. You can change the name and the icon for it.

Now comes the good part…

Each Person entry in the list can be used to create a separate instance of Chrome – they do not share anything like bookmarks, history, etc. They do share the “Settings” page.

If you click on Add Person button a new window pops up and lets you change the name, select an icon, and whether or not a short-cut is created on the desktop. When you click the Add button, a new Chrome window will open up. Click on the original Settings window and add more if you like.

I setup People entries called: Production, QA, COEDEV, CPQ and Training to correspond to my Salesforce orgs that I use.

After you have added a Person, you will notice that the icon to the left of the Minimize button (upper right corner of the browser window) changes from an image of a person to the names of the Persons you have added.

You use this button to switch between instances of Chrome. Right-click the button and a list of People will be displayed. Select one of them and new instance of Chrome will start up or, if it’s already started for this person, you are taken to the window.

This allows you to log into different Salesforce orgs at the same time using Chrome.

For me, this will save 10-15 minutes for each change set deployment while I’m waiting for them to deploy before I switch back to my development sandbox.

Thank you, John Coppedge, for showing me this!