You are here:
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.
| Available in: all editions |
| User Permissions Needed | |
|---|---|
| To set up trusted URLs for redirects: | Customize Application AND Modify All Data |
To understand where and when this allowlist is used, see External Redirection Restrictions in Salesforce.
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. See Identify Cross-Org Urls to Allow for Redirections.
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.
Redirections from Salesforce to URLs in this allowlist are always allowed without a warning.
example.com,
*.example.com, and https://example.com. For detailed
formatting rules, including how to use wildcards or add Chrome extensions, see Manage Trusted URL and Browser Policy Violations.
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 are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security 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 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.