If you want to change your enablement site’s subdomain name after it was first created, you can submit a Salesforce Customer Support case.
Required Editions
| Available in: Enterprise, Performance, and Unlimited Editions |
| User Roles and Permissions | |
|---|---|
| Enablement Site User Roles | |
| This topic supports these enablement site roles: | Salesforce Admins |
| Required System Permissions | |
| To create a subdomain and initial content collection: | Manage Site Settings |
-
Access the Salesforce Customer Support page.
- Log in to the Trailblazer Community.
- From the Community tab, select Salesforce Help.
- From Salesforce Help, click the Contact Support tab.
-
Create a case.
- On the Salesforce Customer Support page, click Create a Case.
- Select Product or Technical Support.
- For Product, select Other Salesforce.
- For Topic, select myTrailhead, and then click Next.
- Enter your org ID, and then select Production for Instance Type.
-
In the Details section, include this information.
- Specify that you want to request to change your enablement site’s subdomain name.
- Include the current subdomain name and the new name that you want to use.
- Complete the remaining fields, and then click Create Case.
-
After your case is resolved, publish a release on your enablement site to establish the
relationship between your new subdomain name and your existing content collections.
Note Changing the subdomain name doesn’t affect your existing content collection records, but your enablement site doesn’t automatically propagate the new subdomain name to your content.- Log in to your enablement site at its new login URL. For example, if you changed your subdomain name from purealoe to acme, log in at https://acme.my.trailhead.com instead of https://purealoe.my.trailhead.com.
- In Trailmaker Release, create a release record.
- In Trailmaker Content, add content to the release. Even a minor content change is fine.
- In Trailmaker Release, validate and publish the release.
Note Because of caching, it can take some time before the new subdomain name propagates to
your site URLs, including your login URL and links to your published content.