multi-tenant-isolation

Enforce row-level security and tenant isolation across Myelin data access operations.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/Seth-arc/myelin-platform --skill multi-tenant-isolation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-tenant-isolation
Source: https://github.com/Seth-arc/myelin-platform/tree/main/primary_build_source/docs/skills/2/mnt/user-data/outputs/multi-tenant-isolation
Command: npx skills add https://github.com/Seth-arc/myelin-platform --skill multi-tenant-isolation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that data access within the Myelin platform strictly adheres to tenant boundaries, preventing unauthorized data leakage and enforcing security policies.

Core Features & Use Cases

  • Row-Level Security (RLS): Enforces tenant isolation at the database layer for all business records.
  • Tenant Context Propagation: Mandates that tenantId is always derived from the authenticated session and passed to all downstream calls.
  • Feature Flag Gating: Manages feature access based on tenant package tiers and explicit feature flag configurations.
  • Use Case: When developing any new API endpoint that accesses user data, this skill must be loaded to ensure that the code correctly implements tenant isolation through RLS and session-based tenantId extraction.

Quick Start

Load this skill before writing any data access or API code to ensure tenant isolation is correctly implemented.

Frequently Asked Questions about multi-tenant-isolation

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

FAQPage Schema
How do I enforce row-level security for multi-tenant data isolation in my API?

You implement multi-tenant data isolation by deriving tenantId from the authenticated session and applying row-level security policies to all database queries. This ensures API handlers and background jobs access only authorized tenant records.

What is tenant context propagation and when is it needed for multi-tenancy?

Tenant context propagation mandates that tenantId is always derived from the authenticated session and passed to all downstream calls. It is required when developing new API endpoints or background jobs to prevent cross-tenant data access.

How do I gate feature access based on tenant package tiers and configurations?

Gate feature access by implementing a feature-flag gating model driven by package entitlement tiers and tenant configurations. This manages feature availability across different tenants according to their subscribed package level and explicit settings.

Does row-level security apply to analytics pipelines and export functions?

Yes, row-level security applies to analytics pipelines and export functions. The multi-tenant isolation model governs all data access operations, ensuring cross-tenant prohibition rules are enforced across the entire platform.

What is the best way to prevent cross-tenant data leakage in background jobs?

The best way to prevent cross-tenant data leakage in background jobs is to mandate tenantId filters and enforce cross-tenant prohibition rules. This guarantees strict row-level security and tenant isolation across all background data operations.