Mintage Workforce ·

Workforce and TimeKeeper start sharing

Workforce began serving employee profiles, photos and payroll self-service to TimeKeeper, and Connect learned to take sections from whichever product owns them.

1 min read29 commits that monthIntegrationTimeKeeper

One employee, several products

August's main theme was making Workforce work with TimeKeeper. An organisation can run more than one Mintage product, and each employee should look the same in all of them. Workforce now serves its employee profiles to Connect, and offers TimeKeeper a dedicated profile endpoint, profile photo sync and version information so TimeKeeper can tell when something has changed. It also passes through the TimeKeeper fields and the source of each punch on its attendance API.

Late in the month Workforce began relaying payroll self-service, such as payslips, to TimeKeeper. And when an organisation connects TimeKeeper, TimeKeeper now decides which sections of Connect it is responsible for, so employees do not see the same thing twice.

Support and clock-ins

Workforce was connected to our shared support ticket tracker, so a support request raised from inside Workforce arrives with the right identity attached, and support can look up Workforce users. Connect's account details were also updated so one login can carry several Mintage products.

Two small changes improved clock-ins. Punches made just outside a work location are now classified as near the boundary, which helps HR review them, without weakening the rule itself. And self-service punches are allowed when a face-presence check is used as a fallback.

Housekeeping

The rest of the month's 29 commits were maintenance: Workforce's data snapshots are now encrypted at rest, and dependencies were patched as advisories came out.

This article was written from Mintage Workforce’s commit history for August 2026. See Mintage Workforce today