Local authentication

Local authentication can be set up so that the user has to verify their identity before performing a punch The entries on a timecard that mark the beginning (in-punch) or end (out-punch) of a work interval, such as the beginning of a shift or transfer. transaction. After tapping the Punch button, the user is prompted to authenticate (passcode, fingerprint , etc.) before being allowed to punch from the mobile app

Important notes about local authentication

  • Local authentication is achieved with the same method used in the device for screen unlocking, such as a passcode or a biometric identifier (fingerprint or facial recognition).
  • Device screen locking must be turned on for local authentication to work. If local authentication is enabled and the screen locking is turned off, an error will occur and the user will not be allowed to proceed with the task (logging in or punching). Screen locking is located in Settings on the device:
  • Some Mobile devices will lock out after multiple failed biometric authentication attempts. Follow your device instructions to enable biometric authentication.

How to set up Local authentication

Local Authentication for Punch is set up with the following two Function Access Control Points (FACPs):

  • Require biometric authentication for mobile app punch

  • Require any local authentication (biometrics, pin, passcode) for mobile app punch

To set up “Local Authentication for Punch” for users:

1. Set the two new FACPs as follows

  • FACP settings for No local authentication:

    • Require biometric authentication for mobile app punch = Disallowed

    • Require any local authentication (biometrics, pin, passcode) for mobile app punch = Disallowed

  • FACP settings for Biometric local authentication only:

    • Require biometric authentication for mobile app punch = Allowed

    • Require any local authentication (biometrics, pin, passcode) for mobile app punch = Either setting (No effect dur to above setting)

  • FACP settings for Local authentication using any method:

    • Require biometric authentication for mobile app punch = Disallowed

    • Require any local authentication (biometrics, pin, passcode) for mobile app punch = Allowed

2. Include the two new FACPs in the applicable Function Access Profile(s).

3. Apply the Function Access Profiles to all affected users.