Multi-tenant embedded analytics lets one dashboard serve many customers while each viewer sees only the data for their tenant, account, organization, or workspace.
Core idea
Instead of creating a separate dashboard for every customer, build one dashboard with filters for tenant-specific values. Your application backend signs the embed payload and includes the filter values for the authenticated viewer.
Tenant scoping examples
- account_id
- organization_id
- customer_id
- workspace_id
- region
- partner_id
- user_id
Implementation checklist
- Add dashboard filters for tenant and date context.
- Keep API keys on your server.
- Generate embed signatures server-side.
- Include tenant filter values in the signed payload.
- Configure allowed domains for your app.
- Test with several tenants before production launch.
Security notes
Do not trust tenant identifiers supplied directly by the browser. Your backend should determine the tenant from your own authenticated session and then sign the Tractorscope embed payload.