How I Designed a Multi-Organization System for my sass

Rajwinder singh — Tue, 19 May 2026 19:21:30 +0000

In this blog , I will explain how I designed a multi-organization architecture for my ticket management system and the challenges I faced while implementing secure tenant isolation.

The Situation

I was building a ticket management system where teams could collaborate on issues, assign tickets, and manage workflows.

Initially, the application supported only a single workspace, but later I realized that real-world teams usually work inside organizations similar to GitHub, Supabase, or Jira.

So I decided to redesign the architecture in a way where:

A user can create multiple organizations
Organizations can have multiple members
Each organization has isolated tickets and resources
Users can switch between organizations
Roles and permissions can be managed independent

The goal was to build a reusable multi-tenant foundation that could scale later.

Understanding Multi-Tenancy

Before implementing the system, I first needed to understand what multi-tenancy actually means.

A multi-tenant application is a system where:

Multiple organizations share the same backend infrastructure
But their data remains logically isolated

This means:

Organization A cannot access Organization B data
even though both use the same database and server.

Choosing architecture

There are multiple ways to multi-tenancy , after some research i found 3 different Approch

Separate Database per tenant: In this structure each organization have its own database which provide strict isolation and excellent scale but very complex , this architecture is used by enterprise SasS, banking system, when Physical isolation is required
Separate Schemas per tenant : It bit complex but provide good isolation
Shard DB with tenantId: It is Easy to implement and less time consuming

For my system , I Choosing

Shared Database + organizationId based on isolation

Because:-

easier to scale Initially
lower infrastructure cost
faster development
Easy migration
Simpler to deploy

Note:-Main trade off is enforcing organization-level filtering which need proper indexing

Database Schemas

First step is to design Schema as shown

model User {
  id                String             @id @default(uuid()) @db.Uuid
  code              String             @unique
  email             String             @unique
  createdAt         DateTime           @default(now())
}

model Organization {
  id                String             @id @default(uuid()) @db.Uuid
  name              String
  createdAt         DateTime           @default(now())
  createdBy         String             @db.Uuid
}

model Membership {
  id             String        @id @default(uuid()) @db.Uuid
  organizationId String        @db.Uuid
  userId         String        @db.Uuid
  roleId         String        @db.Uuid
  createdAt      DateTime      @default(now())
  isSystem       Boolean       @default(false)

}

model Role {
  id             String        @id @default(uuid()) @db.Uuid
  code           String        @unique
  name           String
  permissions    Json
  createdBy      String        @db.Uuid
  organizationId String        @db.Uuid
  isSystem       Boolean       @default(false)
}

The Membership table become core abstraction because it allowed:

One user to join multiple Organization
Different Roles per organization
Easy invitation system or transfer organization
RBAC support

Organization Creation Flow

When a user creates a new organization, the system automatically performs multiple operations behind the scenes.

The goal was to ensure that every organization always has:

a valid owner
at least one role
a membership relationship
protected authorization rules

The creation flow looks like this:

User Creates Organization
        |
        v
Create Organization Row
        |
        v
Create Hidden "Owner" Role
        |
        v
Create Membership Record
        |
        v
Assign User to "Owner" Role

Request Cycle

Every request in the system flow through this lifecycle:

Request
   |
   v
Authentication Middleware
   |
   v
Tenant Middleware
   |
   v
Validate Membership
   |
   v
Attach Tenant Context
   |
   v
Execute Scoped Database Queries
   |
   v
Response

here it follow following steps

Every request enters the system with the x-organization-id header attached. This header identifies which organization the user is currently operating in.
The authentication middleware verifies the user and attaches user details to the request object.

req.user = {
  ...req.user,
  id: userdata?.id,
};

The tenant middleware identifies the organization from the request headers and determines what permissions the user has within that specific organization.

The middleware attaches organization details to the request object:

req.organization = {
  ...req.organization,
  isOwner: member?.role?.name === "OWNER",
  id: organizationId,
};

Any controller can now directly access the organization ID and organization-related metadata from req.organization.

By applying this approach, there is no need to send the organization ID in every route, such as:

/api/v1/:orgId/xyz

The active organization is decided by the frontend and passed through the x-organization-id header, resulting in cleaner and more maintainable APIs.

Isolation Strategy

The main challenge in multi-tenancy is isolating each organization's data without leaking information across tenants. Since the database schema is shared among multiple tenants, the safest and most reliable approach is to always filter records by organizationId during every CRUD operation.

Example:

const data = await prisma.ticket.findMany({
  where: {
    organizationId: req.organization.id,
  },
});

By enforcing organization-level filtering consistently across all database operations, the application maintains strong tenant isolation while still using a shared database schema.

Multi-tenant architectures offer great scalability, but they essentially put all your customers' eggs in one basket. If the "walls" between those eggs aren't reinforced at the code level, a single leak can become a catastrophic breach.

In Addition of batter Security we need to implement Row Level Security to minimize risk of data leak between tenant

Security Challenges in Multi-Tenant Systems

In a multi-tenant environment, security revolves around Tenant Isolation (keeping data separate) and Access Control (ensuring users only do what they are permitted to do).

1. Tenant Data Leakage (The "Missing Filter" Problem)

This is the most frequent and severe risk. Because multiple tenants share the same database tables, a single forgotten WHERE clause in a query can expose sensitive data to the wrong organization.

The Risk: An API endpoint like /api/customers might accidentally return all customers in the database instead of just those belonging to the requester's organization_id.
The Fix: Implement Row-Level Security (RLS) at the database level or use Global Query Filters in your ORM (Object-Relational Mapper) to automatically inject the tenant_id into every query.

2. Horizontal Privilege Escalation

This occurs when a user from Tenant A attempts to access resources belonging to Tenant B.

The Scenario: A user changes a URL from tickets/123 (their own) to tickets/124 (another tenant's).
The Fix: Never rely on the resource ID alone. Your backend logic must perform a "Double-Check":

Does ticket 124 exist?
Does ticket 124 belong to the organization_id associated with the current user’s session?

3. Organization ID Spoofing

Attackers often try to manipulate request headers, cookies, or JWT payloads to "masquerade" as a different organization.

The Risk: Trusting an X-Org-ID header sent by the frontend without server-side verification.
The Fix: Never trust the frontend context.
Store the organization_id inside a secure, server-signed JWT.
On every request, cross-verify that the user is a valid member of the organization they are claiming to represent.

4. Vulnerabilities in the Invitation System

The "Invite User" flow is a common entry point for attackers to bypass standard registration security.

Vulnerability	Impact	Mitigation Practice
Expired Invites	Unauthorized access via old links.	Use strict `exp` (expiration) timestamps.
Reused Tokens	Multi-use of a single-use link.	Implement "One-Time-Use" flags in the DB.
Predictable Codes	Attackers can "guess" invite URLs.	Use high-entropy UUIDs or cryptographically secure strings.
Role Escalation	Invitee changes their role to 'Admin' in transit.	Sign the role inside the token or re-validate roles on the backend.

Final Thoughts

At first, implementing organizations looked simple.

I thought adding an organizationId field would be enough to support multi-tenancy, but while building the system I realized tenant isolation affects almost every part of the architecture.

Things like:

authorization
database queries
file uploads
caching
background jobs
role management

all become organization-aware.

The lesson I learned was that multi-tenancy is not just a database design pattern. It is a system-wide architectural decision.

Building this system gave me a much deeper understanding of how SaaS applications structure teams, permissions, and tenant boundaries internally.

If you've solved this differently or noticed any issues with this approach, I'd like to hear your thoughts. I'm still refining how I structure these systems.

DEV Community: Rajwinder singh