[torimwhaley]

Batch 3 of the cloudy-needs-review burn-down. Every change was checked against the lightdash codebase before editing, and each issue has its own commit.

• Closes Document how Lightdash Cloud organizations enable service accounts #1333: Service accounts. Cloud orgs can't turn them on themselves. The Lightdash team enables them, so a Cloud admin who doesn't see Service Accounts should contact support. The section heading drops "(self-hosted only)". Verified: the service-accounts commercial feature flag gates the settings entry (useSettingsContext.ts), and only self-hosted instances can set it, via SERVICE_ACCOUNT_ENABLED (parseConfig.ts).
• Closes Clarify that results caching and pre-aggregates speed up warehouse query time, not dashboard rendering time #1341: Caching. Results caching and pre-aggregates only speed up query execution, not loading and rendering the dashboard. The note is qualitative, with no numbers. Verified: both take effect inside AsyncQueryService, which is backend query execution.
• Closes Document that AI agent issues can capture requests when users cannot open pull requests directly #1342: AI agent issues. Turns are scanned whoever asked, so users who can't open writeback or coding-agent PRs still get their findings on the board. The writeback and coding-agent prerequisites now link to it. Verified: enqueueReviewClassifierEvent is gated only by the org-level isAiAgentReviewsEnabled, not by the user's permissions.
• Closes Document that SSH-tunneled queries open separate SSH sessions to the bastion #1371: SSH tunnel. Each tunneled query opens its own SSH session to the bastion, so concurrent queries mean concurrent sessions. Verified: acquireUnscoped creates a new SshTunnel and calls connect() on every acquisition, and it skips the client cache when useSshTunnel is set.
• Closes Clarify embedding availability on the embedding docs pages #1373: Embedding availability snippet, which is shared by every embed page. It no longer promises embedding to every Cloud account and says it's available where Lightdash has enabled it. Verified: embedding sits behind the embedding commercial feature flag.
• Closes Explain that the self-hosted Slack app manifest's scopes are a required set, not a pick-list #1380: Self-hosted Slack app. The manifest's bot scopes are a required set. Each Slack feature turns off when its scopes are missing until you reinstall, and chat:write.customize backs the bot avatar. Verified: SLACK_FEATURE_SCOPES / getSlackFeatureAvailability (slackSettings.ts), getCustomIconArgs (SlackClient.ts), and SchedulerFormSlackError.tsx. Correction to the issue: availability is checked per feature now, so a missing scope only turns off the features that need it. Scheduled deliveries isn't disabled whenever any scope is missing. The new text follows the code.

Left out

• Document that AI agents do not query the warehouse directly #1336 and Clarify that data app refresh is available on the published view, not just while building #1368 are already fixed in open PR docs: 35 small fixes from the issue backlog triage #1511 (data-access.mdx and data-apps.mdx), which closes both. Changing them here would conflict with that PR.
• Clarify that disposable editing is not safe for concurrent/parallel edits #1366 was already fixed on main by Scope disposable editing to non-concurrent workflows #1369 ("scope disposable editing to non-concurrent workflows"). The comparison table and the Disposable editing section say the later upload overwrites earlier changes. Upload does no version check (CoderService.upsertChart). The issue just wasn't closed, so it can be closed by hand.
• Document the AI agents fast-response decision feature and its self-hosted environment variables #1345 (fast-response decisions): the issue's claim is incomplete. JEV_API_KEY alone doesn't turn it on. resolveAiDecisionClient also needs the org-scoped ai-agent-fast-decisions feature flag, which is described in code as a "master rollout switch". It's also off for Bedrock-routed orgs and agents pinned to a credential. Whether to document this rollout flag and the third-party JEV provider for self-hosters is a product decision, so I left it out.

Noticed, not changed

• The manifest on the self-hosted Slack page has no reactions:write, even though the code lists it as the scope for writeback reactions (SLACK_FEATURE_SCOPES). It's worth a separate look.

Checks: npm run validate:docs -- --changed-files PASSED, npm run audit:components -- --baseline PASSED (baseline holds), mint validate (4.2.917) passed, mint broken-links --check-anchors clean.

Linked Linear issues AE-1184, AE-1211, AE-1213, AE-1255, AE-1262, and AE-1270 are assigned to Tori. Their status is unchanged.

Commits are unsigned (made on a box that can't use 1Password SSH signing).

[mintlify]

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

Project	Status	Preview	Updated
lightdash	🟢 Ready	View Preview	Oct 21, 2026, 12:37 PM

[github-actions]

Documentation validation

✅ All blocking checks passed.

Component system

0 finding(s) across the corpus.

Findings on lines this pull request touched are annotated inline in Files changed.

View the validation run.