All Collections
Form, Portal & View Editor settings
Error: Failed to read the 'localStorage' property from 'Window": Access is denied for this document.
Error: Failed to read the 'localStorage' property from 'Window": Access is denied for this document.
Updated over a week ago

This is a browser limitation related to iFrames in private windows. The login function cannot work when ALL these 3 factors are true:

  1. The portal is embedded.

  2. Using incognito mode.

  3. In a Chromium-based browser.

localStorage is disabled in private or incognito mode in many browsers, including Chrome. When you use a regular browser window, information can be stored in localStorage or sessionStorage. However, in private or incognito mode, the browser does not want to keep any data that could be used to track the user's actions. This is why localStorage is usually unavailable in these modes.

Understanding Local Storage Limitations in Private or Incognito Mode

When using our portal software in a regular browsing window, your experience should be seamless. However, if you're using private or incognito mode, you may encounter an error message relating to 'localStorage'. It's not a bug with our software – let's delve into why this happens and how to avoid it.

What's Going On?

Web browsers have a feature called 'localStorage', which is a convenient way for websites to store small pieces of data in your browser for quick access. It enhances your user experience by allowing the software to remember certain settings or actions.

However, when you're using private or incognito mode, your browser prioritizes your privacy. It aims to leave no trace of your browsing activity, and as part of that, it disables 'localStorage'.

While this is a good feature for privacy, it unfortunately means that some web applications, including ours, may not function as expected.

How to Navigate This Issue

If you encounter an error related to 'localStorage' while using our portal software, there's a simple solution. Exit private or incognito mode and continue your session in a regular browsing window. Or don't embed the portal and access the portal directly instead. It will then work as intended. This isn't exclusive to our software; it's a broader, industry-wide limitation.

Did this answer your question?