From 3438e466ad8a9e37e42ba35b907c0cfa9f0cf511 Mon Sep 17 00:00:00 2001 From: Natalie <nat@metabase.com> Date: Thu, 1 Jun 2023 13:01:57 -0400 Subject: [PATCH] link (#31222) --- 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 09d16fe96d8..482874de3eb 100644 --- a/docs/databases/users-roles-privileges.md +++ b/docs/databases/users-roles-privileges.md @@ -132,7 +132,7 @@ GRANT metabase_model_caching TO metabase; ## Multi-tenant permissions -If you're setting up multi-tenant permissions for customers who need SQL access, you can [create one database connection per customer](https://www.metabase.com/learn/permissions/multi-tenant-permissions#option-2-granting-customers-native-sql-access-to-their-schema). That means each customer will connect to the database using their own database user. +If you're setting up multi-tenant permissions for customers who need SQL access, you can [create one database connection per customer](https://www.metabase.com/learn/permissions/multi-tenant-permissions#granting-customers-native-sql-access-to-their-schema). That means each customer will connect to the database using their own database user. Let's say you have customers named Tangerine and Lemon: -- GitLab