docs: document analytics chat sharing

[keydunov]

Check List

• Tests have been run in packages where changes have been made if available
• Linter has been run for changed code
• Tests for the changes have been added if not covered yet
• Docs have been added / updated if required

[mintlify]

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

Project	Status	Preview	Updated (UTC)
cubed3	🟢 Ready	View Preview	May 22, 2026, 7:16 PM

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

[claude]

Claude finished @keydunov's task in 45s —— View job

---

Review: docs: document analytics chat sharing

• Gather context and read changed files
• Review documentation content
• Post review feedback

---

Overall: Clean, well-written documentation addition. The new "Sharing" section is placed logically between "Queued messages" and "Embedding," and the prose is clear and consistent with the existing page style. A few minor observations below.

Feedback

1. Verify the screenshot URL is live
The image at https://static.cube.dev/docs/explore-analyze/analytics-chat/share-dialog.png is referenced but since this is a new asset, please confirm it's been uploaded and accessible before merging. A broken image would degrade the page significantly.

2. Consider mentioning how to revoke access
The section explains how to grant access (individual users, user groups, organization-wide) but doesn't mention how to revoke it. If revoking is possible through the same dialog, a brief note would round out the section (e.g., "To remove access, reopen the Share dialog and remove the user or switch General access back to Restricted.").

3. Minor: "Chat not available" — is this the exact error text?
Line 43 mentions recipients seeing a "Chat not available" page. Worth double-checking this matches the actual UI string so users can recognize it.

4. Formatting and style ✓

• <Frame> / <img> usage is consistent with other pages in docs/explore-analyze/
• Markdown line wrapping matches the existing file convention
• Section heading level (##) is correct
• Em dashes and smart quotes are used consistently

5. No code, security, or performance concerns
This is a docs-only change with no code impact. No testing required.

---

Looks good to merge once the screenshot URL is confirmed live. Nice, concise addition. 👍