Timesheets
Overview
A timesheet is a week of time entries submitted for approval. That gives time tracking a closing point: until submission, time is a draft; after it, it passes through a release.
The weekly matrix is the actual working surface — work items in the rows, days in the columns, daily totals below. In that form gaps stand out: a day without a booking is visible, a missing line in a list is not.
Core tasks
Review and submit the week. Navigate with Previous week, Next week and Today; Submit week sends it for approval.
Book quickly. Quick booking enters minutes directly into a cell of the matrix — the fastest way to add a forgotten half hour without opening the capture dialogue.
Approve, reject, reopen. Approvers decide per timesheet. Reopen takes a decision back when something turns out to be wrong.
Rejected entries stay visible. If you reject a single entry (cell dialogue, Reject entry) or the whole week, the time still counts in the week — the weekly total remains the full working time. Rejected entries are clearly marked, though: the list shows the share ("of which 2 h rejected"), the matrix marks the day and shows the share below the weekly total, and the entry itself carries Rejected with the reason. When the employee submits the week again, the mark disappears.
Survey what exists. The list shows period, number of entries, hours, status, approver and time of decision, plus a total and a count.
Fields in detail
The What it does column answers what changes in the system — not what the field is called. The grey name behind the label is the API field: the same thing runs under that name through automation, import and AI tools.
A timesheet is not filled in — it comes out of the time entries of a week. What is edited is therefore only its approval.
| Field | Required | Values / format | What it does |
|---|---|---|---|
Employee employeeId | yes | an employee | Whose week. |
Week weekDate | yes | a date within the wanted week | Which week is meant. Any day will do; the system takes the week it falls in. |
Action action | yes | approve, reject, reopen | What happens to the week. Approve closes it: the entries can no longer be changed and become available for billing. Reject sends it back with a note. Reopen undoes an approval — the only way back, and deliberately not the recorder's to take. |
Note note | on rejection | text | Why it was rejected. It goes to the employee and stays on the week. |
Settings & permissions
- Module
module.timetracking. time.timesheet.submitto submit,time.timesheet.approveto approve and reject —
separate permissions, because one concerns your own work and the other other people's.
- Approved time is no longer freely editable. Corrections run through reversal, see
- The weekly matrix shows what is booked — it does not capture time itself, except through quick
booking.
FAQ & troubleshooting
The matrix is empty although I worked. Then no time entries exist for that week. Book them through Time tracking or the timer.
I cannot submit a week. Check the time.timesheet.submit permission — and whether the week has already been submitted.
After approval a time entry can no longer be corrected. By design. Reopen by the approving person, or correct through a reversal.
I cannot see other people's timesheets. That requires the approval permission, or the project-level view of time.