diff --git a/docs-mintlify/admin/monitoring/alerts.mdx b/docs-mintlify/admin/monitoring/alerts.mdx index a2f762539699d..8f900c68cf55a 100644 --- a/docs-mintlify/admin/monitoring/alerts.mdx +++ b/docs-mintlify/admin/monitoring/alerts.mdx @@ -78,9 +78,10 @@ who were invited but never signed in do not receive alerts. ## Delivery -Alerts are delivered by email only — 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 +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. To alert from your own observability stack instead, export telemetry with [monitoring integrations](/admin/monitoring/monitoring-integrations). diff --git a/docs-mintlify/docs/integrations/google-sheets.mdx b/docs-mintlify/docs/integrations/google-sheets.mdx index e49bbe8a30b62..cfd36aeca5baa 100644 --- a/docs-mintlify/docs/integrations/google-sheets.mdx +++ b/docs-mintlify/docs/integrations/google-sheets.mdx @@ -168,15 +168,38 @@ targets the wrong cell. +If a placement's written cells come back empty — for example, someone deleted +them by hand — the spreadsheet home shows a **No data** tag next to it. Opening +the pane also checks whether the cells it wrote still hold what was last +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 +block — that's the anchor limitation described above. + +Use the row menu's **Detach** or **Delete** to stop working with an exploration +in this document. **Detach** removes it from this spreadsheet only — it stays +in your Cube Cloud workspace and in any other document it's placed in. +**Delete** removes it everywhere it's been placed. Both offer to clear the +written cells, which is checked by default. + If an exploration has filters applied, an admin can turn on **Show applied filters in reports** (Settings → Spreadsheet Add-ins) to make the filter state visible on the sheet itself. When enabled, a summary of active filters is added above the table, and filtered columns are marked "(filtered)" in -their header, both when the exploration is inserted and after **Refresh**. +their header, both when the exploration is inserted and after **Refresh**. Each +user can override this for themselves from the add-on's own **Settings**. Saved explorations also appear in the Cube Cloud workspace. See [Saving explorations][ref-explorations] for details. +## Add-on settings + +Open **Settings** from the add-on's menu to set personal preferences: whether +selecting a sheet jumps the pane to its exploration and vice versa, whether an +exploration runs automatically, whether duplicate values in the result are +suppressed, and the per-user override of **Show applied filters in reports** +described above. + [link-google-sheets]: https://workspace.google.com/products/sheets/ [link-marketplace-listing]: https://workspace.google.com/u/0/marketplace/app/cube_cloud_for_sheets/641460343379 diff --git a/docs-mintlify/docs/integrations/microsoft-excel.mdx b/docs-mintlify/docs/integrations/microsoft-excel.mdx index 85052687201af..b3aedd55c2b3a 100644 --- a/docs-mintlify/docs/integrations/microsoft-excel.mdx +++ b/docs-mintlify/docs/integrations/microsoft-excel.mdx @@ -176,15 +176,38 @@ targets the wrong cell. +If a placement's written cells come back empty — for example, someone deleted +them by hand — the workbook home shows a **No data** tag next to it. Opening +the pane also checks whether the cells it wrote still hold what was last +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 +block — that's the anchor limitation described above. + +Use the row menu's **Detach** or **Delete** to stop working with an exploration +in this document. **Detach** removes it from this workbook only — it stays in +your Cube Cloud workspace and in any other document it's placed in. **Delete** +removes it everywhere it's been placed. Both offer to clear the written cells, +which is checked by default. + If an exploration has filters applied, an admin can turn on **Show applied filters in reports** (Settings → Spreadsheet Add-ins) to make the filter state visible on the sheet itself. When enabled, a summary of active filters is added above the table, and filtered columns are marked "(filtered)" in -their header, both when the exploration is inserted and after **Refresh**. +their header, both when the exploration is inserted and after **Refresh**. Each +user can override this for themselves from the add-in's own **Settings**. Saved explorations also appear in the Cube Cloud workspace. See [Saving explorations][ref-explorations] for details. +## Add-in settings + +Open **Settings** from the add-in's menu to set personal preferences: whether +selecting a sheet jumps the pane to its exploration and vice versa, whether an +exploration runs automatically, whether duplicate values in the result are +suppressed, and the per-user override of **Show applied filters in reports** +described above. + [ref-excel]: /admin/connect-to-data/visualization-tools/excel [link-pivottable]: https://support.microsoft.com/en-us/office/create-a-pivottable-to-analyze-worksheet-data-a9a84538-bfe9-40a9-a8e9-f99134456576