Workspace
Settings
One singleton of Workspace Preferences: how dates, times and numbers look, the language generated documents are written in, the default Standard Day, and the public-holiday calendar. These are display and default settings only — they never rewrite a stored date or duration.
●
Unsaved changes
Nothing is written until you save. A rejected save leaves the stored row untouched.
Regional display
defaults come from the browser, every value is overridableSeeds the four settings below on first run. It is not the language of generated timesheets.
“Today”, “future date” and every displayed timestamp are evaluated here.
Decimal separator and grouping for durations and day equivalents.
Reorders calendar headers and Quick Fill's row-major focus order.
Changing anything here changes how stored work looks, never the stored work.
2026-03-07 stays 2026-03-07; 450 minutes stays 450.Generated documents
document language ≠ interface languageUsed for every generated timesheet unless a client overrides it. Labels come from a per-language bundle, so a second language is one file — no model or migration change.
Not a product setting and not stored: the app chrome is never translated by the document language.
In the document preview the labels stay Dutch while every button,
menu and error message on this screen stays English.
Standard Day
default for clients without their own arrangementA client may specify another length; a Monthly Timesheet snapshots whichever value applies at creation, so changing this number does not move an existing draft's day equivalents.
Public-holiday calendar
offline tables, movable feasts computedSwitching calendar never rewrites history: an entry already recorded
on a date that becomes restricted keeps its duration. The confirmation is only demanded when a duration is
(re)written.
Live preview
follows the form, not the store — nothing is written until you saveDisplayed decimals are always ≤ 2, half-up, no trailing zeroes
March 2026 in the calendar
header order + flags follow these preferencesStored versus displayed
| Stored | Displayed now |
|---|
Design notes — Settings
- WS-04 Browser values are offered, not silently stored: saving writes explicit values, and a later reload keeps the saved ones.
- WS-06 The rounding table is computed live from the same formatter the screens use, so the rule is demonstrable before any timesheet exists.
- WS-07 Document language and interface language sit side by side on purpose — one is a select, the other a read-only statement.
- STD-02 Invalid standard day answers
standard_day_invalidand the stored value survives. Try the checkbox. - DEC-06 Three calendars offered;
beandnlcomputed from an offline table plus Easter computus. Wrong list ⇒ wrong restricted dates, so the list is shown in full. - GAP-03 No retroactive effect when the calendar changes — stated in the UI rather than left implicit.
- I9 / I10 “Stored versus displayed” panel exists to make the invariant visible to a reviewer, not to the end user.