docs: document alerts inbox delivery, add-in settings, detach/delete, and edit detection

[keydunov]

Summary

Closes three documentation gaps found while cross-checking recently shipped cubejs-enterprise features against docs-mintlify:

• Alerts also deliver to the in-app notification inbox now (cubedevinc/cubejs-enterprise#14489), not email-only as the page previously stated. Updated admin/monitoring/alerts.mdx's Delivery section.
• Sheets/Excel add-in: Settings screen, Detach vs. Delete, and edit detection (cubedevinc/cubejs-enterprise#14638, #14697). Added coverage to docs/integrations/google-sheets.mdx and docs/integrations/microsoft-excel.mdx:
  • The per-user Settings screen (sheet↔pane navigation, auto-run, duplicate suppression, a personal override of the account-wide "Show applied filters in reports" setting).
  • Detach (removes a placement from this document only, keeps the exploration everywhere else) vs. Delete (removes it everywhere), both with an option to clear written cells.
  • The No data tag for a placement whose written cells were deleted, and the edited-cells notice (with a locate action) for a placement whose written cells were typed over.

Why

These shipped as plain feat(...) PRs in the product repo with no matching docs PR. All three are small additions to existing pages, not new capabilities that need a dedicated page.

Test plan

• Docs build (cd docs-mintlify && yarn dev) renders all three pages without broken links or MDX errors.
• Spot-check wording against the merged PRs (cubedevinc/cubejs-enterprise#14489, #14638, #14697) for accuracy.

🤖 Generated with Claude Code

https://claude.ai/code/session_018wnZCSqh4S55XD22NRegsL

---

Generated by Claude Code

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
cubed3	🟢 Ready	View Preview	Sep 4, 2026, 12:24 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

[claude]

Claude finished @keydunov's task in 1m 14s —— View job

---

Docs review: no blockers — 2 low-severity wording notes, both posted inline

Full review

• Read PR diff
• Read full context of the three changed pages
• Check for prior review threads (none existed)
• Post review

What's good

• Both add-in pages stay word-for-word parallel apart from the deliberate vocabulary swap (spreadsheet/add-on vs workbook/add-in) — that's the existing convention on these pages and it's held exactly.
• The edit-detection paragraph explicitly ties back to the anchor limitation two paragraphs above (Neither check catches rows or columns inserted above the block), which pre-empts the obvious reader question instead of leaving it dangling.
• Detach vs. Delete is stated in terms of blast radius ("this document only" vs "everywhere it's been placed") rather than UI mechanics, and the default state of the clear-cells checkbox is called out. That's the detail people actually need before clicking.
• The per-user override is disambiguated from the account-wide Settings → Spreadsheet Add-ins toggle by naming where each one lives. Easy thing to get wrong; it's right here.
• ## Add-on settings / ## Add-in settings are page-level headings, so no docs.json entry is needed — nothing missing there. Markdown reference-link definitions at the bottom of both files are untouched and still resolve.

Findings

#	Severity	File	Note
1	Low	admin/monitoring/alerts.mdx:81-84	"the recipient's in-app notification inbox" is unscoped, but the Recipients section above allows custom email addresses that aren't account users and therefore have no inbox. Suggested scoping inline.
2	Low	docs/integrations/google-sheets.mdx:175, microsoft-excel.mdx:183	which clears the next time you run the exploration attaches to "the changed cells", reading as though a re-run clears them rather than dismisses the notice. Suggested rewrite inline (applies to both files).

Not verified

I can't read cubedevinc/cubejs-enterprise, so the factual claims (inbox delivery for fired and resolved alerts, the four settings listed in the new section, clear-cells defaulting to checked, the No data tag's exact trigger) are unverified against #14489 / #14638 / #14697. Those still need the human spot-check listed in your test plan. I also didn't run the Mintlify dev server; the changes are plain prose and heading syntax with no new components or links, so an MDX break is unlikely, but the build check in your test plan is still worth doing.

No security, performance, or test-coverage surface in this PR — it's prose-only.

• branch `claude/gallant-ramanujan-an09zv`

[claude]

The new inbox sentence leaves one question open that this page otherwise answers carefully: the Recipients section above says Also send to can hold arbitrary custom email addresses that aren't account users. Those addresses can't have an in-app inbox, so "the recipient's in-app notification inbox" is true only for the user recipients. Worth scoping it explicitly so a reader configuring a custom address doesn't expect an inbox entry.

Suggested change

	Alerts are delivered by email, and a fired or resolved alert also appears in the
	recipient's in-app notification inbox — there is no Slack, webhook, or PagerDuty
	delivery. [Scheduled refresh notifications](/docs/explore-analyze/notifications), which
	cover dashboard refresh outcomes, are a separate feature with its own delivery channels.
	Alerts are delivered by email, and a fired or resolved alert also appears in the in-app
	notification inbox of each recipient who is a user on this account — there is no Slack,
	webhook, or PagerDuty delivery. [Scheduled refresh
	notifications](/docs/explore-analyze/notifications), which cover dashboard refresh
	outcomes, are a separate feature with its own delivery channels.

(Only apply if that scoping matches the behavior in cubedevinc/cubejs-enterprise#14489 — I can't read that repo to confirm.)

[claude]

which clears the next time you run the exploration attaches grammatically to "the changed cells", so it reads as if re-running clears the cells (the opposite of what happens — it rewrites them and dismisses the notice). Naming the subject removes the ambiguity:

Suggested change

	written; if any have been typed over or cleared since, it shows a notice with
	an option to jump straight to the changed cells, which clears the next time you
	run the exploration. Neither check catches rows or columns inserted above the
	written; if any have been typed over or cleared since, it shows a notice with
	an option to jump straight to the changed cells. The notice goes away the next
	time you run the exploration. Neither check catches rows or columns inserted above the

Same wording at docs-mintlify/docs/integrations/microsoft-excel.mdx:183.