Enablement is org-wide rather than per site, so one admin doing this changes the whole org. Run it in a sandbox first.
- Enable the feature
From Setup, enter Digital Experiences in the Quick Find box, select Settings, then select Enable Digital Experiences.
- Choose the org domain
Enter a domain name. Salesforce appends my.site.com to whatever you type. Check it against your brand and your published support URLs before you save.
- Create a site
Go to Digital Experiences, then All Sites, and click New. Pick a template, name the site, and enter the URL path that follows your domain.
- Build it and lock it down
Open Experience Builder for branding, pages, and navigation. Then open the site's guest user profile and remove every object the public does not need.
- Activate, then publish
Activate the site to make the URL live, and publish in Experience Builder to push your Builder changes. Those are two separate actions.
The org-wide switch under Setup, Digital Experiences, Settings. It creates the site domain and the Digital Experiences app.
The subdomain that becomes yourname.my.site.com. Entered during enablement, and shared by every site in the org.
Chosen per site. Customer Service, Customer Account Portal, Partner Central, Build Your Own (LWR), and Microsite (LWR) are the usual starting points.
The path appended to the org domain, such as help or partners. Enhanced LWR sites can drop the older /s segment.
- The domain is not editable after enablement. Orgs that typed a project codename are still living with it years later.
- Activating a site and publishing in Experience Builder are different actions, and a published but inactive site serves nothing at its URL.
- Guest access is configured per site, so a second site does not inherit the careful guest profile you built for the first.
Keep the related term in your library so you can find this topic again.