The short version: Notion has no native world clock, which is why a small market of embeddable widget vendors exists just to add one, and a documented manual approach (a page or database column of cities and UTC offsets) is common too. Both solve the "what time is it for them" display problem. Neither actually schedules a meeting, that's a different job a dedicated app like Atlas is built for.
If your team runs on Notion, you've probably noticed it has no built-in way to see what time it is for a teammate in another city. People have built two real workarounds, worth knowing both before reaching for a third-party widget.
Workaround 1: embeddable world-clock widgets
Several vendors (Indify, Blocky, Apption, widgetsfornotion.com) sell small embeddable clocks specifically for Notion pages, real enough demand that multiple independent businesses exist to fill this one gap. You paste an embed block into a page and it shows a live clock for the city you choose.
Workaround 2: a manual tracking page
A documented approach is a dedicated Notion page or database with one row per teammate, their city, and their UTC offset, updated by hand and rechecked whenever daylight saving shifts. It costs nothing beyond the time to build and maintain it, which is exactly where the manual approach tends to break down.
This kind of page tends to start well, right after someone builds it, then quietly go stale: a new hire never gets added, a teammate relocates and nobody updates their row, or the whole page just stops being anyone's job to maintain after the person who built it moves on. A tracker only a few people remember to check is barely better than no tracker at all.
What both approaches are missing
A clock, embedded or hand-built, tells you the time. It doesn't shade anyone's actual working hours, doesn't tell you when a group's schedules overlap, and doesn't suggest or book a meeting. You still do the scheduling maths yourself, on top of maintaining the tracker.
An embedded clock is genuinely useful for a quick glance while you're already in a Notion page. It just isn't trying to solve the harder problem: working out when everyone can actually meet.
Where Atlas fits
Atlas lives in your Mac menu bar rather than inside a Notion page, and does the part neither workaround attempts: it shades each teammate's real working hours on a map, auto-suggests the best overlapping meeting time, and books it to your calendar in one tap, daylight saving handled automatically. It's a $4.99 one-time purchase, and it works whether or not your team runs on Notion at all, so it doesn't ask you to change how the rest of your team already works.
So which should you use?
Keep a Notion widget if all you want is a glance at teammates' local time while you're already working in a page. Add Atlas the moment the real question becomes "when can we actually meet," since that's the step neither Notion approach was built to answer.
Frequently asked
Does Notion have a built-in world clock?
How do people track time zones in Notion manually?
Are the Notion world-clock widgets any good?
When does a dedicated app beat a Notion widget?
How much does Atlas cost?
Do any of the Notion time-zone widgets update automatically for daylight saving?
Stop doing timezone math
Atlas finds the time everyone's awake and adds it to your calendar in one tap.
One-time purchase, yours forever.