In addition, as a Salesforce ISV/SI partner there are development orgs, branch orgs, packaging orgs, testing orgs, patch orgs, release orgs, trial orgs, and more. Throw in my company business org, the Salesforce Success Community and Partner Community just to make it fun. That's a lot of org credentials to remember and access on a daily basis.
Here is how I keep track of it all. My focus is on using Chrome, as it is my browser of choice and is available across platforms.
Force.com Logins Extension
First of all, Force.com Logins, an extension for Chrome is my best friend. This extension helps manage login information across multiple environment with one-click login. With support for production, developer, sandbox and pre-release orgs, it covers all my needs. You can easily add a login/password for an org and assign it to a group. Optionally, include a description and the security token, which helps when using development tool. Then with one-click from within Chrome, you can launch a new tab, window, or incognito window and automatically log in.
To keep similar org credentials together, you can define your own set of custom groups. Then assign specific accounts to a group, which will keep similar accounts next to each other. I put together all of my pre-release orgs, beta testing orgs, trialforce orgs, and so forth together in their own groups. For example, under my Trialforce group, I have a login for the TMO (Trialforce Management Org), and different TSO (Trialforce Source Org) variations.
To keep similar org credentials together, you can define your own set of custom groups. Then assign specific accounts to a group, which will keep similar accounts next to each other. I put together all of my pre-release orgs, beta testing orgs, trialforce orgs, and so forth together in their own groups. For example, under my Trialforce group, I have a login for the TMO (Trialforce Management Org), and different TSO (Trialforce Source Org) variations.
Finally, be sure to use the Options tab to enable encryption and understand the security implications of stored usernames/passwords. If you are working across computers, an Import/Export option allows the data you have entered to be moved.
Update (January 11, 206): Force.com Logins has updated their extension and license terms. If you have 10 or fewer logins, it is free. If you have more, there is an annual fee (currently $3/year).
Login Naming Scheme
With all the different orgs to track, I follow a naming scheme for my logins. First, I have admin accounts in just about every org. However, I also tend to use other user accounts for demo or testing purposes. For example, an internal and external user account when working with communities. To try an keep the scheme easy to use and remember. Here is what I do in three simple steps
- All logins take the form of an email address - prefix
@domain.com -
The type of login goes as the prefix. For example, all of my administrator logins are admin -
I add a suffix based on what the org is for. For example, .dev or .demo
Salesforce My Domains
Go to Setup | Administer | Domain Management | My Domain and pick a name. The domain will be in the form of https://<your name>-dev-ed.my.salesforce.com. You will have to check for availability and it cannot be changed. So act fast before all the good names are gone. Starting with Winter 16, My Domain is required to use Lightning Components. So getting it in place now is a good idea.
For those using Force.com Logins, there is an Other option for Org Type. Be sure to provide your custom domain when setting up or editing an org login. This ensures you can login to different orgs within the same browser.
Chrome Person Profiles
So this takes care of the majority of my use cases. However, my usage pattern includes certain orgs that I am in all day as well as a bunch of others others that I tend to hop in and out. For example, my main business org is open all the time. This is also the org I use to authenticate to the Salesforce Partner Community as well as the Salesforce Success community. As these communities have time outs for inactivity, I find I have to reauthenticate multiple times a day. If I have another developer org open, often the wrong credentials are passed over.
To solve this issue, the ability to setup multiple users in Chrome comes to the rescue. You can easily add multiple people to Chrome. Once you are signed into Chrome, the current user is shown in the upper right hand corner of the title bar. If you click on it, there is option to switch persons. From the next screen, you can add another person.
You will have to setup a separate email/password or use a guest account. Once another person is setup, you only have to right click on the user to switch to a different one. You can also opt to pin the browser to the task bare with the different users logged in.
With two Chrome person profiles, I keep one open with my main business org and the communities. The other is used to log into various environments with My Domains enabled.
Chrome Incognito Window
Recap
So that’s my setup to help make managing an abundance of Salesforce logins manageable.
-
Force.com Login Chrome Extension -
Use of My Domains -
Separate Chrome Person Profile for main org and the rest -
Incognito Window for one-offs
Let me know if you have additional tips and tricks to share.
Good info CARL BRUNDAGE!
ReplyDeleteExcellent information even today. over a year later. I use similar info. Instead of the FORCE.com Logins, I use LastPass, which is free. The drawbacks to this is that if using My Domains, LastPass doesn't recognize subdomain and I'll end up trying to login to .force.com instead of login.salesforce.com. It isn't a huge problem though. I will typically keep the SF home page as my browser home page and then just hit CTRL-H to open the home page and login. It's certainly not as nice as Force.com Logins, but it's the free way around it.
ReplyDeleteThanks for sharing the article.
ReplyDelete