The calendar, closures and absences

The calendar decides which days count as working days — hence a block's real duration. This guide covers active days, closures (the whole team), and absences (one row).

Active days and working hours

In Settings › Working calendar, the WORKING DAYS section offers a checkbox per weekday (Monday to Sunday) and a Shade inactive days checkbox; WORKING HOURS sets From (hour) and To (hour) for an hourly timeline. Checking or unchecking a day immediately changes what "one working unit" means for the whole schedule. Just above, the Unit type setting (day, hour, quarter-hour…) carries its own warning: "Changing the unit type snaps blocks to the new unit's slots; Ctrl+Z restores them."

Placing a closure

Still in Settings › Working calendar, the CLOSURES AND ABSENCES section lists what already exists ("Name · start date → end date · non-working · whole schedule or one row", with a Remove button) and offers a form below it:

• Name (for example "Summer closure", "Anne's leave")
• From / To
• Kind — Non-working (the only kind observed; a colored range without being non-working is also possible depending on the setting)
• Repeat — Once, or a yearly range that replays every year
• For — The whole schedule, or restricted to a row
• Add button

A closure for the whole schedule blocks out the period for every row. A closure placed for one row (shortcut: right-click the row › Closure on this row…, which opens the same form already filled in for that row) only blocks out that row. For a person's time off, use Add an absence… instead (same menu, or the button in the Agenda tab): it is the same absence an agent adds through MCP, shown in the Agenda and on the rows linked to that person.

What it changes on blocks

The form's own text states it: "A non-working range extends the blocks it crosses and pushes what follows; on rows, it only extends theirs." Verified on a minimal case: two blocks linked hard, A (Oct 5–7) immediately followed by B (Oct 8–9) — starting summary "from 2026-10-05 to 2026-10-09 — 5 working units". After placing a two-day closure (Oct 6–7) crossing A:

1. A stretched out by the number of non-working days it contains — its end, on screen, moved back to the 9th (the non-working range is painted highlighted inside the block). Its duration in working units, though, didn't change.
2. B, linked hard right after A, was pushed by the same number of days — its start moved back from the 8th to the 12th (the connector between the two blocks shows it).
3. The summary confirms it: "from 2026-10-05 to 2026-10-13 — 5 working units" — the period stretched by four calendar days, while the working-unit count didn't move.

A block linked soft wouldn't have moved: that link type never pushes anything (see The timeline: blocks, links and milestones).

What happens when you get it wrong

• A closure with the wrong dates or on the wrong scope: Remove next to its name in the list, or Ctrl+Z right after placing it.
• An active day unchecked by mistake immediately snaps every block onto the new working slots — Ctrl+Z reverts it.

What this page doesn't cover

• The unit type, the headers shown, the reference date: neighboring settings in the same Settings › Working calendar tab, described in Understanding the timeline in five minutes.
• Coloring days (without making them non-working): a different kind of special range, not detailed here.
• The hard and soft links that decide what gets pushed: see The timeline: blocks, links and milestones.