Add the URL of the web page where you intend to add the snap-ins chat to the CORS whitelist in your org. The web page where you add the snap-ins chat is the page that customers use to access chat.
|Available in: Enterprise, Professional, Unlimited, and Developer Editions|
|To create, read, update, and delete:||“Modify All Data”|
Only HTTPS domains are permitted for embedded chat per the CORS whitelist limitations.
From Setup, enter CORS in the Quick Find box, then select CORS.
Enter an origin URL pattern.
The origin URL pattern must include the HTTPS protocol (unless you’re using your localhost) and a domain name and can include a port. The wildcard character (*) is supported and must be in front of a second-level domain name. For example, https://*.example.com adds all subdomains of example.com to the whitelist.
The origin URL pattern can be an IP address. However, an IP address and a domain that resolve to the same address are not the same origin, and you must add them to the CORS whitelist as separate entries.