Local Employee Enrollment

Local employee enrollment allows you to enroll employees on the Dayforce Touch Clock who haven’t been onboarded yet in the main application. This is useful in cases where organizations need to rapidly onboard a large number of new employees, and need them to perform clock entries on the clock before their employee records have been created in the main application.

Enroll Local Employees

To enroll local employees:

1. Go to the Administrator Mode screen.
2. Tap Local Employee Enrollment.
3. When prompted, record a badge number for the employee.
4. If you record a badge number that is 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 typed 11, the application would record the badge number as 000011.
4. If biometric enrollment or picture capture are enabled, the clock then prompts the employee to complete the necessary enrollment steps. For example, if biometric verification is enabled, but picture capture isn’t, the clock only prompts the employee to scan their finger, but doesn’t capture a picture template.

After you have completed the necessary enrollment steps, the local employee can perform clock entries on the clock. Their clock entries are stored locally until either:

• The employee is onboarded: After the employee has been onboarded in the main application, 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 the main application, and then submit the clock entries, templates, or clock pictures (depending on which features are enabled) from the clock. After those have been submitted, the application shows the employee’s clock entries in the main application.
• For more information about updating the clock’s database and submitting clock entries, templates, and clock pictures, see Server Synchronization.
• The local employee record expires: The <local_employee> tag contains an inactive_expire_days attribute that administrators use to control how many days an employee can be inactive (that is, not perform any clock entries on the clock) before their local employee record expires. When that number of days elapses, the clock automatically deletes all of the employee’s local clock entries.
• For example, with inactive_expire_days="7" specified, the clock would automatically delete the employee’s local clock entries if they hadn’t recorded any new clock entries in seven days.