Restrict Page Resource Requests with Cross-Origin Embedder Policy (COEP)
To safeguard your custom Visualforce pages, only allow content from external sources
that trust your page. When you enable the Cross-Origin Embedder Policy (COEP) setting, externally
sourced embedded content loads only when the origin explicitly states that your page or domain can
load its content. Embedded content can include images, documents, and widgets.
Required Editions
Available in: both Salesforce Classic and
Lightning Experience
Available in: Contact Manager, Group, Professional,
Enterprise, Performance, Unlimited, and Developer
Editions
User Permissions Needed
To modify session security settings:
Customize Application
When COEP is enabled, externally sourced embedded content loads only when the external origin
allows it via one of these methods.
Note To preserve your users’ access to required content, we recommend that you review the
expected behavior and test COEP in a sandbox before you enable this feature in production.
Browser access checks use the headers for both your Visualforce page and the external sites
that you access from your page. The combination of Cross-Origin Embedder Policy (COEP) and
Cross-Origin Opener Policy (COOP) headers determines whether the Visualforce page and external
sites can interact. To learn more about COOP and COEP, we recommend these topics on MDN Web
Docs: Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy.
Cross Origin Resource Policy (CORP). The externally sourced content includes the
Cross-Origin-Resource-Policy header with the cross-origin value.
Cross-Origin Resource Sharing (CORS). The external origin includes your page or its domain
in its CORS allowlist. When your page makes a request, the external origin responds with the
required Access-Control-Allow-* headers that allow your page access to the content.
From Setup, in the Quick Find box, enter Session Settings, and then
click Session Settings.
In the Visualforce Cross-Origin Security Headers section, select Cross-Origin
Embedder Policy (COEP).
Note COEP applies to all your custom Visualforce pages.
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.