Enable Enhanced Domain with FoundationConnect

Important Announcement

With the release of Winter ‘23 (around October/November), Salesforce will enforce enhanced domains for every customer.

update November, 2022: Salesforce has again extended that timeline to Winter ’24 now – your enhanced domain will automatically be enabled in October 2023. In the meantime, you can OPT OUT of the deployment if you are not yet prepared for the original February 2023 timeframe. Watch our quick video to help guide you through the process. Also make sure to join the online trailblazer group if you have any questions or you can also reach out to your Sputnik Moment consultant.

update on July 1, 2022: Salesforce is extending that timeframe to Spring ’23 now – your enhanced domain will automatically be enabled in March 2023, but we still advise you plan for this ahead of that deadline.

What does this mean and why should I care?

In Winter ‘22, Salesforce enabled MY DOMAIN for every customer. This meant that your internal Salesforce platform URL was transformed from NA##.salesforce.com to MYFOUNDATION.my.salesforce.com (replace “MYFOUNDATION” with the name of your actual org).

In Winter ‘23, Salesforce will enable ENHANCED DOMAIN for every customer, which adds a bunch of boring infrastructure and security things (with which I won’t bore you the details) AND will automatically change all of your external URL domains to MATCH your internal myDomain. 

Lol, wut?

Yup, you read that right, if you have any external experience cloud or public sites, that url will change to match whatever you use internally. So if you have a grantee or reviewer portal that shows as “foundation.force.com/grantee” and your internal salesforce login shows as “myorg.my.salesforce.com,” your portal will automatically transform into “myorg.my.site.com/grantee.” You can no longer have 2 different URLs.

Good news! Anyone who goes to your current URL automatically gets redirected to the new url.

Bad news: All of your applicants, grantees and reviewers will lose access to the portal UNLESS you take the following actions BEFORE the Winter ‘23 release:

    1. Verify which url you want to keep IF your internal and external domains are different (see example above)
    2. If your domains match already, skip to step 4
    3. If your domains DO NOT match, you’ll first need to change your internal mydomain to match your desired external domain (in the example above, you would change and deploy your myDomain from “myorg” to “foundation” first)
    4. Test in the sandbox: turn on enhanced domain – again, you lose the ability to have a different internal vs. external domain so your portal sites will automatically update to match your internal myDomain once you deploy your new enhanced domain
    5. Mass update every active portal user’s username with the new external domain url
      • if you ARE upgrading to v.11.50: you can utilize the new batch apex tool included with the package
      • if you are NOT upgrading to v.11.50: simply export all active users, find and replace the username from @myorg.force.com to @foundation.my.site.com and reimport the updated usernames [NOTE: use your actual enhanced domain URL, not “@foundation.my.site.com” literally]
    6. Navigate to the new portal site and directly log into the portal as a user, verify everything is working without issue
    7. Test new user registration or new user creation (if you have custom actions to create a new portal user internally), verify everything is working without issue
    8. Replicate the same steps in your production instance

How long will this take to update and by when do I need to complete this?

Be successful! Enable enhanced domain before Salesforce enables it for you so you can plan your communications to your grantees before you open your next cycle (or at least hopefully when you don’t have a significant amount of portal activity). 

Plan for 2 weeks to execute the steps in a sandbox, test and then finally upgrade in production.

If you attended the May fC user group meeting, the latest foundationConnect release (11.50) contains a batch tool that you can utilize to change all of your portal usernames automatically. *NOTE:* As with any fC upgrade, we recommend you always fully test in a sandbox before installing into production.

If you plan on doing an fC upgrade AND enabling enhanced domain, plan for upwards of 12 hours of work.

If you plan on only enabling enhanced domain and not upgrading fC right now, plan for upwards of 8 hours of work.

How to be successful: plan accordingly and utilize your resources

Do not wait until the last minute: plan to enable enhanced domain manually within the next 3 months (before October).

If you have a current support contract with Sputnik Moment, work with your consultant and plan out a time to enable enhanced domains – we can utilize your existing support hours to accomplish this.

If you do NOT have a support contract with Sputnik Moment AND/OR you are a technical maven, here are the release notes from foundationConnect that you can utilize to execute this upgrade on your own: https://powerofus.force.com/s/article/fC-Release-Notes#ariaid-title2

*NOTE* See above under step 5 if you plan on doing this manually, without upgrading your fc package.

If you do NOT have a support contract with Sputnik Moment AND you do not have the bandwidth or desire to execute this update on your own, contact [email protected] and we can send you a quick-project contract to help you make this transition as smooth as possible.

Is there a checklist of everywhere I need to update?

This list is not comprehensive as it can be different for each client, but here’s a list of the most common places to update your URL:

  1. Enabling enhanced domain in Salesforce
  2. Changing all hard-coded url references in any of your website and external grantee publications
  3. Changing any hyperlinked url references in any and all templates (in Salesforce and in any other external communication tools) – this includes email and merge templates
  4. Changing any website bookmarks you have and advising your staff and grantees to do the same
  5. Changing the url references in all documentation – both for internal staff training and applicant resources.


Salesforce Announcement: https://help.salesforce.com/s/articleView?id=000358662&type=1

foundationConnect Release Notes: https://powerofus.force.com/s/article/fC-Release-Notes#ariaid-title2

foundationConnect May 2022 User Group recap: https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000Hju5P (note: you will have to log in with your trailblazer credentials to access this)