Weeks ago, I had the chance to talk to a number of the Executives and Key-players at TBS Factoring. I had not seen this much excitement over the Salesforce Platform in a long time. They have the driving ambition to revolutionize their industry through technology. They picked up Sales Cloud, Einstein and Heroku last Fall and were priming the pump for a full implementation. They have a fleet of Developers ready to build a well-oiled machine. Salesforce is to be at the center of it all and they needed an Admin to bring this baby online. When presented with this mountain of a challenge, who can turn their back on this opportunity? I worked with my friends at World Water Works to close out as many projects as possible and said my goodbyes. It’s a weird moment when you are deactivated from your very first Org, your baby that you built from the ground up over the last 7 years… Still, onward we go. My newest Adventure as the Salesforce System Administrator at TBS has begun!!!
I will have a ton of questions and I will learn about so many new features that before had never been in my realm. My objective is to post my progress every week on the Cloud Force Collective site. I encourage each of you to hold my feet to the fire on this project; to ask follow up questions; to guide me when you see me driving in the wrong lane; and to use this series as a tool for any Admins implementing their own Salesforce Org.
On that note, the first week on the job always starts off slower than one would prefer. After the obligatory HR Meet-n-Greet, my first day was spent introducing myself to all the teams I will be working alongside. I loved how their eyes would light up when I told them I’ll be setting them up on Salesforce. Very few people didn’t know what Salesforce was and EVERYONE was excited at the opportunity to get it going. At my last place, I always commended the passion I found in some of our Executives and Directors. Here at TBS, I am aghast at the passion I find in EVERY SINGLE PERSON.
On day two, we all took a Cupcake break together to celebrate our President’s birthday. On day three, we shut down the whole shop to hold the first annual TBS Talent Show. I was too late to sign up, so they have to wait a year to hear my Accordion skills. No worries, though. That Passion I spoke of earlier came blasting off the stage. We had Salsa and Flamenco dancing. There was some raucous lip-sync dance-offs and repurposed SNL sketches. There was a Garth Brooks song that stunned the room to silence and a Broadway number about Lattes that would have had Kristin Chenoweth hide her face in shame. The talent and passion here at TBS is second to no other work environment I have ever seen.
Day four, I was finally able to login to Salesforce!!! <<<INSERT YOUR PREFERED CELEBRATION GIF HERE>> Waiting three days to get access to the system you’re hired to Administer might seem painful… and it was. My predecessor was never deactivated because she will continue on as a consultant. If she had been deactivated, we may have been able to figure out who in the system was set up as a SysAdmin. Remember, the Org was quite new and had only been used for demonstration and testing so far. When we did get ahold of the original Admin, she couldn’t get in due to Single Sign On. The one thing she did set up was SSO. Since her company Microsoft account was deactivated she couldn’t get into Salesforce either (This was not the last time I tangled with SSO). We had an amazing game of tug-o-war with Salesforce Support to grant me access. It wasn’t until my AE looked up who had the SysAdmin profile in our system that I finally got keys to our Org. I am not sure what one can do to avoid this type of Comedy of Errors. All I can advise is, treat your System Administrator login like keys to the house. If you accidentally lose your keys, have another set under a rock somewhere.
Where was I?
There were two people involved in setting up SSO for our Salesforce Org and neither one is still here. I was assured that this should be a simple set up and not any real trouble. The first time I logged into our Org, it was through the “Set up your Password” email. When I timed out later that day, I couldn’t get back in. My Tech Department brethren helped me late into the afternoon figuring out how to get back into Salesforce. My boss insisted that we not kill SSO altogether, for which I should probably thank him. Once we understood how to set up the connection on the Azure side, it was a bit more fluid. I still had to open a case with Salesforce so I could allow the Tech team to bypass SSO if necessary.
TIP: There is a System Permission under Profiles and Permission Sets called "Is Single Sign-On Enabled". You have to open a case with Support to make that setting visible.
What is one of the first things you do as a responsible Admin? I’m assuming all of you said in unison, “Spin up a Sandbox!” Something new I learned about that. Under My Domain, you can Prevent login from https://login.salesforce.com. This apparently transfers to your Sandbox and if you have SSO turned on, but not set up from the other side (in my case, this would be MS Azure) you will be locked out of your Sandbox. Even the Login button from the home Sandbox page was shutting me out. I still have a ton to learn about Single Sign On. I appreciate my boss not letting me walk away from something because it was a nuisance. The end result will make Salesforce a friendlier place for my Users, which really is my objective here. Keep posted on future fights with SSO.
Next Week on The Implementation:
…so what would you do in this situation? Exactly, you would dress up a dummy as an SSO effigy and muster up your best “Rowdy” Roddy Piper impressions.