Common Browser Issues While Using Logik.io<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #7057C7; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } If attempting to configure in Logik.io results in an error (configurator not loading, a 403 error is returned, etc.) and using another browser seems to resolve the issue, then there must be an issue with the settings of the original internet browser that the end user is configuring with. Logik.io utilizes “Authentication cookies” to track active sessions across browser tabs. These cookies do not track the user and are deleted when the user closes their web browser. Their only purpose is to validate the user and their organization for the use of our software. If cookies are not enabled in the browser, Logik.io cannot configure products. The browser itself or the extensions used by the end user in this browser could be inhibiting this active cookie. Here are some examples of known causes for when this issue arises: Inherent Browser Cookie-Blocking Safari and Firefox have a default setting to block all cross-site cookies. This default behavior interferes with our authentication cookie that jumps across Logik and Salesforce. If either of these browsers is your (or your end user’s) default browser, it is necessary to allow cookies to use the configurator. If you have no control over what browsers you expect end users to be using to access the Logik Configurator, and you use easyXDM, then you should submit a support case requesting a “runtimeAPI” parameter. Once the runtime clients are updated to include this parameter, the browsers should work with their default settings. Browser Specific Cookie-Blocking Location Chrome Settings > Privacy and Security > Third-party cookies: Firefox Settings > Privacy & Security Safari Settings > Privacy > Website tracking: Prevent cross-site tracking Edge Settings > Cookies and site permissions > Manage and delete cookies and site data: Common Cookie-Blocking Extensions Here are some third-party cookie-blocking browser extensions that are in common use to look out for: uBlock Origin Privacy Badger Ghostery Disconnect Cookie AutoDelete Some other extensions such as email templates or crypto wallets also cause issues with inadvertently blocking cross-site third- party cookies. Known extensions are: Briskine BNB Chain Wallet MetaMask WalkMe Please check if any other extensions could be interfering while using Logik.io by checking the plugins at the top-right corner of your browser. If you disable all of your browser extensions and the end user can configure, then it must be an issue with one of the extensions. If you discover an extension is the cause of your issue and is not in the list above, please let us know!