Settings and Time Zones
This guide covers the settings that shape how your calendar reads, with an emphasis on the one thing distributed teams fight most: time zones. After this page you will set your clock and zone, put a colleague's zone on screen next to yours so a meeting never lands at the wrong hour, tune the grid to your taste, and understand exactly how a repeating meeting behaves when the clocks change.
Opening Calendar Settings
After this section you will find every setting. Open the settings gear in the top bar to reach Calendar settings. Changes save to your account and a confirmation banner tells you the save succeeded. If the server reports a problem, the message is shown to you directly rather than failing quietly.
Your Time Zone and Clock
After this section you will read every time correctly. Set your primary time zone from a searchable picker, and choose a 12-hour or 24-hour clock. These control how times are shown to you across the calendar. Each timed event also carries its own zone (set on the event editor), which is what keeps an event anchored to the place it belongs to even when you travel.
Show More Than One Zone at Once
After this section you will see two or more zones side by side on the grid. The time gutter down the left of the Day and Week views can show up to five ordered time-zone columns, each with an optional short label (up to 40 characters, for example "New York" or "Team, London"). Add a zone, give it a label, reorder the columns, and remove one you no longer need. A 9 a.m. Eastern meeting then reads at a glance in London and in San Francisco without anyone doing the arithmetic in their head.
Does each event keep its own time zone, and can I see several zones side by side? Yes on both. A timed event stores the zone you set on it, so it stays anchored to that place; and the Day and Week gutter can show up to five labeled zone columns at once, so a cross-zone meeting reads correctly for everyone without mental conversion.
Grid Display: Weekends, Week Numbers, and Density
After this section you will tune the grid to how you like to read it. Several display choices take effect on the grid immediately:
- Show weekends: include or hide Saturday and Sunday in the Week and Month views, to focus on the work week.
- Show week numbers: display the number of each week alongside the grid, useful for teams that plan by week number.
- Density: choose Responsive, Comfortable, or Compact to fit more or less on screen.
The calendar grid currently begins the week on Sunday. If starting the week on another day is important to your team's read, hiding weekends and showing week numbers give you most of the practical benefit today, and the week-start choice is part of the calendar's ongoing display work.
Can I show week numbers or hide weekends? Yes, both are settings that reflow the grid the moment you change them. The grid begins the week on Sunday today; if a Monday start is essential to your workflow, hiding weekends and showing week numbers cover most of the need in the meantime.
Recurring Meetings and Daylight Saving
After this section you will understand why a repeating meeting sometimes shifts by an hour, and it will stop surprising you. A recurring event is anchored to a time zone. For its owner it stays locked to the same local time all year, including across a daylight saving change, which is what you want: your 9 a.m. standup is always at 9 a.m. for you. For an attendee in a different zone, the meeting can appear to move by an hour for the few weeks each year when their zone and the anchor zone have switched to or from daylight saving on different dates. Nothing is broken; the two regions are briefly a different number of hours apart. When a recurring meeting spans zones, state the anchor zone in the invitation so everyone reads it the same way. Editing across a series is covered in Recurring Events.
Why does my recurring standup shift by an hour a few weeks a year? Because your zone and the meeting's anchor zone enter daylight saving on different dates, so for a short window they are one hour further apart than usual. The meeting is still anchored correctly; it is the gap between the two regions that changed. Naming the anchor zone in the invite prevents confusion.