Documentation
A practical guide to safer booking-link handoffs.
Start with setup, learn how findings work, and understand exactly what happens when you disconnect.
What BookableCheck is for
BookableCheck helps HubSpot administrators find scheduling pages and future CRM meetings that still reference deactivated users. It groups those risks into actionable findings, automates supported meeting-owner reassignments, explains the appropriate workflow for the remaining items, and checks the data again after the work is complete.
It is designed for a common gap between offboarding an employee and keeping the company’s public booking flow healthy. It is not a calendar migration tool.
Choose a guide
Setup
Requirements, scopes, installation, the initial scan, and the Pro authorization flow.
Open setup guide →Using BookableCheck
Findings, issue types, offboarding cases, replacement mappings, alerts, and verification.
Open usage guide →Disconnect & uninstall
Stop scans, remove access, understand deletion timing, and cancel Stripe billing separately.
Open disconnect guide →Plan boundaries
| Capability | Free | Pro |
|---|---|---|
| Scanning | One completed initial scan | Daily, offboarding, and verification scans |
| Results | Deactivated-user and risky-link counts | Authorized admins see exact users, links, and classifications |
| Workflow | Upgrade prompt | Automated meeting reassignment, page remediation, and offboarding cases |
| Alerts | None | New, worsened, and failed-scan alerts |
| History | Aggregate scan result | 90 days for resolved findings and scan history |
Who can see details
BookableCheck uses the signed HubSpot user context for every in-app request. Users with the exact integration-management permission can access paid details and settings. Everyone else receives the same aggregate summary shape used by the free plan.
The backend enforces this rule. Hiding a screen element in the browser is never treated as authorization.
Need help?
Email support@bookablecheck.com with your HubSpot portal ID, the time of the issue, and the scan ID if one appears. Do not send access tokens, attendee details, or calendar invitation contents.