docs(features): add Warehouse Metrics page - #218
Conversation
Add Warehouse Metrics under Features, covering prerequisites, permissions, creating a metric, aggregation options, Insights visualization, refresh frequency, costs, and early-access limitations. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Confidence Score: 4/5The PR is not yet safe to merge because the existing permissions guidance still incorrectly grants all Project Admins warehouse-metric management access. The previous permissions finding remains unresolved: the table still says every Project Admin can create and manage warehouse metrics, while the following note says access depends on the independently assignable Create and Manage Data Warehouses permission. Files Needing Attention: docs/features/warehouse-metrics.mdx
|
| Filename | Overview |
|---|---|
| docs/features/warehouse-metrics.mdx | Adds the Warehouse Metrics guide; the previously reported permission guidance remains inaccurate. |
| docs.json | Adds the Warehouse Metrics page to Features navigation. |
Reviews (6): Last reviewed commit: "Merge branch 'main' into warehouse-metri..." | Re-trigger Greptile
- Repeat the connected-warehouse prerequisite at the top of the metric creation steps so it isn't missed - Add a Time zones section covering UTC-offset handling and conversion to the project time zone - Frame permissions around the Create and Manage Data Warehouses permission rather than the Admin role, since Enterprise custom roles make Admin an unreliable indicator Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
simplified user roles sections
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| | **Project Admins** | Create and run warehouse queries, save them as warehouse metrics, set the refresh frequency, and choose who to share each metric with. | | ||
| | **Other Users** | Use a warehouse metric that's been shared with them in new reports they create, and view the metric's data in any report they can access. | |
There was a problem hiding this comment.
Enterprise custom roles can independently grant or withhold Create and Manage Data Warehouses. A non-admin with this permission can create metrics, while an admin without it cannot, so these rows give both groups incorrect guidance. Describe access in terms of the permission instead.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Document the two entry points to the SQL editor for a saved metric: the three-dot menu on a metric in an Insights report, and the Edit button on the metric in Lexicon. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The table now keys on Project Admins, so the sentence framing access by the Create and Manage Data Warehouses permission no longer matched it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
added details about custom roles
2 participants
Adds a new Warehouse Metrics page under the Features group.
What's here
docs/features/warehouse-metrics.mdxdocs.jsonCovers prerequisites and supported warehouses, permissions, creating a metric, aggregation options, visualizing in Insights, refresh frequency, data/privacy, warehouse costs, how it differs from Warehouse Connectors, and early-access limitations.
Notes for review
> 📘/> 🚧callouts became<Note>, absolutedocs.mixpanel.comlinks became relative/docs/..., and the H1 moved into frontmatter.<Frame>image, so this reads sparse by comparison. Worth adding shots of the metric builder and the Insights metric picker before this leaves draft.🤖 Generated with Claude Code