Skip to content

The easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart:

docs: tenant example (#71365)

Alex Yarosh161ebe81d5c6
diff --git a/docs/embedding/tenants.md b/docs/embedding/tenants.md
index 6b109dba138..cf3f760dbd4 100644
--- a/docs/embedding/tenants.md
+++ b/docs/embedding/tenants.md
@@ -192,8 +192,6 @@ You can create tenant-level [user attributes](#tenant-attributes) which all user
![Edit tenant](./images/edit-tenant.png)
-There are three ways to add a tenant attribute, using the Metabase UI, the API, or JWT SSO.
-
To create a tenant attribute manually using the Metabase UI:
1. Go to **Admin settings > People**
@@ -201,7 +199,7 @@ To create a tenant attribute manually using the Metabase UI:
3. Click on **three dots** next to the tenant.
4. Input the attribute key and value.
-For details on how to set tenant attributes using JWT tenant claims, see [Setting tenant attributes using tenant claims](#setting-tenant-attributes-using-tenant-claims) below.
+You can also assign tenant attributes automatically through JWT claims, see [Setting tenant attributes using tenant claims](#setting-tenant-attributes-using-tenant-claims) below.
Once you add a tenant attribute, all users of that tenant will inherit the attribute, but the value can be overridden for any particular user, see [Edit user attributes](../people-and-groups/managing.md#adding-a-user-attribute).
@@ -274,7 +272,8 @@ To create tenant attributes from JWT SSO, include a claim `@tenant.attributes`:
{
"@tenant": "meowdern_solutions",
"@tenant.attributes": {
- "industry": "cat food"
+ "id": "13371337",
+ "name": "Mammoth Solutions"
},
"email": "[email protected]",
"first_name": "Mister",
@@ -319,7 +318,7 @@ Please review [Data permissions documentation](../permissions/data.md) for more
### Use tenant attributes for data permissions
-[Row and column security](../permissions/row-and-column-security.md), [Impersonation](../permissions/impersonation.md), and Database routing require user attributes. You can [specify custom tenant attributes](#tenant-attributes) to configure data permissions based on attribute values. See [Tenant attributes](#tenant-attributes). Alternatively, you can use the special tenant slug attribute, see [Special slug attribute](#special-tenant-slug-attribute).
+[Row and column security](../permissions/row-and-column-security.md), [Impersonation](../permissions/impersonation.md), and Database routing require user attributes. You can [specify custom tenant attributes](#tenant-attributes) to configure data permissions based on attribute values. See [Tenant attributes](#tenant-attributes).
## Collection permissions for tenants
@@ -349,7 +348,7 @@ Permissions are granted to groups. Which permissions are available to each group
### Internal user collection permissions
- Metabase Admins will have **Curate** access to all shared collections and all tenant collections.
-- Other internal groups and non-admin users have **No** access by default, but can be granted **View** or **Curate** access to **shared collections**. See [Configuring shared collection permissions](#configuring-shared-collections-permissions) for details.
+- Other internal and non-admin groups have **No** access by default, but can be granted **View** or **Curate** access to shared or tenant collections. See [Configuring shared collection permissions](#configuring-shared-collections-permissions) for details.
For configuring permissions to _internal_ collections for internal users, see [general docs on collection permissions](../permissions/collections.md).