Skip to main content

Calendar writer

Exposes ICS feeds teammates embed in personal devices partner apps or reporting sinks read-only outbound mirror.

Adding the App

  1. AppsApp StoreCalendar writer enable.
  2. Generate feed tokens per persona or pooled secret depending security model.
  3. Distribute HTTPS URLs expiry rules optional rolling tokens.
  4. Document consumer refresh cadence Apple slow Google medium.

Token leak rotation Apps troubleshooting for stuck regeneration UI.

App-specific requirement

Anyone with URL reads whatever scope you mapped classify URLs like passwords.

Usage

Personal practitioner subscribe on iPhone

What it is for: Side calendar outside Timelish still shows bookings.

Prerequisites: Staff understands delay minutes inherent to consumer polling.

Franchise rollup dashboard

What it is for: BI tool ingesting ICS parses counts.

Prerequisites: Parser tolerates quirks repeating rules notes.

Share limited busy mask without titles

What it is for: Privacy first leaders hide client names externally.

Prerequisites: Choose masking template if offered.

Partner agency visibility

What it is for: External coordinator sees tentative holds.

Prerequisites: Contract governs SLA refresh frequency.

Removing the App

  1. Installed apps → Calendar writer revoke feeds tokens.
  2. Confirm consumers receive 403 afterwards.

After you disconnect

Published endpoints stop emitting Timelish severs linkage cached copies on phones decay naturally.

Security hygiene

If URL leaked before shutdown rotate any downstream stored secrets consumers clear subscriptions.