Supported browsers

The system opens in a browser and installs nothing on the workstation: no plugin, no extension, no component that needs installation rights.

What is required

Requirement	Why, and what happens without it
JavaScript enabled	The interface is a client application. Without it no screen loads
Local browser storage	Holds per-machine preferences. Blocked ⇒ the system works, the choices simply do not survive a reload
Canvas	The graphs are drawn in it. Every graph also has a table equivalent, so the content is available without it
Extensions	None. Nothing is installed on the workstation

No outbound internet access is required from the browser: fonts, libraries and icons are bundled into the build and served from the server inside your network.

The floor

The application does not pin a browser target list, so there is no single version number that is true for every deployment. What is true:

Supported	Any current, still-updated version of a Chromium browser, Firefox or Safari
Not supported	Internet Explorer, and pre-Chromium Edge
Agreed per deployment	The exact floor, with the team that manages the browser fleet

The floor for a particular installation is a decision made with that organisation's fleet in mind, not a number this page can state on its behalf.

Why the floor is low, on purpose

A system installed on a disconnected network meets managed browser fleets that update at the organisation's pace rather than the vendor's. So very new styling features are not used here even where they would be convenient, and in the few places a newer feature is used, its absence costs a visual detail — a divider that stays visible — and never an action, a value or a state indicator.

What is stored in the browser rather than in the account

Language, theme, table density and rows per page are stored per machine, and separately per user on a shared machine. A user signing in from another workstation gets the defaults for those four; everything else — permissions, saved views, dashboards — follows the account.

A narrow screen

Tables do not scroll sideways. When the width is not enough, the lowest-priority columns move behind a per-row control — "Show N more fields" — instead of every column being crushed together. The identity column always stays. A narrow screen therefore costs information density, not rows and not actions.

This documentation site

The documentation site itself has a higher floor than the system does — Chrome 111 · Safari 16.4 and above. A locked-down workstation running an older browser may render the system correctly and this site less so; that is not evidence about the state of the system.