Local Employee Enrollment (Dayforce Clock Pro Only)

On the Dayforce Clock Pro, you can grant employees access to the clock even if they haven’t been onboarded in Dayforce. This functionality is useful when:

• Organizations need to rapidly onboard many new employees.
• The employees need to perform clock entries on the clock before their employee records are created in Dayforce.

Enrolling local employees involves creating a badge number. If you create a badge number that’s shorter than the length specified in the clock’s config file, the clock automatically adds zeros to the beginning of the badge number to reach the required length. For example, if the config file specified a badge length of six, but you entered 11, Dayforce would record the badge number as 000011.

Enroll Local Employees

To enroll local employees:

1. Go to the Administrator Mode screen.
2. Tap Local Employee Enrollment.
3. When prompted, enter a badge number for the employee.
4. If biometric enrollment or picture capture are enabled, the clock prompts the employee to complete the necessary enrollment steps. See Enroll Employees for Biometric Verification and Enroll Employees for Picture Capture.
5. The clock shows an authorization message to indicate if the employee was successfully enrolled
4. Do one of the following:
   • Enroll another employee.
   • Log out.
   • Click Back to my clock to return to the admin menu.

Post-Enrollment Support

After enrollment, the employee can record their worked time on the clock. The clock stores the employee’s clock entries locally, until one of the following conditions is met.

Scenarios in which the clock stops storing clock entries for employees that were onboarded locally

Scenario	Description
The employee is onboarded in Dayforce	After the employee is onboarded in Dayforce, you need to update the new employee’s badge number in People in the Work > Badge screen to the one specified during local enrollment. Continuing the example above, you would set the badge number to 000011. Next, you must update the clock’s database so that the clock associates the local clock entries with the new employee record in Dayforce. Finally, you must manually submit clock entries, templates, or clock pictures (depending on which features are enabled) from the clock to Dayforce. After you submit this data, Dayforce shows the employee’s clock entries in time and attendance features. For more information about updating the clock’s database and submitting clock entries, templates, and clock pictures, see Clock Server Synchronization.
The local employee record expires	In the <system> section of the clock’s config file, the <local_employee> tag contains the inactive_expire_days attribute. Administrators can use this attribute to configure the number of days that an employee can be inactive (that is, not perform any clock entries on the clock) before their local employee record expires. After this number of days passes without a clock entry, the clock automatically deletes all of the employee’s local clock entries. For example, with inactive_expire_days="7" specified, the clock automatically deletes the employee’s local clock entries when they don’t record any new clock entries in seven days. See System Configuration.