-- Use BigQuery-specific grantee and privilege names:
- - Use `user:jeremy@dbtlabs.com` (do not use `jerco_user`)
- - Use `roles/bigquery.dataViewer` (do not use `select`)
+On BigQuery, "privileges" are called "roles," and they take the form `roles/service.roleName`. For instance, instead of granting `select` on a model, you would grant `roles/bigquery.dataViewer`.
+
+Grantees can be users, groups, service accounts, domains—and each needs to be clearly demarcated as such with a prefix. For instance, to grant access on a model to `someone@yourcompany.com`, you need to specify them as `user:someone@yourcompany.com`.
+
+We encourage you to read Google's documentation for more context:
+- [Understanding GCP roles](https://cloud.google.com/iam/docs/understanding-roles)
+- [How to format grantees](https://cloud.google.com/bigquery/docs/reference/standard-sql/data-control-language#user_list)
-## BigQuery examples
+### BigQuery examples
Granting permission using SQL and BigQuery:
@@ -169,25 +261,3 @@ models:
-
-## General examples
-
-When granting permissions, you can optimize for single or multiple users.
-
-Granting a single permission:
-
-```sql
-{{ config(materialized = 'incremental', grants = {
- 'select': 'bi'
-}) }}
-
-```
-
-Granting multiple users the same permission:
-
-```sql
-{{ config(materialized = 'incremental', grants = {
- 'select': ['bi','reporter']
-}) }}
-
-```
diff --git a/website/docs/reference/resource-configs/plus-prefix.md b/website/docs/reference/resource-configs/plus-prefix.md
index 42501f1197..3d143e8ea1 100644
--- a/website/docs/reference/resource-configs/plus-prefix.md
+++ b/website/docs/reference/resource-configs/plus-prefix.md
@@ -62,3 +62,9 @@ models:
Since it doesn't hurt to use the `+` prefix, we recommend you use it whenever adding configs to your `dbt_project.yml` file.
+
+