Every piece of data with a date on it has a calendar dimension, even if you usually look at it as a list. Appointments, project deadlines, employee shifts, marketing campaigns, delivery schedules, content publication plans — all of these are considerably clearer on a calendar than in a table. The calendar view turns any date-valued property into a timeline, with no extra setup beyond picking which property to drive it.
Setting one up is a matter of selecting start and end date properties on the underlying type. Events that are simply points in time — a meeting, a reminder, a deadline — need only a start date. Events that span a range — a campaign that runs for two weeks, a shift that runs from 9 to 5, a customer engagement with a known begin and end — get both, and render as horizontal bars across the days or hours they cover. The same calendar can mix the two, so a schedule view can show both deadlines and the multi-day blocks of work leading up to them.
Navigation follows the conventions users already know. Month, week, and day layouts are the standard trio, with keyboard navigation and a clear indicator of the current day. The month view is for orientation — quickly seeing what's busy and what isn't. The week view is for planning — slot-level detail across seven days. The day view is for execution — hour-by-hour, often with events stacked side by side when they overlap.
Per-viewer title property selection is a small but impactful feature. The same calendar can be configured to display an event's subject, its customer name, its responsible person, or whatever other field is most informative for the team looking at it. Different views over the same data can make different choices — a planner's calendar labels events with the customer, while the executor's calendar labels them with the task — and no duplication of the underlying data is required.
Popovers give you a detail peek without leaving the calendar. Hover or click an event and a small card appears with the key fields, action buttons, and a link to open the full record. That's how dense calendars stay readable: the layout shows you when, and the popover shows you what without committing to a full page navigation. For a day packed with appointments, the popover is often all users need.
Click-to-add is the small feature that makes the calendar feel like a living scheduling tool. Click an empty slot and the create form opens with the start date (and end, if applicable) pre-filled based on where you clicked. Any parameters the view itself carries — the customer whose calendar you're looking at, the project you've filtered to — are also pre-set on the new record, so the event lands in the right context without additional input. That turns the calendar from a read-only dashboard into the place you actually plan.
Color cues carry the same visual logic used elsewhere in the platform. Events can be colored by an enumeration property, which lets a user scan a busy month and immediately see the mix: which days are heavy on prospecting, which are loaded with customer meetings, which are packed with internal reviews. Combined with a choice of title property, the calendar communicates a lot of structure at a glance.
Filters and saved queries carry over cleanly from other viewers. A calendar is, under the hood, the same query machinery as a table — the difference is the rendering, not the data. A filter for my events or this region behaves identically on a calendar as on a table, and switching between the two viewers for the same query is a single click. That consistency is what makes it reasonable to offer a calendar as a view on top of any type with a date on it.
Reminders and follow-ups off calendar events are one of the most common automation patterns. An event scheduled for a future date is a natural trigger: send a notification the day before, email the attendees an hour out, create a follow-up task the day after. The calendar is the place people plan the work; the automation layer is the place that work quietly happens. The automations article covers the details. The combination — a visual scheduling surface plus the automations that run off it — is often what finally gets a team off their separate calendar tool and onto the platform that holds the rest of their data.