Skip to main content

Using kiosk mode

Kiosk mode offers the option to have users signed out automatically due to inactivity

Updated today

Kiosk mode adds an extra level of security for shared devices. When enabled, after 5 minutes of inactivity on Blink, the logged-in user will be automatically logged out.

This feature is available with all Blink subscriptions.

In this article:

Enable kiosk mode

Please get in touch with your account manager or Blink support to enable kiosk mode for your organization and grant management access.

Once an administrator has been given kiosk mode access, they then need to use their usual Blink account to set it up on each device.

  1. Log into the device using the usual Blink account

  2. Open Settings (on the web or desktop version, click on the preferences tab)

  3. At the bottom of this page, you'll see a toggle to enable kiosk mode

  4. Toggle this on: the toggle will be to the right and blue when enabled.

  5. You will see a prompt confirming that you wish to enable kiosk mode on this device. Once you confirm this, you will be logged out.

Using kiosk mode

When you are logged into a device where kiosk mode is enabled, your view will differ depending on the device:

  • 📲 On mobile: A logout button replaces the setting button. To get to settings, click on the cog or gear icon in the top right-hand corner of Feed.

  • 🖥️ On web/desktop: a logout button is added below the admin button in the navigation bar.

After 5 mins of inactivity, a message is displayed on the device confirming that they will be logged out if no activity takes place. This message includes a 20-second countdown. The user is given the option to Stay logged in (which resets the 5 mins timer) or log out immediately.

Risk Considerations

Before enabling kiosk mode on any device, there are some risk factors that need to be considered, specifically around authentication sessions as a whole. A typical authentication session in Blink will remember who a user is and whether they have logged in (this is typically stored as a session or persistent cookie). This persistence depends on a few things:

  • The app itself - can range from a few hours to indefinite

  • Type of browser used - i.e. mobile/web browser tab, WebView, iFrame, etc.

  • Browser and device settings

This is relevant to kiosk mode when we consider the following hypothetical illustrated below. If user John logs into Blink via a web browser, then accesses another system (like Workday) via Blink while logged in, then logs off, there is a possibility that the Workday session will continue into a new user like Bob logging in which could cause John's information to be visible to Bob.

If target shared devices do not clear sessions at the Device or Operating System level between users, Blink does not recommend using Kiosk Mode.

FAQs

What counts as activity?

  • On android: Track based on the Activity#onUserInteraction callback. (Whenever a key, touch or trackball event is dispatched to the Activity)

  • On iOS: When a UIEvent is recieved via sendEvent(_ event: UIEvent). Essentially a touch event on the screen.

  • On web: Track based on the SET_IS_FOCUSED event (ie, when it’s false, start the timer)

Why the 20-second countdown?

The timer is included to warn the users that they will be logged out and to give them time to stop it from happening. 20 seconds is the minimum time we can offer to comply with accessibility laws.

Did this answer your question?