Bosca / Calendar

Platform overlays

The platform knows what's coming

Campaigns are scheduled, jobs are queued, publishes are timed — that schedule already exists inside Bosca. Overlays put it on the calendar next to your own events, instead of leaving it scattered across admin pages.

Three sources

Campaigns, jobs, publishes

Three synthetic feeds project other subsystems' schedules into calendar events — queried by date range like everything else.

  • Campaigns — scheduled audience campaigns, so the send date sits next to the meetings about it.
  • Scheduled jobs — what the scheduler will run and when.
  • Publishes — content scheduled to go live, visible before it does.
  • Each synthetic event carries its source, title, times, and a completed flag — enough to see at a glance what's done and what's still ahead.
overlays · this week
campaignSpring launch emailThu 10:00
jobnightly-syncdaily 02:00
publishLanding page v2completed

Read-only by design

A lens, not a second control panel

Overlays show the schedule; they don't own it. The systems that created those entries stay the single place to change them.

  • Overlay events can't be dragged, edited, or deleted from the calendar — they're projections, refreshed from their source of truth.
  • Each overlay renders in its own color, toggled from the sidebar like any calendar.
  • To change a campaign's send time or a publish date, you do it where that schedule lives — and the overlay reflects it.
sidebar
Team calendareditable
Campaignsread-only
Scheduled jobsread-only
Publishesread-only

Content-backed calendars

A calendar is content too

Your own calendars follow the same philosophy as the overlays: reuse the platform instead of duplicating it.

  • Every calendar is backed by a content record of type bosca/v-calendar — its name lives on the content, the calendar adds color and description.
  • Permissions are inherited from that record — who can view, edit, or manage a calendar is decided by the content permissions you already run.
  • Deleting a calendar removes its backing record, and its events go with it — one lifecycle, no orphans.
  • In Studio, month, week, and day views render whichever calendars you've toggled visible, events colored by their calendar.
Team calendar
Backed bybosca/v-calendar
Color#7659f2
Permissionsinherited from content

Keep exploring

More on Calendar

Calendar overview

Calendars, events, repeating series, and platform overlays.

Events & participants

Event fields, RSVPs with roles and statuses, and content attachments.

Recurrence

Repeating events, one-off exceptions, series splits, and clean endings.