Manage how users and API calls access your Salesforce org. Specify whether logins to your org require your My Domain. And choose what users see when they access a bookmark or link that contains your instance-specific domain.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
| User Permissions Needed | |
|---|---|
| To edit My Domain settings: | Customize Application |
Note This setting applies to your org’s deployed and provisioned domains.
To learn how to handle requests to your instanced URL, such as https://eu55.salesforce.com, and requests to your previous My Domain URLs, see Manage My Domain Redirections.
- From Setup, use the Quick Find box to find and select My Domain.
- In the Routing and Policies section, click Edit.
-
To require that users log in with your My Domain in production, select
Prevent login from https://login.salesforce.com and
https://welcome.salesforce.com. Or, in a sandbox, select Prevent
login from https://test.salesforce.com.
If you enable this setting, users also can’t use your instanced URL, such as https://usa77.salesforce.com, to log in. Also, if you enable Prevent login from https://test.salesforce.com in a sandbox, admins can’t log in to that sandbox via the Log In action on the Sandboxes Setup page.
-
To require that SOAP API logins use your My Domain login URL, in production, select
Prevent SOAP API login from https://login.salesforce.com. Or, in
a sandbox, select Prevent login from
https://test.salesforce.com.
If you enable this setting, SOAP API logins also can’t use your instanced URL, such as https://usa77.salesforce.com, to log in.
API traffic that uses an incorrect instanced URL is blocked on a rolling basis shortly after your org gets the Summer ’26 release, regardless of this setting. See Prepare for the End of Redirections for Non-Enhanced Domains.
- Save your changes.