docs: clarify scopes for custom SQL dimensions vs SQL Runner#588
Open
docs: clarify scopes for custom SQL dimensions vs SQL Runner#588
Conversation
The custom-roles scope reference described "Manage Custom SQL" as the scope that controls custom SQL dimensions in Explore. That scope actually controls saving SQL Runner output as a saved chart. Custom SQL dimension authoring is gated by "Manage Custom Fields" (description: "Create and edit custom dimensions"), which the page didn't mention at all. - references/workspace/custom-roles.mdx: rename the section to "SQL-related scopes", correct the "Manage Custom Sql" description, add a third entry for "Manage Custom Fields" pointing at custom SQL dimensions in Explore. - guides/custom-fields.mdx: note that on Enterprise, the admin/developer requirement can be opened up to any custom role with the "Manage Custom Fields" scope. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
🤖 Documentation Bot✅ All checks passed! No issues found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The custom-roles scope reference had an incorrect description of which scope controls custom SQL dimensions in Explore. This came up while reviewing docs after lightdash#22555, which re-lands the FE hides + diff-aware backend save gate for SQL custom dimension authoring. The PR enforces the `manage:CustomFields` scope, but the docs page didn't mention that scope at all.
Test plan
🤖 Generated with Claude Code