Project Time Tracking

Project time tracking lets you split the working time your team already records across projects, customers and activities — without changing how people clock in. It is the same working time, only segmented, so daily and weekly totals stay identical; each segment simply carries a project and an optional activity (travel / on-site / general). It is off by default and gated by two permission layers plus a per-user permission for personal projects.

Enabling it — company & departments

Two switches must agree before a user sees project time tracking:

• Company (master switch). A super-admin enables Project time tracking per company under Admin → Companies. With it off, no project UI, routes or clock controls exist.
• Department (opt-in). With the company switch on, each department is then enabled individually under Admin → Departments (Project time for this department). It is opt-in: a new department is off until enabled. A user assigned to a department needs that department enabled; users without a department follow the company switch.

Once a user qualifies, a Projects entry appears and the clock widget gains project controls. Upgrades keep working: a one-time migration enables the existing departments of any company that already had projects on.

Personal projects permission

Besides company-wide projects, users can keep their own personal projects. Whether they may create them is controlled by a company-wide default (Admin → Companies → Allow personal projects by default) that can be overridden per user (Admin → Users: company default / allow / deny). When disallowed, the “new personal project” form is hidden and creation is rejected; existing personal projects stay usable.

Projects & visibility

Admins manage projects under Admin → Projects (/admin/projects). Each project has a name, optional number and customer, a department, an active flag, and a visibility of Company (everyone may book it) or Personal. Archived projects stay on historical entries but can no longer be booked. Users manage their own personal projects under Projects (/projects).

Booking, reclassifying & reporting

From the clock widget (or the Projects page while clocked in) an employee can start a project, switch to another (closing the running segment and opening the next), or stop project work while staying clocked in. The result is a chain of segments that exactly tiles the working day; time that was clocked but never assigned shows up under Unassigned project times for later classification.

Because a project segment is metadata on already-approved working time, reclassifying a segment to a different project does not trigger a new approval — the hours were already counted. Admins get a per-project report (/admin/projects/report, CSV export) totalling time by project, customer and period. The public extension API exposes the same segmented entries via read:time_entries, and Klokk Anchor binds each segment into its daily proof, so the project breakdown is covered by tamper-evident anchoring too.