System Configuration

The PIN that users enter to open the admin mode menu. By default, this PIN is set to 4110. The PIN you configure should contain four numerical digits.

Important: It’s strongly recommended that you replace the default admin PIN value with a unique value.

Controls whether administrators and supervisors can enroll employee badges on the Dayforce Clock Pro. By default, this feature is disabled and the tag is set to no. When the tag is set to yes, administrators and supervisors can enroll employee badges when the "enroll_raw_badge" function is assigned to a button in the <functions id="admin"> or <functions id="supervisor_functions"> sections of the clock’s config file.

The number of digits stored in the badges that employees use on the clock. Enter the number of digits employees use to identify themselves on the clock.

The <badge_length> tag has the following additional attributes:

• prefix and suffix: Use these attributes to add a prefix or suffix to employees’ badge numbers. Prefixes and suffixes are useful in cases where two employees have the same badge number and perform clock entries on different devices. For example, two organizations merge and each organization has an employee with a badge number “123,” who work at different locations and clock in on different devices. By configuring one of the clocks to append a prefix or suffix to employees’ badge numbers, administrators can differentiate between the two employees without having to reissue their employee badges.
• Note: For this functionality to work, you must also update the badge numbers for the employees who clock in on the device so that they include the specified prefix or suffix. You update the employee badge numbers in Dayforce in the People feature in the Work > Badge screen. Continuing the example above, the employee who works at that location and has the badge number “123” would then be assigned a badge number such as “A10123b20.”
• After configuration is complete, when employees clock in on that device using their old badge number (by entering it in or using the scanner), the clock automatically appends the new prefix and suffix to their badge number.

Controls when the Dayforce Clock Pro restarts when the battery falls below a specified level. The default value is 20. For example, if the value is set to 20, the clock restarts when the battery level falls below 20%. If the value is 0, the clock doesn’t restart at all when the battery is low. In this scenario, the battery continues to run until it loses its charge.

The clock restarts only when it’s operating on battery power. It doesn’t restart when it’s plugged in and charging.

Controls whether biometric verification is enabled on the clock. When set to yes, the clock prompts users to scan their finger before their clock entry is accepted.

The following attributes are available for the <biometric> tag:

• mode: The clock can operate in two biometric modes: "identify" and "verify".
• When configured with mode="identify", the clock prompts users to scan their finger without first having to enter their badge number. The clock checks their scan against the ones saved in the database to find the appropriate match.
• When configured with mode="verify", users must first enter their badge number. The clock then prompts the user to scan their finger, and compares that scan with the one saved in the database for that user.
• threshold: Controls the sensitivity for fingerprint quality.
• When the clock is configured with a lower sensitivity, it accepts lower quality fingerprints. This attribute can be configured with values from 1 to 4, corresponding to low, medium, high, and very high sensitivity. For example, set the attribute to threshold="3" to configure the clock for high sensitivity. 
• enrollment: Controls whether the clock prompts users for one or two fingers when enrolling them for biometric verification.
• When configured with enrollment="normal", the clock prompts employees for two finger scans. When configured with enrollment="simple", the clock prompts employees for only one scan.
• lift_finger_in_enroll: Controls whether the clock prompts users to lift their finger from the fingerprint scanner when enrolling them for biometric verification. When configured with lift_finger_in_enroll="yes" (the default setting), the clock requires users to lift their finger between scans when enrolling them for biometric verification. When configured with lift_finger_in_enroll="no", the clock doesn’t prompt users to lift their fingers between scans.
• verify_attempts: Controls the number of biometric verification attempts the clock supports. For example, with verify_attempts="3" specified, the clock allows three attempts. This means that if an employee fails their first attempt at biometric verification, the clock allows them two more attempts without having to re-enter their badge number.
• accept_on_hw_failure: Controls whether clock entries are accepted when biometric verification is enabled, but the biometric reader isn’t connected. When set to yes, the clock continues to accept clock entries, despite not being able to perform biometric verification. When set to no, clock entries are rejected if the reader isn’t connected.

Controls whether the camera is enabled on the Dayforce Clock Pro. When set to yes, the clock prompts users to capture and submit their facial image to verify their identity when performing clock entries.

The Dayforce Clock Pro uses a flat flash when it captures employees’ pictures. A flat flash means that the LED lights up when the camera starts focusing the picture, and then stays lit until the picture has been captured. This type of flash contrasts with a more traditional flash which is lit only at the instant that the picture is captured.

The following attributes are available for the <camera> tag:

