How is tenant isolation enforced?

Every API endpoint validates tenant ID against the requester's JWT scope. The database uses tenant_id columns + row-level policies. Penetration tests confirm isolation.

Can a venue see other venues' data?

No. Venue admins see only their own venue. MSPs see all venues they manage. Resellers see only their assigned slice.

All features

MSP & Ops

MSP Multi-Tenant Management

A native multi-tenant model that mirrors how MSPs actually sell. Super admin manages the platform, MSPs manage their clients, reseller partners get their own scoped views, venue admins manage their location. Strict data isolation between tenants.

Business outcomes

Run hundreds of venues from one MSP account
Each tenant sees only their own data
White-label per MSP, co-branded per reseller
Per-tenant quotas prevent runaway costs

Capabilities

What's inside.

Four-tier hierarchy

Super → MSP → Reseller → Venue with inherited permissions.

Strict tenant isolation

Row-level + tenant ID enforcement — no cross-tenant data leaks.

Per-tenant package limits

Cap sessions, venues, sends, vouchers per tenant.

White-label per MSP

Each MSP gets their own brand surface.

Bulk venue provisioning

Onboard 50 client venues with a CSV upload.

How it works

3 steps from connect to deliver.

You provision an MSP

Super admin creates the MSP account and quota.

MSP invites clients

MSP onboards venues with email invites or CSV upload.

Roles enforce scope

Every dashboard view, API call, and audit log is tenant-scoped.

Pairs with

Features that work together with MSP Multi-Tenant Management.

See all 18 features