Create calendars
Each calendar is a named, colored container backed by a content record — so who can see or edit it follows the same permissions as the rest of your content.
Bosca Calendar
Calendars and events with repeating schedules that survive real life, participants with RSVP statuses, and attachments that point at actual content — plus overlays for everything else the platform has scheduled.
How it works
Each calendar is a named, colored container backed by a content record — so who can see or edit it follows the same permissions as the rest of your content.
One-off, or repeating on whatever rhythm you need. Invite participants with roles and RSVP statuses, and attach the content that matters — an agenda, the minutes, a collection of materials.
Month, week, and day views with drag to move and resize — plus read-only overlays that put scheduled campaigns, jobs, and content publishes on the same grid.
What makes it powerful
Everything you expect from a calendar — recurrence, RSVPs, drag to reschedule — plus the view you only get when the calendar lives inside the platform doing the scheduling.
Daily, weekly, monthly, or yearly — every second week, weekdays only, ending after ten times or on a date — on the same standard the major calendars use.
Change one occurrence, this-and-following, or the whole series — real exceptions and splits, not workarounds.
Invite profiles to an event with a role and an RSVP status — accepted, declined, or still pending — stored on the participant record.
Link documents or collections to an event under a relationship label — agenda, minutes, or anything you name.
Read-only synthetic calendars project scheduled campaigns, jobs, and content publishes onto the same views as your events.
Three views in Studio with direct manipulation — drag an event to move it, drag its edge to resize it.
Repeating events are computed for the window you're looking at — no stored copies to drift out of sync, and runaway rules are capped.
A calendar is backed by a content record, so visibility and editing follow your existing content permissions — no second ACL.
Built on content, fed by the platform
The calendar isn't a silo with its own accounts and its own idea of a document — it's built from the platform's own parts, and it shows the platform's own plans.
bosca/v-calendar) — its name and its permissions come from the content system, so sharing a calendar is sharing content.bosca/v-calendarSpring launchLanding page v2occurrences(from, to, calendars)Go deeper
Your meetings and the platform's own schedule, on one grid, under one permission model. The docs cover calendars, events, participants, and repeating series end to end.