The Calendar Five views, fourteen colour-coded sources, two time zones, and the keys that move you around.

There is one calendar. Not a NearSync calendar sitting alongside your Google calendar: one grid showing everything, including the parts of your working life that are not really calendar events at all.

The five views

View	Shows	Key
Day	One day, hour by hour	1
Week	Seven days	2
Work week	Your working days only	3
Month	The month, with a day panel	4
Team	Who is free, across your team	5

The timed views run from 7am to 9pm. Anything outside that is still in the data and still opens; the grid is drawn for the hours most people work rather than for all twenty-four, because a grid that fits the day is worth more than one that fits every possible day.

Work week is not Monday to Friday. It is your hub's working days. In a hub that works Sunday to Thursday, that is what you get, and the weekend shading follows the same source. Nobody configures this per person, and nobody has to remember to.

Month view shows a compact grid, and clicking a day opens a panel beside it with that day laid out on a vertical time rail: each event as a dot on the line, with its time, title and source. It is the fastest way to answer "what is that week actually like" without leaving the month.

Team view is different in kind. It is about availability rather than events, and it has its own piece.

Overlapping events

Where events collide, they are laid out side by side in columns rather than stacked on top of each other, so a triple-booked hour reads as three blocks rather than one block hiding two.

Two small behaviours worth knowing. A very short event still renders at a readable minimum height rather than as an unclickable sliver. And an event whose end time is not after its start, which happens occasionally with imported data, falls back to a one-hour block rather than disappearing.

Colour is the source, not the subject

Every event is tinted by where it came from. Fourteen sources, in three groups, and the grouping is the part worth learning.

Providers: things that connect

Source	Colour
Google	Sky blue
Microsoft	Deep blue
Internal	Violet
WhatsApp	Emerald
WebChat	Grey
Calls	Teal

The first three are calendars. The last three are conversations that produced a commitment: a booking made over WhatsApp, one made through the website chat, or a phone call logged against a contact.

They are grouped with providers because they are channels rather than subjects, and they are on the calendar because they are things happening at a time. A customer who booked through WhatsApp is exactly as much of a commitment as one who booked through a form.

Time off

Source	Colour
Holidays	Rose
Leave	Indigo

Public holidays for your hub, and approved leave. Neither is an HQ, both are availability, which is why they sit in a group of their own.

Leave appears automatically. Nobody has to remember to block their calendar before going away, and nobody can quietly not.

HQ calendars: things the business does

Source	Colour
Marketing	Pink
CRM Tasks	Slate
Sprints	Cyan
Training	Violet
KB Articles	Sky
Bookings	Teal

These are dates that live inside other parts of the platform. A campaign going out. A sprint boundary. An article scheduled to publish. A task with a deadline. A customer booking.

They are on your calendar because they are things happening on a date that affect you, and keeping them somewhere else is precisely how deadlines get missed by people who were not looking at that somewhere else.

Turning sources off

Every source can be switched off from the side panel, and each one shows a count so you can see exactly what you are hiding.

Everything on is the right default for the first week and rarely right after it. Most people settle on hiding two or three HQ calendars they have no part in, which turns a busy grid back into a readable one.

Turning a source off is a display choice and nothing more. Nothing is deleted, nothing stops syncing, and turning it back on brings everything with it.

Two time zones at once

A second time zone can run down the side of the grid.

By default it is your hub's zone when that differs from where you actually are, which is the case this was built for: you travel, your hub does not, and every meeting you book while travelling is an opportunity to book it in the wrong reality.

Any zone can be chosen instead, from the full list, searchable, and your choice is remembered between sessions.

The two columns show the same instants in both zones, so a 4pm slot is visibly half past twelve somewhere else before you send the invitation rather than after somebody declines it.

Keyboard

Key	Does
T	Jump to today
N	New event
1 2 3 4 5	Day, week, work week, month, team
Left or J	Previous
Right or K	Next

These only fire when you are not typing and no panel is open, so they never eat a character you meant for a field. They also stand down when a modifier key is held, so nothing here fights a browser shortcut.

Previous and next move by whatever you are looking at: a day in day view, a week in week view, a month in month view.

Opening an event

Clicking an event opens a detail panel on the right, carrying what colour cannot tell you.

The attendees, with their responses, so you can see who has actually accepted rather than who was invited.

Your own response, which you can change from here.

The meeting link, where there is one, with the provider named.

Whether Pippin Scribe is set to join, and a control to send it if not.

A link through to the source, for events that came from elsewhere in the platform. A sprint boundary opens the sprint; a booking opens the booking.

The panel is also where deletion happens, and where a repeating event asks which occurrences you meant.

Syncing external calendars

Connected Google and Microsoft calendars sync on their own schedule. The sync control forces a check for when you have just changed something on the other side and do not want to wait for it to catch up.

There is a fuller resync behind it for the rarer case where the two have genuinely drifted apart. It costs a slower refresh and it fixes the problem properly rather than papering over it.

What the grid will not tell you

Colour tells you where an event came from. It does not tell you whether anybody accepted, whether it is being recorded, or whether it matters.

For all three, open it. The panel takes one click and answers all of them, which is a better arrangement than encoding six things into a coloured rectangle nobody can decode without a key.