From ff06a45e7f64941133e56f9994304bcc46654a89 Mon Sep 17 00:00:00 2001 From: "metabase-bot[bot]" <109303359+metabase-bot[bot]@users.noreply.github.com> Date: Tue, 30 May 2023 16:50:20 +0000 Subject: [PATCH] docs - fix typo in db privileges (#31085) (#31159) Co-authored-by: Natalie <nat@metabase.com> --- docs/databases/users-roles-privileges.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/databases/users-roles-privileges.md b/docs/databases/users-roles-privileges.md index f8614644925..09d16fe96d8 100644 --- a/docs/databases/users-roles-privileges.md +++ b/docs/databases/users-roles-privileges.md @@ -139,7 +139,7 @@ Let's say you have customers named Tangerine and Lemon: - Create new database users `metabase_tangerine` and `metabase_lemon`. - Create a `customer_facing_analytics` role with the `CONNECT` privilege. - Create roles to bundle privileges specific to each customer's use case. For example: - - `tangerine_queries` to bundle read privileges for people to query and create stored procedures against the Orange schema. + - `tangerine_queries` to bundle read privileges for people to query and create stored procedures against the Tangerine schema. - `lemon_queries` to bundle read privileges for people to query tables in the Lemon schema. - `lemon_actions` to bundle the write privileges needed to create [actions](#privileges-to-enable-actions) on a Lemonade table in the Lemon schema. - Add each user to their respective roles. -- GitLab