Repository navigation
Status pages: which Communicate plan unlocks what, and status pages vs dashboards - #794
Conversation
Incident automation and status page maintenance need Communicate Team, not the Team plan for checks. Add a feature/plan table and a short comparison of status pages and dashboards to the overview. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
hlenke
left a comment
There was a problem hiding this comment.
Needs changes · The plan table is accurate, but three sibling pages still use the wording this PR fixes. Update them in this PR so the docs agree.
I checked every entry in the new Plans table against the product's plan definitions, and all of them are correct. It's a useful addition. Nothing blocks the merge. Only the sibling sweep is missing, plus one wording fix.
Important: siblings that still say the old thing (not in this diff, so they're listed here)
guides/communicate-availability.mdx:231still hasIncident automation is available on Team and Enterprise plans.That's the same ambiguous sentence this PR changes on the overview and incidents pages. Suggested:Incident automation is available on Communicate Team and Enterprise plans.learn/incidents/anatomy-of-a-status-page.mdx:60sayson Team and Enterprise plans, [automation rules](...). Suggested:on Communicate Team and Enterprise plans.communicate/status-pages/password-protection.mdx:9saysPassword protection is available as a Communicate Team add-on.That leaves out Enterprise, which the new table lists, and it still uses "add-on", the term this PR replaces on the maintenance windows overview. Suggested:Password protection is available on Communicate Team and Enterprise plans.
I grepped main for the other plan notes on status page features. custom-domain.mdx (Starter, Team and Enterprise), customization.mdx and status-pages/maintenance-windows.mdx (Team and Enterprise) already match the table.
Merge readiness
- CI: all six checks pass (docs-gate, static-docs-checks, preview-checks, Mintlify deployment, link-rot, vale-spellcheck).
- Mergeable, state CLEAN. Since the merge base,
mainchangedcommunicate/status-pages/overview.mdxin 415f636 (#799), which added a maintenance-window sentence under Uptime calculation. GitHub reports no conflict, and the new Plans section still lands after that paragraph. - Overlap: #792 touches
communicate/status-pages/custom-domain.mdx, which this PR only links to. Either can land first. pr_impact.py: no removed pages or anchors and no broken links. The only note is thatcommunicate/maintenance-windows/overviewis a hub page, and its slug and anchors are unchanged.
Section placement: Plans and Status pages and dashboards come after Uptime calculation and before Monitoring as code, so the page's main content stays first. That position works.
Inline: 0 blockers, 0 important, 1 wording.
What I checked
- Read the full diff from merge base 7da4a04 to head 339491b:
communicate/status-pages/overview.mdx,communicate/status-pages/incidents.mdx,communicate/maintenance-windows/overview.mdx. Also read the whole overview page at the head andcommunicate/dashboards/overview.mdxonmain. - Verified against source (monorepo origin/main@2d79b98589):
apps/backend/api/src/common/services/billing-ng/products/communicate/communicate-hobby.ts,communicate-starter.tsandcommunicate-team.ts. Hobby includes status pages, components (services), subscribers and email notifications. Starter adds custom domain. Team adds status page maintenance, incident automation, theme colors (custom CSS), password protection and custom domain.apps/backend/api/src/common/services/entitlements/lib/plan-overrides.ts: the Enterprise (contract) plan includes all five gated features. The Team plan for checks includes none of them, which supports "A Team plan for checks doesn't include the Communicate Team features".- The theme customization row maps to the custom CSS entitlement, which gates theme colors. See
apps/webapp/src/pages/status-pages-next/status-pages-editor/sections/StatusPageEditorThemeColorsSection.vueand enforcement rule201-status-page-custom-css.ts.
- https://www.checklyhq.com/pricing/: the Communicate section uses the tier names Hobby, Starter, Team and Enterprise. The extracted text appears to list custom domain from Starter and the other four features from Team. The feature matrix didn't extract cleanly, so the source files above are the primary evidence. The tier names support the "Communicate Team and Enterprise" wording.
- Grepped
mainfor "Team and Enterprise", "Communicate add-on" and related plan notes in*.mdxto find the siblings above. - CI (
gh pr checks), mergeability (gh pr view),git log <base>..origin/mainon the touched files, the open-PR file list for overlap, andpr_impact.py. - No end-to-end test. Plan entitlements depend on billing, and
checkly testcan't exercise them, so the claims were verified against source. - Could not verify: nothing outstanding.
What changed
Why
"Team" was ambiguous: users on the Team plan for checks expected incident automation and status page maintenance to work, but those come with the Communicate Team plan. Users also regularly ask whether they need a status page or a dashboard.
Verification
Verified against the product code and on a local instance: with the Team plan for checks and no Communicate plan, custom domains, password protection, theme customization and automation rules were refused; Communicate Starter added custom domains; Communicate Team and Enterprise allowed all of them. Status page maintenance gating was verified against the code.
Checks
frontmatter, anchors, internal links, redirects, sitemap and
mint broken-links: all pass.🤖 Generated with Claude Code