docs: fix a batch of undocumented/stale Cube Cloud features found in a doc audit - #11519
docs: fix a batch of undocumented/stale Cube Cloud features found in a doc audit#11519keydunov wants to merge 3 commits into
Conversation
feat(console-server) in cubejs-enterprise (#13818) added a membershipChanges attribute to SCIM group create/update/delete audit events, listing which members were added or removed by email. Document it in the Extended view section. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RSU2ReENu3kzHVCUC6z16o
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Claude finished @keydunov's task in 58s —— View job Review: docs-only, looks good — 0 blocking, 2 nitsFull reviewVerdict: Approve-equivalent. Three-line docs addition to Checklist
What's correct
Nits (non-blocking, inline)
Not applicableTests, error handling, input sanitization, query efficiency — no code changed. The unchecked "Linter has been run" / "Tests have been run" boxes in the PR description are fine for a docs-only change; Pre-existing, out of scopeThe page carries several empty screenshot slots (around lines 34, 41, 66) while the Sanitization section still says "You can see that a password was sanitized on the screenshot above." That dangling reference predates this PR — flagging only so it's on the radar, not as a change request here. Fix this → No prior review threads existed on this PR, so nothing to resolve or dedupe against. |
| For `Created group via SCIM`, `Updated group via SCIM`, and `Deleted group via SCIM` | ||
| events, event-specific attributes also include the list of members added to or | ||
| removed from the group, by email. |
There was a problem hiding this comment.
Nit (style): this section is a bullet list, and the new content is a refinement of the "Event-specific attributes" bullet. Folding it in as a nested bullet keeps the section scannable and drops a paragraph, matching the "say it once / be concise" guidance in docs-mintlify/CLAUDE.md. Either form is fine — take it or leave it.
| For `Created group via SCIM`, `Updated group via SCIM`, and `Deleted group via SCIM` | |
| events, event-specific attributes also include the list of members added to or | |
| removed from the group, by email. |
with the list above becoming:
- IP address from which an event was initiated.
- Event-specific attributes. For `Created group via SCIM`, `Updated group via SCIM`,
and `Deleted group via SCIM` events, these include the list of members added to or
removed from the group, by email.Also worth double-checking on the cubejs-enterprise side that Deleted group via SCIM genuinely carries a non-empty membershipChanges payload — for a delete it's plausible the members are implicitly removed without an explicit delta, in which case that third event name shouldn't be listed here.
- Dashboard widget menu now offers per-chart CSV/PNG/PDF download (charts.mdx) - AI widget was renamed to 'Analysis' across the UI (ai-summary.mdx, widgets/index.mdx, CLAUDE.md taxonomy) - Controls now sync manual filter/time-grain changes to the URL on published dashboards (controls.mdx) - Themes can be renamed from the Styling tab's theme menu, not just the admin list (dashboard-themes.mdx) - Dashboard Agent can now edit a dashboard draft in place (editors) or duplicate-then-edit (viewers who can create workbooks), not just adjust session filters (dashboard-agent.mdx) - MCP server gained 4 tools: getBranchDiff, getDeploymentEnv, getPreAggregationStatus, buildPreAggregation (mcp-server.mdx, tool count 16 -> 20) - Snowflake Semantic Views pull now supports scoping by comma-separated names/glob patterns (snowflake-semantic-views.mdx) - New GPT-5.6 Sol/Terra models available for agent LLM selection (admin/ai/index.mdx) - Workbook Agent saves a data question's result into an attached empty tab (workbook-agent.mdx) - Explore's shareable URL now preserves the chat thread, not just query state (explore.mdx) Found via a routine audit cross-checking recent cubejs-enterprise changes against docs-mintlify. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RSU2ReENu3kzHVCUC6z16o
…, branch source picker, and system group visibility - Time dimension filters gained six calendar-period operators: in/not in the month, quarter, year (view.mdx) - Period-over-period comparison can now anchor to a filtered (not just grouped) time dimension (querying-data.mdx) - Data Model IDE's branch switcher gained 'Create branch from...' to fork from an explicitly chosen source, including remote-only branches (data-model-ide.mdx) - Admin -> User Groups now hides system groups by default behind a user/system/all filter, affecting discoverability of the auto-created All embed users group (creator-mode.mdx) Found via a routine audit cross-checking recent cubejs-enterprise changes against docs-mintlify. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RSU2ReENu3kzHVCUC6z16o
|
Claude finished @keydunov's task in 1m 32s —— View job Review: docs-only — 0 blocking, 1 medium (heading nesting), 2 lowFull review — commits
|
| ### Pre-aggregations | ||
|
|
||
| These tools verify that pre-aggregations defined in the data model actually build — including on an un-deployed dev branch, which `runQuery` can't reach since it only hits the deployed SQL API. Gated the same way as [Data model editing](#data-model-editing). | ||
|
|
||
| | Tool | Description | Access | | ||
| | --- | --- | --- | | ||
| | `getPreAggregationStatus` | Lists pre-aggregations with their partitions, how many have built, the newest build time, and the exact error for any that failed. | Read-only | | ||
| | `buildPreAggregation` | Triggers an on-demand build of one pre-aggregation. | Write | | ||
|
|
||
| Both tools target the deploy branch by default; pass a dev `branchName` from `startDataModelEdit` to target that branch's dev worker instead. |
There was a problem hiding this comment.
Heading nesting is now wrong. Inserting ### Pre-aggregations here splits the Data model editing section from its own #### How model edits stay safe subsection (line 294), which now renders as a child of Pre-aggregations. Its content is entirely about model edits — "Edits never touch production", "startDataModelEdit is the only entry point", "Promotion is manual and human" — so under Pre-aggregations it reads as if those constraints govern buildPreAggregation, which they don't (that one does write, and it's a plain Write, not gated behind a dev branch).
Fix: move this whole ### Pre-aggregations block down so it starts after Review pending work with getDataModelChanges before you commit. (line 312), keeping Data model editing → How model edits stay safe intact.
Also, once it moves, the cross-reference "Gated the same way as Data model editing" reads naturally as a back-reference rather than a forward one.

Check List
Description of Changes Made
Found via a routine audit cross-checking recent
cubejs-enterprise(Cube Cloud product) changes againstdocs-mintlify. Each item below is a small, surgical edit — no new pages. Grouped by area:Audit Log
admin/monitoring/audit-log.mdx).Dashboards & widgets
widgets/charts.mdx).widgets/ai-summary.mdx,widgets/index.mdx, and the taxonomy indocs-mintlify/CLAUDE.md.widgets/controls.mdx).admin/customization/dashboard-themes.mdx).dashboard-agent.mdx).MCP & AI-engineer
getBranchDiff,getDeploymentEnv,getPreAggregationStatus,buildPreAggregation— bumping the documented tool count from 16 to 20 (docs/integrations/mcp-server.mdx).*-glob patterns (docs/integrations/snowflake-semantic-views.mdx).gpt_5_6_sol/gpt_5_6_terrapredefined models available for agent LLM selection (admin/ai/index.mdx).workbook-agent.mdx).explore.mdx).Data modeling & filters
in/not in the month,quarter,year(reference/data-modeling/view.mdx).querying-data.mdx).data-model-ide.mdx).all_embed_usersgroup) by default behind a user/system/all filter (embedding/iframe/creator-mode.mdx).A separate, larger tenant-wide time-zone policy feature (admin default zone, personal override, embed override) was also found undocumented; given its scope it's being tracked as a Linear ticket for a dedicated docs page rather than bundled into this PR.