- 06 May 2025
- 1 Minute to read
- Print
- DarkLight
Before you begin
- Updated on 06 May 2025
- 1 Minute to read
- Print
- DarkLight
Applies to: All Board Cloud subscriptions
đź’ˇThis article contains version changes.
Spot the light bulb icon? That means you’ll find helpful details about what’s changed across versions. Read more about version changes here.
WHAT: Supported browsers and requirements
The Board Subscription Hub is tested on and supports the following desktop browsers:
Microsoft Windows 10
Google Chrome (latest stable version)
Firefox (latest stable version)
Microsoft Edge (latest stable version; Chromium-based only)
MacOS 10.x and newer
Google Chrome (latest stable version)
Safari (latest stable version)
For best results, we recommend the latest version of Google Chrome.
Please note that the Board Subscription Hub is only supported by Board 10.7, 11.3 and newer.
đź’ˇSession Expiration Management in the Subscription Hub
In versions 14.2.2 and earlier, the SessionExpiration parameter is managed at the instance level.
Session management is incorporated into the Subscription Hub to prevent disruptions due to inactivity when simultaneously active in multiple instances. A logout due to inactivity will only occur if a user is inactive for 1 hour across all instances within the Subscription Hub.
Available from:
BOARD Version 14.3 + (if the Subscription Hub has multiple instances with previous Board versions, this parameter cannot be activated)
Subscription Hub Version 9 +
What changed?
Session management has been centralized through the Subscription Hub. The system monitors the time between HTTP calls across all instances. If the inactivity time exceeds the value set in "Session Expiration In Minutes", the user will be automatically logged out.
Configuration Parameters and Default Values
Starting with BOARD 14.3 and Subscription Hub 9, session expiration and duration settings can be managed in the app settings of the Subscription Hub.
Default Values
This parameter is not active by default. It can be activated opening a ticket with our Cloud Team.
Upgrade to 14.3 / Sub-Hub 9
Upon an upgrade to 14.3, provided that all the instances under the Sub-Hub are 14.3+, this new parameter can be activated and all the configurations at instance level switched off. This can be requested contextually to the upgrade ticket to our Cloud team. For customers not using the Subscription Hub at the instance level, old parameters can still be used.