docs: clarify HSM delivery dashboard setup and sharing steps#647
docs: clarify HSM delivery dashboard setup and sharing steps#647SangeetaMishr wants to merge 2 commits into
Conversation
Add a note that the Contacts table step is only used to open the query editor in the right dataset (the query itself only reads messages), and a note on setting Looker Studio sharing to "Anyone with the link" so teammates outside the owner's account can open the dashboard. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
🚀 Deployed on https://deploy-preview-647--glific-docs.netlify.app |
|
Warning Review limit reached
Next review available in: 51 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis change updates the HSM Delivery Dashboard setup documentation with two added notes. One clarifies that selecting Contacts is only to open the BigQuery editor in the correct dataset context, while the actual query reads from the messages table. The other explains that the Looker Studio preview link is tied to the report owner's account and must be re-shared for teammates outside that account to access it. Changes
Sequence Diagram(s)Not applicable; this change is documentation-only. Estimated code review effort: Low Related PRs: None identified. Suggested labels: documentation Suggested reviewers: None identified. Poem A rabbit hops through docs so neat, 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…otes Add the read-time/level/Last Updated header used elsewhere in the docs (Last Updated: July 2026), and drop backticks from the two notes added in this PR for consistency with review feedback. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Summary
Addresses #332
This is a partial fix - the issue also asks to change the preview dashboard URL so it can be opened by all, but I don't have access to the live Looker Studio report's sharing settings to change them directly. Instead, this documents the sharing step needed so report owners know to fix access themselves.
Changes:
Contactstable" step in Part 1 is only used to open the BigQuery query editor in the right dataset context - the query itself only reads from themessagestable. Kept the step as-is per feedback, just added the clarifying note rather than removing it.Open question
The issue also mentions "remove the contact_collection table" from the query, but the current query only selects from
messages- there's no contact_collection (or similar) table referenced anywhere in it. If there's a specific query change intended here, please comment and I'll follow up in this PR.Verification
Ran
yarn buildlocally (with dummy Algolia env vars matching CI) to confirm the docs site still builds cleanly with this change.Test plan
Summary by CodeRabbit