Multi-tenant embedded analytics: show each customer only its own data

Metabase supports multi-tenant embedded analytics through guest embeds with locked parameters or Pro and Enterprise modular embeds using JWT single sign-on and user attributes. Guest embeds work on all editions, including open source, do not create Metabase accounts or incur per-viewer billing, and securely pass a server-signed tenant ID as a locked filter, though each embedded dashboard card must be connected to that filter and viewers cannot use drill-through or the query builder. Modular embedding creates Metabase accounts for signed-in viewers and applies tenant-based row and column security across dashboards, drill-through, and customer-created queries, but requires paid Pro or Enterprise plans and counts viewers as users. The guide details configuring both approaches, separating guest-token and SSO signing keys, validating requested embedded resources, sourcing tenant IDs only from the application’s authenticated session, and implementing token endpoints in Next.js, Django, and Rails. It also covers optional tenant management for customer-specific collections and permissions, as well as connection impersonation, database routing, and schema-based permissions for SQL questions or separate customer data stores, while outlining plan pricing and feature availability.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.