Skip to content

Clarify Manage Custom SQL vs Manage SQL Runner permissions #423

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
torimwhaley merged 3 commits into from
Feb 18, 2026
Merged

Clarify Manage Custom SQL vs Manage SQL Runner permissions #423

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4b73419
Clarify Manage Custom SQL vs Manage SQL Runner permissions
torimwhaley Feb 18, 2026
348d985
Remove em dash from permissions tip
torimwhaley Feb 18, 2026
7005653
Move SQL scope clarification to custom roles page
torimwhaley Feb 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions references/workspace/custom-roles.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,6 +81,20 @@ Custom roles are assigned at the project level to provide granular access contro
3. Select the custom role from the dropdown
4. All members of the group will inherit the custom role permissions for this project

## Scope reference

### Manage SQL Runner vs Manage Custom SQL

These two scopes are independent and control different features.

**Manage SQL Runner** controls access to the [SQL Runner](/guides/developer/sql-runner), which lets users write and run ad-hoc SQL queries directly against your data warehouse. It also controls the ability to create [virtual views](/guides/developer/virtual-views) and [write back dbt models](/guides/developer/dbt-write-back) from SQL Runner queries.

**Manage Custom SQL** controls the ability to create [custom SQL dimensions](/guides/custom-fields) inside the Explore view. Custom SQL dimensions let users add calculated fields to an existing table using raw SQL. This scope does **not** grant access to the SQL Runner.

<Tip>
If you want a user to query tables that include custom SQL dimensions created by others, they don't need either of these scopes. Any user with access to the Explore view can **use** existing custom SQL dimensions in their queries - these scopes only control who can **create** them.
</Tip>

## Troubleshooting

### Users Can't See Expected Content
Expand Down