• mode: The camera can operate in the following modes on the Dayforce Clock Pro:
• Note: The Dayforce Clock Pro supports all of the following camera modes when running in both standalone and online modes.
• picture: The camera takes a picture of the employee in front of the camera. This camera mode is the least restrictive.
• This camera mode is supported when the clock is operating in directionless mode.
• face_verification: The camera verifies the face against the enrollment photos that are associated with the employee. When operating in this mode, the clock also prompts employees to enter their badge number before the camera captures their image.
• Note: Depending on your Dayforce configuration, this attribute might be unavailable or might not function.
• face_identification: The camera verifies the face against the enrollment photos that are associated with the employee. This mode is identical to face_verification mode but doesn’t prompt employees to enter their badge number on the clock before the camera captures their image.
• This camera mode is supported when the clock is operating in directionless mode. However, the clock doesn’t support both biometric verification and facial identification at the same time. If you’ve configured both of these validation features, the clock prioritizes and uses biometric verification only.
• torch_intensity: Control the intensity of the flash by editing a number that corresponds to the percentage of the LED’s brightness. For example, with torch_intensity="50" specified, the flash would be limited to 50% of the LED’s possible brightness.
• submit_all_pics: With this attribute set to yes, the clock submits all clock pictures, regardless of whether they passed facial verification. When set to no, the clock submits only pictures that failed verification, so that managers can view them using the existing functionality in Timesheets and Clock Entry Audits.

Controls whether employees can perform directionless (fast) clock entries. When directionless clock entries are enabled, validation on the clock is limited. Instead, Dayforce determines the type of clock entry that the employee performed based on their order. For example, Dayforce determines that the employee’s first clock entry is to start their shift and their second clock entry is to clock out for their meal.

The following attribute is available for the <directionless> tag:

• default: Controls how directionless clocking functionality works on the clock. When set to default="keypad", the login screen shows the keypad and a message indicating that clock entries will be submitted automatically after users log in and verify their identity. When set to default="functions", the clock also shows the login screen with the keypad, but the user also has to click the Logical Clocking button to submit their clock entry after they log in.

Controls employee PIN functionality on the clock. When set to yes, the clock prompts employees to enter their PIN when clocking in and out.

Users can configure employee PINs in People in the Work > Badge screen. See Work > Badge in the HR Administration Guide.

Controls whether the clock shows a legal consent agreement before employees enroll for biometric or facial verification (Dayforce Clock Pro only). When the tag is set to yes, employees can’t enroll for biometric or facial verification until they review information about stored templates and agree to submit their fingerprint or facial image for verification purposes.

Important: You can’t edit the legal consent text in the localization override file in Site Setup > Clock Configuration in the Localization tab. If you try to edit this text, Dayforce generates an error and doesn’t save your changes.

The following attribute is available for the <legal_consent> tag:

• record: Controls whether the clock prompts users to review the legal consent text and agree to submit their biometric or facial templates when performing a clock entry (if they haven’t previously agreed to submit their biometric or facial templates). When the user agrees, their confirmation is recorded in the database and they’re no longer prompted to view the legal disclaimer text when they perform clock entries. If they disagree, they must confirm that they don’t consent which results in the deletion of their biometric or facial templates.
• This attribute is set to "no" by default. To enable it, set it to "yes" in the clock’s custom config file.

Controls whether administrators can enroll employees on the Dayforce Clock Pro who haven’t been onboarded yet in Dayforce. This functionality is useful in cases where organizations need to rapidly onboard a large number of new employees, and need them to perform clock entries before their employee records have been created in Dayforce.

Use the inactive_expire_days attribute to configure how many days an employee can be inactive (that is, not record any clock entries on the device) before their employee record expires. For example, with inactive_expire_days="7" specified, the clock automatically deletes the employee’s local clock entries if they don’t perform any new clock entries in seven days.

See Local Employee Enrollment (Dayforce Clock Pro Only).

Controls whether the clock operates in standalone or online mode.

When this tag is set to yes, the clock operates in standalone mode. In standalone mode, the clock performs its own validations (that is, the ones that are available in the <validations> section. See Validation Configuration.

When this tag is set to no, the clock operates in online mode. In online mode, the clock accepts clock entries and transmits them to Dayforce. The application then performs the validations configured in System Admin > Clocking Sequence Validation. See Configure Clock Entry Validations in the Dayforce Implementation Guide.

The screen brightness for the Dayforce Clock Pro.

The following attributes are available for the <screen_brightness> tag:

• low: Sets the screen brightness when the clock hasn’t been in use for a while. The number is a percentage of possible brightness. This means that with low="30" specified, the clock would dim its screen to 30% brightness after it hasn’t been in use for a while.
• high: Sets the screen brightness when the clock is in use. The number is a percentage of possible brightness. This means that with high="100" specified, the clock shows its screen at full brightness when it’s in use.
• on_battery_low: Sets the screen brightness when the clock hasn’t been in use for a while and is operating on battery power. The number is a percentage of possible brightness. This means that with on_battery_low="20" specified, the clock dims its screen to 20% brightness after it hasn’t been in use for a while and is on battery power.
• on_battery_high: Sets the screen brightness when the clock is in use and on battery power. The number is a percentage of possible brightness. This means that with on_battery_high="80" specified, the clock shows its screen at 80% brightness when it’s in use and on battery power.
• timeout: Sets the timeout (in seconds) after which the clock dims from high brightness to low brightness. For example, with timeout="10" specified, the clock dims from high to low brightness after 10 seconds of inactivity.

Controls supervisor PIN functionality on the clock. When set to yes, the clock prompts supervisors to enter their PIN when clocking in and out.

Users can configure supervisor PINs in People in the Work > Badge screen. See Work > Badge in the HR Administration Guide.

The clock’s user interface. Set to either default or everest:

• default: The legacy user interface.
• everest: The new reimagined user interface.