# Absences: My absences, the Agenda, risks An **absence** belongs to a person, not to a plan: entered once in your preferences, it applies to every plan you're a member of. It never moves a block — it flags a **risk** on whatever is assigned to you. This guide covers the three places that talk about it: **My absences** (where you enter them), **linking a row to a member** (what lets an absence weigh on a block), and **the Agenda** (where you see them, by person and over time). ## Entering an absence: Settings › Absences In **Settings**, the **Absences** tab (`/settings?onglet=absences`) lists your absences and offers a three-tab form, for the three requested shapes: - **A date range** — *From* / *To*, with a **starting half-day** and an **ending half-day** (morning or afternoon). A one-day range with the same starting and ending half-day covers only that half-day; with different ones (morning → afternoon), it covers the whole day. - **A short absence** — a single **day**, and its **duration**: full day, morning, or afternoon. A shortcut for the most common case of a range. - **A recurring day** — one or more checked **days of the week**, **every N weeks** (1 to 4, counted from the week of the start date), a **starting on** date, an optional **until** date (empty = no end), and a **scope of the day** (full day, morning, or afternoon). Each shape asks for a **reason**, from a closed list: *Leave*, *Part-time*, *Training*, *Other*. There is no free-text field, and no medical reason is offered: the screen never asks *why* you're away, only that you are. **Add** enters the absence; it immediately joins the list, stated in plain language — for example "Every Friday starting on September 1, 2026 · Leave", or "From August 4, 2026 (morning) to August 22, 2026 (afternoon) · Leave". **Modify** reopens the absence in the same form, on its original tab, fields already filled; **Save** replaces it, **Cancel** closes the form without changing anything. **Remove** deletes it. ## Linking a row to a member An absence only weighs on a block if someone links it there — through an **assigned action** (S10), or through the **row** itself. The second gesture lives in the grid: right-click a row opens its menu, which now carries **Link to a member**, a submenu with **None** and one name per current member of the plan. A checkmark marks the member already linked; clicking another name replaces it, clicking **None** unlinks the row. The gesture is undoable (Ctrl+Z) like the others. A row linked to someone who is no longer a member of the plan (removed, or their account disabled) shows it in that same menu as **"Member removed from the plan"** — an entry you can't pick again, but you can still unlink with **None**. Every block on a linked row now counts toward the person it names, on each block's own dates: that's what the risk list (the Risks tab of the side panel) and the Agenda's shading read. ## A plan's Agenda **Agenda**, in the Bar's menu (next to Print), opens `/s/:id/agenda` in a new tab: the plan's **current members** in rows, **time in columns**, at the same scale as the Gantt — the time header and the background grid are painted by the same drawing as the editor's timeline. Each member's absences are painted as background shading, **half-days included**: a morning or afternoon absence only covers half the day's column. The names area stays fixed on the left; the rest scrolls horizontally if the period to show is wider than the screen. With no block and no absence on the plan, the Agenda says so instead of showing an empty, dateless grid. With no member (a plan you just created, alone), it says so too. ## Who sees what Everyone manages their own absences in their Settings; the instance owner can manage them for anyone from the admin screen. A plan's owner, though, cannot modify another person's agenda: an absence applies to every plan that person belongs to, and that power would reach beyond the one plan they own. In a plan's Agenda, as in its risk list, you only see the absences of that plan's **current members** — never those of someone who doesn't share it with you, and never those of a former member, even if a row still names them. ## If you get it wrong - **An absence with the wrong dates or reason**: **Modify** it in the list, or **Remove** it and enter it again. - **A row linked to the wrong member**: reopen its menu, **Link to a member**, pick the right one — or **None** to unlink. **Ctrl+Z** right after the gesture undoes it too. ## What this page doesn't cover - **The risk calculation itself** (how many working days an absence covers on a block, partial or total) and how it's shown on the Gantt (the marker on the block, the side panel's list): a different topic, to be documented separately. - **A plan's calendar** — closures, non-working days on rows — which remains the S13 tool, described in *[The calendar, closures and absences](/docs/en/guides/calendrier-fermetures-absences/)*: a range placed there is a team matter and moves blocks; a personal absence, here, moves none. - **Assigned actions**, the other path that links a person to a block: see *[A block's actions and its derived progress](/docs/en/guides/actions-et-avancement/)*.