Timesheet

The Timesheet tab configures how time is reported: until when an entry stays editable, whether it goes through validation, and which kinds of time (actuals and absences) users can pick.

Settings → Workspace → Timesheet

The entry unit is not on this tab

The man-days / % / hours choice and the "1 MD = n hours" conversion are set on the Calendar tab, because they depend on the selected calendar.

Timesheets closure date

The Timesheets closure date picker sets the date up to which entries are locked. Beyond that date, timesheets become editable again.

This is the period-freeze mechanism: once payroll or invoicing for a month is out, set the closure date to the end of that month to freeze history.

Validation of timesheets

The Validation of timesheets checkbox turns the workspace validation circuit on or off.

State	Effect
Unchecked	The resource's entry is taken into account directly
Checked	Entries go through the Pending then Approved statuses — an approver must validate them

This is a workspace-wide setting: there are no separate circuits per manager, per project, or at two levels. See Timesheet for the approver's side.

Actual types

This list defines the kinds of worked time offered at entry. Each row is a Key / Value pair:

• the Key is the technical identifier, stable, used by exports, the API and the datamart;
• the Value is the label shown to the user.

Shipped defaults:

Key	Default label
0	Standard
1	Not standard
2	Not Billable

What you can do:

• Add a type with the Add button;
• Edit key and label with the pencil icon, then confirm or cancel the row;
• Delete a type with the cross.

The 0 key row is protected

The 0 row ("Standard") can neither have its key renamed nor be deleted: it is the default type applied to any entry that does not specify one.

Vacancy types

This list defines the kinds of absence and special presence offered in the Leave screen and in the timesheet.

Unlike actual types, the list is fixed: ten entries, keys 0 to 9. You can neither add nor delete any — you rename the ones you need and hide the others.

Key	Default label	Capacity impact
0	Vacation	✅
1	Training	✅
2	Illness	✅
3	Bank Holiday	✅
4	Other	✅
5	--- To be defined 1 ---	✅
6	--- To be defined 2 ---	✅
7	Penalty (on-call)	❌
8	Telework	❌
9	--- To be defined 3 ---	❌

The "Impact the capacity" column

It is computed, not editable, and derives from the key:

• keys 0 to 6 — the reported time is an absence: it is subtracted from the capacity of the resource in the Workload plan;
• keys 7 to 9 — it is a special presence (on-call, telework): the resource stays available, capacity is not reduced.

This drives which row to rename: a new absence reason goes on keys 5 or 6, a new presence reason on key 9.

The "Visible" column

The Visible checkbox determines whether the type is offered at entry. Unchecking a type removes it from the dropdowns without erasing the declarations already recorded with it.

That is how you neutralise the "--- To be defined ---" entries you do not use.

Renaming a type

1. Click the pencil icon on the row.
2. Edit the Value column — the Key stays greyed out, it is never editable.
3. Confirm the row, then Save the workspace.

Translating the labels

Both tables are multilingual. The language selector above each table switches the display to the language to fill in: enter the label for each language used by your teams. Every user sees the label of their interface language.

See also

• Calendar — weekly capacity, exception days and the timesheet entry unit
• Timesheet — day-to-day entry and validation
• Leave — where absence types are used
• Budget — the rates applied to reported time

Good habit

Decide on actual types before the first entry: the key acts as an identifier in exports and the datamart, and changing it afterwards breaks historical continuity.