Help your users access external and cross-org URLs via redirections. Add your trusted
URLs to the Trusted URLs for Redirects allowlist. Redirections from Salesforce to URLs in that
allowlist are always allowed without a warning.
To determine the URLs to trust, consider the sites that your users access to perform their
daily work. For example, your company website, trusted partners, and tools hosted on the
internet. Also identify cross-org URLs to allow.
To identify blocked redirections from components and pages that were built in Salesforce
Classic, use the Trusted URL and Browser Policy Violations list in Setup. See Manage Trusted URL and Browser Policy Violations.
To get details about blocked redirections, use the Blocked Redirect event type object. The
blocked redirect event is free for all customers with a 24-hour data retention period. The
event is available in the API but not in the Event Monitoring Analytics app. To collect details
for blocked redirections over multiple days, schedule a daily query of the Blocked Redirect
event type via REST API.See Blocked Redirect Event Type in Object Reference
for the Salesforce Platform.
Warning To protect your users, we strongly discourage adding top-level Salesforce
domains, such as *.salesforce.com, *.force.com or
*.file.force.com, to the Trusted URLs for Redirects allowlist.
Update the Trusted URLs for Redirects Allowlist
Redirections from Salesforce to URLs in this allowlist are always allowed without a
warning.
In Setup, find and select Trusted URLs for Redirects.
Click New URL.
Enter the URL, and save your changes.
These formats are accepted: example.com,
*.example.com, and https://example.com.
The host
section of the URL can include an asterisk (*) as a wildcard. Otherwise, the
URL cannot be malformed. Examples of malformed URLs that fail a syntax check are
malformed^url.example.com, and
https://{subdomain}.example.com.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.