Enable My Domain in Your Development Org

For security purposes, Lightning components require you to define a custom Salesforce domain name for your org. Setting up a new domain is simple, but it takes a few minutes before it’s available for use. When you enable My Domain, references and links to Lightning resources are in the format https://yourDomain.lightning.force.com. Use a Developer Edition org for this exercise.

Enable My Domain in Your Org

Before we get to the heart of creating Lightning components, let’s use Salesforce My Domain to set up a subdomain. Is setting a My Domain a requirement? Yes, if you want to use Lightning components in Lightning tabs, Lightning Pages, or as standalone apps. Salesforce requires My Domain as a security measure to help prevent malicious attacks—just in case a security hole lies hidden deep within a third-party or custom component.

If you already have My Domain enabled in your DE org or use a Trailhead Playground org, skip this section and the next one. You already have My Domain set up.

If you don’t have a subdomain yet, it’s easy to set one up.

Every Salesforce org is set up within the salesforce.com domain with a URL like https://na30.salesforce.com. With My Domain, you define your own domain, or a subdomain, within the salesforce.com domain. Your new URL looks something like: https://yourDomain.my.salesforce.com.

Use the My Domain wizard to create a subdomain.

From Setup, enter My Domain in the Quick Find box, then select My Domain.
Enter the name for your subdomain after https:// and click Check Availability. Typically, a subdomain is your company name, but you can use any name as long as it’s unique. If this name is already taken, choose another one.
Click Register Domain.

Salesforce updates its domain registries with your new subdomain. When it’s done, you receive an email with a subject like, “Your Developer Edition domain ready for testing.” It takes just a few minutes.

Did you catch that last part? It can take a few minutes before your domain is available. You can’t move to the next step until you get the activation email.

Important

Roll Out My Domain to Your Org

Did you get your activation email? From the email, click the link to get back to the My Domain wizard. It takes you to Step 3, where you test the links to your subdomain URLs before rolling out the subdomain to your org. Even though you don’t have users to deploy it to in your DE org, you must still roll out My Domain to make your custom Lightning components available in Lightning Pages, in the Lightning App Builder, and for standalone apps.

Click the link in the activation email to log in to your Salesforce subdomain. It takes you to your Salesforce org.
Notice that the URL in the browser address bar shows your new subdomain name. Right now, you’re the only one who has this URL.
Click around your org to make sure that links point to your new domain. You probably haven’t created links in your DE org, so we can go on. (When creating a domain in a production org, this important step is easily overlooked.)
From the My Domain page, click Deploy to Users, and then click OK. Deploying a subdomain rolls out the new subdomain URL throughout your org. Now all your users see the subdomain URL in the browser address bar.
Step 4 of the wizard displays configuration options, which we can ignore for now.

Congratulations, you’ve set up My Domain! When setting up My Domain in a production org, you have a few more steps. Learn more by completing the My Domain unit of the User Authentication module. Now that you’ve protected—and branded—your org with a subdomain, let’s go on.

Force.com IDE Developer Guide

Enable My Domain in Your Development Org

Enable My Domain in Your Org

Roll Out My Domain to Your Org