multi-tenant-accounts

rbarazi's avatarfrom rbarazi

Implement multi-tenant architecture using an Account model as the tenant boundary. Use when building SaaS applications, team-based apps, or any system where data must be isolated between organizations/accounts.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 7, 2026
[Architecture Design]

When & Why to Use This Skill

This Claude skill provides a comprehensive blueprint for implementing multi-tenant architecture in Rails applications using an Account-based model. It focuses on ensuring strict data isolation between organizations, offering a secure and scalable foundation for building SaaS platforms, team-based tools, and enterprise systems where data privacy is paramount.

Use Cases

  • SaaS Platform Development: Building multi-user software-as-a-service applications where multiple companies share the same infrastructure while maintaining complete data separation.
  • Team-Based Collaboration Tools: Developing applications where resources like projects, documents, and tasks must be strictly scoped to specific organizational accounts or departments.
  • Security-Critical Data Isolation: Implementing robust request-scoped access patterns to prevent cross-tenant data leaks and ensure that users can only access records belonging to their specific account.
namemulti-tenant-accounts
descriptionImplement multi-tenant architecture using an Account model as the tenant boundary. Use when building SaaS applications, team-based apps, or any system where data must be isolated between organizations/accounts.

Multi-Tenant Account Pattern

Account-based multi-tenancy for Rails applications. All resources scoped to accounts for data isolation.

Quick Start

  1. Create Account model as the tenant container
  2. Add belongs_to :account to User model
  3. Configure Current model to delegate account from session
  4. Scope all resources via Current.account

Core Architecture

Account (tenant boundary)
  └── Users (belong to account)
  └── All resources (scoped to account)

Current.session → Current.user → Current.account

Components

Component Purpose Reference
Account model Tenant container models.md
User-Account relationship User scoping models.md
Current model Request-scoped access models.md
Controller scoping Safe queries controllers.md
Database migrations Schema design migrations.md
Testing patterns Isolation tests testing.md

Minimal Implementation

Account Model

class Account < ApplicationRecord
  has_many :users, dependent: :destroy
  has_many :agents, dependent: :destroy  # Example resource

  validates :name, presence: true, uniqueness: true
end

User-Account Association

class User < ApplicationRecord
  belongs_to :account
  has_secure_password
end

Current Model

class Current < ActiveSupport::CurrentAttributes
  attribute :session
  delegate :user, to: :session, allow_nil: true
  delegate :account, to: :user, allow_nil: true
end

Controller Scoping

class AgentsController < ApplicationController
  def index
    @agents = Current.account.agents  # Always scope to account
  end

  def show
    @agent = Current.account.agents.find(params[:id])  # Security critical!
  end
end

Critical Security Pattern

# CORRECT - scoped to account
@agent = Current.account.agents.find(params[:id])

# WRONG - exposes all accounts' data!
@agent = Agent.find(params[:id])  # SECURITY VULNERABILITY

Account Access Pattern

# Anywhere in your application:
Current.account        # => #<Account id: "abc-123">
Current.user           # => #<User id: "xyz-456">
Current.account.agents # => [Agent, Agent, ...]
Current.account.users  # => [User, User, ...]

Detailed References