nazim-multi-tenancy

Enforce organization and school data isolation with Row Level Security policies.

Updated Nov 15, 2025
One-click install
npx skills add https://github.com/AHMADJAN-New/nazim-web --skill nazim-multi-tenancy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nazim-multi-tenancy
Source: https://github.com/AHMADJAN-New/nazim-web/tree/main/.cursor/skills/nazim-multi-tenancy
Command: npx skills add https://github.com/AHMADJAN-New/nazim-web --skill nazim-multi-tenancy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures strict data isolation between different organizations and schools within the Nazim multi-tenant SaaS application, preventing data leakage and maintaining security.

Core Features & Use Cases

  • Data Scoping: Enforces organization_id and school_id constraints on all tenant data.
  • Frontend & Backend Consistency: Provides patterns for consistent data handling across the application stack.
  • Use Case: When developing a new feature that involves student records, use this Skill's guidelines to ensure that a user from Organization A cannot access or modify data belonging to Organization B.

Quick Start

Use the nazim-multi-tenancy skill to ensure all new database tables include organization and school ID columns.

Frequently Asked Questions about nazim-multi-tenancy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce multi-tenancy data isolation in a SaaS application?

Multi-tenancy data isolation in a SaaS application is enforced by applying organization_id and school_id constraints across database schemas, API calls, and backend controllers to prevent cross-tenant data leakage. Row Level Security policies ensure strict data segregation.

How do I implement Row Level Security policies for multi-tenant databases?

Row Level Security policies for multi-tenant databases are implemented by enforcing organization_id and school_id constraints on tenant data tables. Backend helper functions like getCurrentSchoolId() provide the required context to scope database queries securely.

What is the best way to keep frontend query keys consistent with backend tenant isolation?

Keeping frontend query keys consistent with backend tenant isolation requires applying organization_id and school_id scoping patterns across the application stack. This ensures frontend data handling mirrors backend controller constraints for strict multi-tenant data segregation.

How do I prevent data leakage between organizations in a multi-tenant SaaS architecture?

Preventing data leakage between organizations in a multi-tenant SaaS architecture requires strict data scoping using organization_id and school_id columns. Implementing Row Level Security policies and backend helper functions blocks cross-tenant data access.

Do I need organization_id and school_id columns on every database table for SaaS tenant isolation?

Yes, organization_id and school_id columns are required on all new database tables to enforce SaaS tenant isolation. Adding these columns ensures every data record is properly scoped and segregated by tenant to prevent unauthorized cross-organization access.