Time off has had a list of requests since it shipped. A list answers "who asked for what". It does not answer the question you usually have, which is "does anything break that week".
People → Time off → Time off calendar lays the month out: one row per person who is away, one column per day. You can see at a glance that two of the three people who know the deployment are off the same week, which is not something a list of requests will ever tell you.
The approve and decline buttons are on that screen, under the grid, and that is deliberate. Deciding one request without seeing the week around it is how a team ends up with nobody covering.
Reading it
- Solid is approved. Striped is requested and not yet agreed.
- Half filled is a half day. A shaded column is a weekend.
The solid-versus-striped distinction is the one worth remembering: pending time off is not time off yet, and planning cover around it is the mistake the stripes exist to prevent.
Who appears
The same rule as everywhere else in People, enforced by the database rather than by the page: a member sees their own time off, a manager sees themselves and the people who report to them, an administrator or owner sees everybody.
Only people who actually have time off in the month get a row. Somebody with nothing booked is not listed — a wall of empty rows buries the answer. When nobody you can see is away, the page says so and names the month.
Colors
Each leave type now has a color, set under People → Time off → Configure next to the type's name. Until you choose one, each type is given a consistent color of its own, so the calendar reads properly before anybody configures anything.
What it is not
It does not show public holidays or working patterns — it shows time off that was requested. For "who was expected to work and logged nothing", Reports → Coverage already does that, and it does account for holidays and non-working days.