Use cases
What teams use Scalendar for.
Four ways teams put a calendar in the channel doing the work. Pick the one closest to yours.
The category
What teams use a shared team calendar for, in Slack.
A shared team calendar is the single source of truth for what a team is doing and when. The launch date. The Friday retro. The community AMA. Who's off next week. The kind of dates that shouldn't live in someone's personal Google or Outlook calendar — and definitely shouldn't live in a Notion doc nobody updates.
Scalendar makes the shared team calendar a Slack-native object. Every calendar is a team channel calendar — scoped to one Slack channel, with the same membership and the same audience. The team doing the work is the team that sees the dates.
Below are some of the most common things teams use it for. Each has its own walkthrough.
All use cases
Launches & deadlines
A product launch calendar pinned in the channel that's shipping the launch. Code freezes, demos, retros — visible to everyone who actually has to do them, never lost in a thread.
See workflowStandups & rituals
A team standup calendar for the channel running the standup. Recurring sync, design crit, retro — visible to the whole channel, with a ping the moment it's about to start. No more "starting now" DMs.
See workflowCommunity events & meetups
A Slack community events calendar for AMAs, workshops, and office hours. Members spot what's coming on the App Home and get reminded the moment it kicks off — no calendar invite hunting.
See workflowVacation & PTO tracking
A vacation tracker and team OOO calendar in one shared #team-ooo channel. Who's off, when, and for how long — at a glance, with no spreadsheet involved.
Pick a use case. Install Scalendar. Done.
Two calendars are free forever — no card, no contract, thirty seconds to install.
Add to Slack