Skip to content

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

docs: remove temp tenants docs (#67819)

Alex Yaroshc1f08f65a697
diff --git a/docs/people-and-groups/assigning-users-to-tenants.md b/docs/people-and-groups/assigning-users-to-tenants.md
deleted file mode 100644
index 7cd2924bbc3..00000000000
--- a/docs/people-and-groups/assigning-users-to-tenants.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Assigning tenant users to tenants
-description: How to automatically assign users to tenants using SSO authentication (JWT and SAML).
----
-
-# Assigning tenant users to tenants
-
-{% include plans-blockquote.html feature="Tenants" %}
-
-If you're running a multi-tenant application, you can assign users to tenants based on a claim in the JWT token.
-
-## Prerequisites
-
-- Multi-tenant user strategy must be enabled in Metabase
-- JWT authentication must be configured
-
-## How it works
-
-When a user logs in with JWT:
-
-1. Metabase reads the tenant identifier from the JWT claim. By default, this is the `@tenant` key.
-2. If the tenant doesn't exist, Metabase automatically creates it
-3. New users are automatically assigned to the tenant from their JWT
-
-## Example JWT with tenant claim
-
-```json
-{
- "email": "[email protected]",
- "first_name": "Jane",
- "last_name": "Doe",
- "@tenant": "acme-corp"
-}
-```
-
-## Important restrictions
-
-**Users cannot change tenants.** Once an external user is assigned to a tenant, they cannot switch to other tenant.
-
-If a user attempts to log in with mismatched tenant information, they will receive one of these errors:
-
-- `Cannot add tenant claim to internal user` - JWT includes a tenant, but the user is an internal user. Only tenant users can have a tenant.
-- `Tenant claim required for external user` - JWT lacks a tenant claim, but the user is an external user.
-- `Tenant ID mismatch with existing user` - JWT has a different tenant than the user's assigned tenant
-- `Tenant is not active` - The tenant exists but has been deactivated
-
-# Configuring the tenant claim
-
-By default, Metabase looks for a `@tenant` key in your JWT. You can customize this:
-
-1. Go to **Admin** > **Settings** > **Authentication** > **JWT** > **User attribute configuration**
-2. Change the **Tenant assignment attribute** key to your preferred identifier.
diff --git a/docs/people-and-groups/authenticating-with-jwt.md b/docs/people-and-groups/authenticating-with-jwt.md
index bb89160381e..ecb88faa284 100644
--- a/docs/people-and-groups/authenticating-with-jwt.md
+++ b/docs/people-and-groups/authenticating-with-jwt.md
@@ -42,7 +42,7 @@ These are additional settings you can fill in to pass user attributes to Metabas
- **First name attribute:** the key to retrieve each JWT user's first name.
- **Last name attribute:** if you guessed that this is the key to retrieve each JWT user's last name, well then you have been paying attention.
- **Group assignment attribute:** the key to retrieve each JWT user's group assignments.
-- **Tenant attribute:** the key to retrieve each JWT user's tenant. Default is `@tenant`. See [Assigning tenant users to tenants](./assigning-users-to-tenants.md).
+- **Tenant attribute:** the key to retrieve each JWT user's tenant. Default is `@tenant`. See [Tenants](../embedding/tenants.md).
You can send additional user attributes to Metabase by adding the attributes as key/value pairs to your JWT. These attributes will be synced on every login.
@@ -109,7 +109,7 @@ To require people to log in with SSO, disable password authentication from **Adm
## Assigning tenant users to tenants
-If you're running a multi-tenant application, you can use JWT to automatically assign users to tenants based on a claim in the JWT token. See [Assigning tenant users to tenants](./assigning-users-to-tenants.md) for details.
+If you're running a multi-tenant application, you can use JWT to automatically assign users to tenants based on a claim in the JWT token. See [Tenants](../embedding/tenants.md) for details.
## Note about Azure