Skip to main content

TabCalendar Documentation

Last updated: February 23, 2026 (America/Los_Angeles)

Applies to version/build: TabCalendar Production (controlled access) docs baseline (updated February 19, 2026; see changelog)

Skip docs search

Search TabCalendar docs

Find setup, troubleshooting, limitations, scopes, changelog, and operational guides from this docs hub.

Showing 6 of 6 TabCalendar docs.

  • TabCalendar · Guide

    TabCalendar Documentation

    Operator docs for TabCalendar: setup, limitations, scopes, troubleshooting, and changelog.

    /apps/tabcalendar/docs

  • TabCalendar · Setup

    TabCalendar Setup

    Install TabCalendar, configure deal-date layers, and validate behavior in a controlled rollout slice.

    /apps/tabcalendar/docs/setup

  • TabCalendar · Limitations

    TabCalendar Known Limitations

    Current TabCalendar boundaries and what to do when you hit them.

    /apps/tabcalendar/docs/limitations

  • TabCalendar · Troubleshooting

    TabCalendar Troubleshooting

    Operator triage for common TabCalendar issues (auth, context, and optional integrations).

    /apps/tabcalendar/docs/troubleshooting

  • TabCalendar · Scopes

    TabCalendar Scopes and Permissions

    OAuth scope summary for TabCalendar with least-privilege context.

    /apps/tabcalendar/docs/scopes

  • TabCalendar · Changelog

    TabCalendar Changelog

    Release notes for the TabCalendar public docs surface on clevercat.app.

    /apps/tabcalendar/docs/changelog

TabCalendar is a CleverCat operational utility for HubSpot: a hosted fullscreen calendar for year-at-a-glance availability planning.

TabCalendar is a production app with controlled access.

These docs are written for operators. They describe what ships, what doesn’t, and a low-risk first-run path. (Promises live elsewhere.)

Operator index

What it does (today)

  • Launches from HubSpot Company and Deal record tabs and opens the hosted fullscreen calendar (/calendar/fullscreen).
  • View modes: Year / Month / Week / Day (year view is the year-at-a-glance surface).
  • Availability statuses: sold, held, unavailable.
  • Day-level actions: manual holds, plus deal and note creation from a selected date.
  • Optional / configuration-dependent: multi-artist mode (watch list) and Google Calendar import overlays.
  • Optional / enablement-gated: ICS subscription feeds (may be disabled by default).

Start small. Validate the boundaries with one portal and a handful of Company records before you widen access.

  1. Install TabCalendar in HubSpot and complete OAuth authorization.
  2. From a Company record, open the TabCalendar record tab and click Open TabCalendar to launch fullscreen.
  3. Confirm view switching works in fullscreen: Year / Month / Week / Day.
  4. Configure at least one deal-date layer and confirm status mapping uses: sold, held, unavailable.
  5. Validate one action end-to-end: create a manual hold, a Deal, and a Note from day detail.
  6. If you plan to use external availability overlays, validate Google import for one Company (optional).
  7. If you expect multi-artist comparison, configure the watch list first, then re-validate scope (optional).
  8. Review limitations and scopes before wider rollout.

Boundaries (read this before rollout)

TabCalendar does:

  • Provide a hosted fullscreen calendar experience anchored to Company context (Deal context resolves to Company).
  • Visualize availability using the canonical status set: sold, held, unavailable.
  • Support one-way Google Calendar import as unavailable overlays (when enabled).

TabCalendar does not:

  • Render the full calendar inside the HubSpot record tab card (the card is a launcher).
  • Provide a published HubSpot Workflow Action (metadata exists, but the action remains unpublished).
  • Provide bidirectional Google sync.
  • Treat ICS subscription URLs as “safe to share” links (and the feature may be disabled by default).

Support intake checklist

When you contact support, include:

  • Portal ID
  • Record URL(s) (Company and/or Deal)
  • What you clicked (exact steps) and what you expected vs what happened
  • Timestamp with timezone
  • Screenshots (and any visible error text)
  • Whether the issue involves: status layers, create actions, multi-artist, Google import, or ICS