Everything that is planned, in one place

Four views, and the URL is the view

Dag, Week, Maand and Jaar, each with a keyboard shortcut (d, w, m and y for the view, t to jump back to today). The chosen view and the date live in the URL, so the back button behaves and a link to one particular week lands your colleague on that same week. Which view you normally open is a personal preference remembered per user rather than something buried in org settings — and a shared link always beats that preference, so opening someone else's link never quietly overwrites your own choice. In Dag and Week, timed items are positioned on the hour grid; whole days stay a bar along the top. The year view deliberately ships no individual events to the browser, only a count per day.

Five feeds from three modules

Every feed comes from the module that actually owns the data, so the Agenda need not know the insides of any of them. That is also why your calendar grows with you: if you do not run Verlof or the Google integration, those feeds simply do not exist, and there is no empty slot where they should have been.

• Verlof (team), from the leave module: who is away and when, with still-pending requests muted and marked with a question mark
• Feestdagen, from leave as well: not a chip but a quiet marking across the day, because a public holiday is nobody's absence and nobody's working day
• Ingeplande taken, from the tasks module: the time blocks set with "Taak inplannen", yours and those of the colleagues you overlaid
• Taakdeadlines, also from tasks: your own open tasks with a date in range, red the moment they run late
• Google Agenda, from the Google integration: your own appointments, read from the local copy the integration keeps and therefore never fetched from Google live

Colour and visibility, saved per person

The feed menu doubles as the legend: it names every enabled feed, hidden ones included, with a dot in whatever colour you gave it. Leave can be split per colleague on top of that, each with their own colour and their own toggle, so "colour Stan purple" beats "colour the whole leave feed blue", which in turn beats the leave type's own colour. Splitting per colleague is only offered to someone who may read other people's leave; an ordinary team member keeps their own calendar in one colour. Public holidays are deliberately not recolourable, because they draw as a dashed band rather than a coloured pill. All of this is personal preference, and a hidden feed genuinely costs nothing: it is never fetched.

A drag is a real change

Drag a leave day or a task block to another day and the Agenda hands it back to the module that owns the item; the core calendar knows no module's API at all. The server then recomputes: leave that lands in a week with a public holiday gets cheaper by itself, and an edit to already-approved leave goes back to pending with your approver. The drag is only offered where a change could actually succeed (your own request, or someone else's with the right permission), but the API stays the boundary, not the button. Timed blocks keep their wall-clock time, including on the two days a year the clocks move: that conversion happens on the server, in your organisation's own timezone.

Plan from the calendar, and log hours against it

The Nieuw button lets you plan without leaving the calendar: a task block (date, start time, duration, note, for yourself or, with the right permission, for a colleague) or, one click onward, a leave request. What the menu offers follows your modules and your permissions, so someone who may not schedule tasks never sees the option. Once a block has passed it offers Uren registreren: that is where the real time entry comes from, and the block is marked as logged, so planning and recording are not the same work done twice. Beyond that the Agenda is a staff screen: a client signing in to the portal gets no team calendar. The calendar itself is core functionality and needs no licence key; which feeds hang in it follows the modules you run, and Verlof and the Google integration are extension modules running on a licence key.