Page tree
Skip to end of metadata
Go to start of metadata


Availability of this feature:

  • Linchpin Mobile 2.17.0 or above
  • Linchpin Intranet Suite 1.2.0 or above

(Haken) Available for the Linchpin Mobile app
(Haken) Available for branded custom apps



Feature description

The PIN security feature for authenticating system access via the Linchpin mobile app introduces an additional prompt before any system content can be accessed via the app.

  • The PIN security feature requires users to set up a 4-digit PIN code to access the Linchpin Mobile app.
  • As part of the PIN code setup, the selected 4-digit code must be confirmed by the user before it is enabled.
  • Users can optionally enable facial or fingerprint recognition to authenticate themselves.

The PIN security feature is triggered by the following user actions in the mobile app:

  • When setting up a new login to a system that has the extended security feature enabled.
  • When logging in to a connected system with the extended security feature enabled.
  • When opening the Linchpin mobile app after it has been running in the background (e.g. after switching apps), if the current active login is to a system with the extended security feature enabled.

Current limitations of the PIN security feature:

  • You can only set a numeric PIN code of four digits.
  • There is no technical check for "weak" digit combinations (e.g. "0000" or "1234").
  • A 4-digit PIN code set for a system is valid for the entire app from that time onwards.
  • You cannot assign different PIN codes for multiple systems or logins.
  • Once a PIN code has been set, it cannot be changed or deleted.
  • The PIN security feature is available for the Linchpin mobile app as well as for customized mobile apps created for our clients.

What happens after enabling the system's extended security feature in the Confluence administration area?

If a user wants to add a new login to this system in the mobile app, the PIN security feature must be set up on this device.

  • If the PIN security feature has already been configured, the user must enter their PIN code or use face/fingerprint recognition to add the new login.
  • If the PIN security feature has not yet been configured, the user must set it up before they can add the new login.

If the user has an existing login to this system in their mobile app, the PIN security feature is activated for this login when the extended security feature is enabled in the administration area:

  • There may be a short delay before the PIN security feature is enabled on the mobile device.
  • The user will then need to enter their PIN code in the mobile app for any user actions in this system as described above.

In the mobile app, securely protected systems or logins can be identified in the system overview by the small "lock" icon displayed behind the protected system's name.

What happens if the system's extended security feature is disabled in the Confluence administration area?

After disabling the extended security feature of a Confluence instance in the Linchpin Mobile configuration, there may be a short delay before users are no longer required to enter their PIN codes for any user actions in this system as described above.





Screenshots