Skip to main content
The Time Clock uses seven capabilities. This page shows what each one unlocks and which roles hold it.

​
The capabilities

Reading and editing a timecard also depends on schedule.view, because expected hours come from a schedule.

​
Which roles hold what

Finance clocks in. Unlike time tracking, which Finance has no part in, the Time Clock is a working-role feature. Finance clocks in, reads its own timecard and submits it – but never reviews anyone else’s.
Client contacts never clock. A portal contact holds no internal capabilities and is skipped by the absence job entirely.

​
Self versus others

Almost every timecard rule follows the same shape:
  • Your own timecard is governed by timecard.clock and timecard.view.
  • Someone else’s is governed by timecard.manage or timecard.approve.
So a Member can correct their own shift times but cannot open a colleague’s timecard at all.

​
Capability is not scope

timecard.manage says you may work on other people’s timecards. Your supervision scope says whose. A Project Manager whose scope covers one group will only find that group’s people in the member picker – even though the capability is workspace-wide on paper. Both checks run on every read and every write. See Supervision scope.

​
Self-approval is allowed

A manager may approve their own timecard. There is no rule forcing a second pair of eyes on your own period.

​
Two gates that are not permissions

​
The app gate

The Time Clock app must be on in Settings → Apps.
  • It is off by default. A workspace opts in.
  • It requires Work schedules. You cannot switch it on without them.
  • Switching it off hides the clock and the timecards, keeps every recorded session, and stops missing clock-out reminders.

​
The plan gate

This is the general rule across TimeTracker: capture is free, resolution is paid. A Free workspace records everything and accumulates submissions it cannot clear. The day it upgrades, the backlog can be cleared – nothing is lost. See Plans and features.

​
The per-person override

Clocking can be switched off for one person on their member record, under Employment → Time & attendance. It is deny-only. It narrows what their role grants and can never widen it. If the role does not grant clocking, or the app is off, the switch is disabled. Changing it needs member.changeRole – Owner and Admin only. See Turn clock access off for one person.

​
Location rules

A location rule can hold clocking back while someone is off-site. That is a state, not a permission – the capability is still there, the person is in the wrong place right now. They see an explanation, and nothing already recorded is affected. See Location rules overview.

​
Example

At Northwind Studio, with the Time Clock switched on: Approving is Pro, so Priya’s Approve button only works while Northwind is on a paid plan.

​
Common questions

No. That needs timecard.manage or timecard.approve, which Members do not hold.
Yes. Build a custom role containing timecard.approve and the clock capabilities, and assign it. See Custom roles.
Reversing a sign-off is an owner and admin action, the same tier as closing a period. It also requires a written reason.
No. They are separate capability families. Someone can clock in without being able to track time, and the other way round.
The Time Clock app is off, or you do not hold timecard.view. If you are looking at someone else, you also need timecard.manage or timecard.approve.

Roles and capabilities

The full permission model.

Turn clock access off for one person

The deny-only override.

Apps and modules

Why the Time Clock may be hidden.

Approve a timecard

Using timecard.approve in practice.