Tour calendars

Tour calendars let you publish selected calendar information without giving someone full workspace access.

Tour calendar template settings with visibility templates and active shared links — Tour calendar templates control which event fields external collaborators and public links can see.

You can create a tour calendar, add eligible events to it, and share it as a web page or calendar feed. Use this for artist itineraries, tour routing, production handoffs, and people who need routing context without workspace navigation.

Only events marked Internal + External can be added to a tour calendar. Draft events are excluded. This matters because the tour calendar is not a second permission layer that makes an internal event safe after the fact; the event itself must be intended for external visibility.

A tour calendar can show calendar records in a public-style view with compact rows, expanded rows, table-style detail, month context, and map context when location data is visible. Recipients can search, filter, inspect event detail, switch the page language, download event files, and subscribe to a calendar feed when those controls are available for the share.

Tour calendars are separate from workspace membership. Creating tour calendars, adding or removing events, changing team/public sharing, regenerating links, revoking links, and emailing a share link all require the Share calendars permission.

There are three different access ideas that are easy to confuse:

Access path	Use it for	What controls access
Internal team sharing	Let other signed-in workspace members see the tour calendar inside Calendar.	The tour calendar's private/team setting. Only its creator can change this setting.
Public link	Let anyone with the link open the tour calendar web page.	The tour calendar's share token plus an Anyone with link access rule and its visibility template.
Calendar subscription	Let a recipient add the tour calendar to Apple Calendar, Google Calendar, Outlook, or another calendar app.	A subscription token. Regenerating or clearing the share token revokes existing subscriptions for that tour calendar.

Named external users are related, but they are managed separately in External users. They have an external session, a template, and optional artist scope. Use that model when you need a named outside collaborator instead of a bearer link.

Visible fields

Tour calendars use visibility templates so you can choose what an outside person sees. For example, one audience might need dates, cities, venues, and public notes; another might also need travel fields, ticket links, or contact details.

The core fields are always included: title, date, event type, status, category, and performance type. Optional fields can add artists and organizers, agency contacts, venue and location, times and schedule, tickets and links, travel logistics, contract and invoice status, guest list, and external notes.

Some internal data should never be treated as public calendar content. Internal notes, private tasks, private updates, and workspace-only context belong in Offstage, not in broad calendar links. Deal terms and financial line items can be shared, but only through an explicit template grant that starts switched off; think twice before granting them on a broad link. Use Visibility and sharing when deciding which layer should carry a detail.

Offstage treats the visibility template as an access rule, not just a display preference. Hidden fields stay out of the public calendar and feed, internal notes stay internal, and deal terms, revenues, and expenses appear only when the template grants them. Calendar feeds never include them.

Recipient view

The recipient view is built for people who need to understand the itinerary without seeing the internal workspace. Depending on the template and event data, a recipient can:

switch between compact and expanded event views;
use search across visible event text;
filter by time range, date or week from the month context, event type, status, artist, organizer, or venue;
use map context when coordinates are visible;
open an event detail panel for venue, times, tickets, travel, accommodation, return travel, guest list, and external notes;
download one event as an .ics file;
subscribe to the full feed or download all shared events as .ics;
switch the page language for their own reading context.

If a field is hidden by the template or missing on the event, it should not appear in the recipient detail panel. This is why template design matters: a public tour calendar can feel rich without exposing internal deal data.

Public tour calendar recipient view with event table, search, filters, language switcher, download, and subscription controls — Recipients get a calendar view of their own. They can search, filter, switch the page language, inspect visible event details, and use download or subscription controls.

Calendar feeds

Calendar feeds are useful when someone wants events to appear in their own calendar app. A feed should contain only the event detail that is appropriate for that audience, and it is intentionally less detailed than the web page.

Feeds include the event title, date, visible timing, visible artist or organizer names, visible venue/address context, and a link back to the tour calendar when those fields are allowed. If show time is hidden, the feed does not leak the time through DTSTART; the event appears as date-only. Travel events can create separate calendar entries for outbound travel, accommodation, and return travel.

Use the web page when the recipient needs to filter, inspect details, browse the map, or download individual event files. Use a feed when the recipient mainly wants the dates to stay synced in Apple Calendar, Google Calendar, Outlook, or another calendar app.

The direct download option is a snapshot; it will not update when the tour calendar changes. Subscription is the better option when the recipient needs updates. Regenerate or clear the share token when old links and subscribed feeds should stop working.

Tour calendar download confirmation warning that downloaded ICS events are a one-time snapshot — Download is the snapshot path. Use it when someone needs a file export, not an updating calendar subscription.

Operational checklist

Before sending a tour calendar:

Check that each event is marked Internal + External.
Confirm the tour calendar contains the right events and no stale routing holds.
Choose a visibility template that matches the audience.
Open the public link yourself and inspect the recipient view.
Use the feed only when the recipient needs calendar-app syncing; use the web page when they need the richer itinerary.
Review old active links in Settings when the tour calendar or audience changes.

Relationship to events

Tour calendars do not replace the internal show detail page. The event remains the source of truth for staff: tasks, documents, contracts, invoices, updates, and private notes stay on the internal record. The schedule is the outward-facing view of selected calendar information.