skip to Main Content

Why You Should Set Up ‘My Domain’ Today

Set Up My DomainWith the Spring ’17 release, Salesforce will be enforcing the My Domain feature. This will impact any partner or customer with a Salesforce org (but not Developer orgs), so your organization will likely be affected. Here’s what you need to know.

My Domain is a feature that allows you to add a subdomain to your Salesforce org URL. This lets you emphasise your brand, plus it helps protect your org. For example, with a subdomain you can block page requests that don’t use the new domain name, define a custom login policy to control how users are authenticated, and work in several orgs at the same time. My Domain is required to use single sign-on (SSO) with external identity providers. It’s also required for certain custom or third-party Lighting components, such as tabs, pages and the Lightning App Builder.

Finally, enabling My Domain will help Salesforce deliver a smoother maintenance experience. That means streamlining maintenances such as instance refreshes and migrations.

So why should you set up My Domain now? It’s simple: If you want a good domain name, you must choose it now before another company scoops it up. I’ve set up my company’s domain as nuvem.my.salesforce.com; now, no other company can use the same name.

Setting up a My Domain Name

This step requires you to carefully consider your unique domain name.  Choose wisely, because once you’ve registered, only the customer support team can change it. Domain names can contain up to 40 letters, numbers and hyphens. (Sorry, it can’t contain “salesforce.”) And names must be unique—Salesforce will check the availability of your name before you can register it. You’ll get an email once your domain name is ready for testing. The name will be available once you test and deploy it.

Tips for Testing My Domain

Here are some things to consider when you’re testing out My Domain:

  •   Click all tabs and test out as many links as you can. Every page should show the new domain name.
  •      Make sure to update all application URLs (for example, the Email Notification URL field in Chatter Answers).
  •      Don’t forget about custom buttons or Salesforce pages, which may end up with broken links because of hard-coded references. You should also ensure that third-party apps(?) don’t use hard-coded Salesforce server references either.
  •      Links that originate from emails should use the {!Link} function. These will show the new subdomain URLs after the domain is deployed.

Setting the Login Policy

If a login policy isn’t set up, users can make page requests without your new domain name (when using old bookmarks, for example); they’ll simply be redirected after login.

There are 3 options for redirect:

  1. Redirect to the same page within the domain
  2. Redirect with a warning to the same page within the domain (recommended for a few days to help users transition)
  3. Not redirected (requires users to use the new domain name)

I also suggest leaving the Prevent login from https://login.salesforce.com box unchecked, unless you plan on implementing SSO.

Once you’ve deployed My Domain, you can let users authenticate using alternate identity provider options, right from the login page. In addition, once My Domain is up and running, you can use the Domain lookup tool to get system performance and maintenance information.

Back To Top