diff --git a/references/workspace/custom-roles.mdx b/references/workspace/custom-roles.mdx
index 96d11f17..f621a399 100644
--- a/references/workspace/custom-roles.mdx
+++ b/references/workspace/custom-roles.mdx
@@ -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