Skip to main content

Multi-Tenancy Architecture

Understanding how Organization scoping works in the Hedges VIP platform.

Overview​

Multi-tenancy allows multiple independent Organizations to use the same platform while keeping their data completely separate.

Vocabulary note​

The user-facing entity is Organization. The database column is still tenantId for backwards compatibility, but every UI label, page heading, and user-facing surface uses "Organization". The architectural pattern is still commonly referred to as "multi-tenancy" in engineering contexts.

Key Concepts​

Organization: The top-level entity representing a single account on the platform — e.g., a hospitality group with one or more venues.

Organization Scoping: All data is automatically filtered by Organization — users can only see data from their own Organization.

Cross-Organization Access: Only Platform Admin can access multiple Organizations using the Organization selector.

How It Works​

Backend Enforcement:

  • All API requests include Organization context
  • TenantGuard middleware (legacy code name) enforces scoping
  • No way for users to access other Organizations' data

Location Scoping:

  • Location Admin users see only their assigned locations
  • Org Admin sees all locations in their Organization
  • Member visibility based on location visit history