multitenancy-guard

Enforce tenant isolation and soft-delete guards in backend queries.

2|1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/genfeedai/genfeed.ai --skill multitenancy-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multitenancy-guard
Source: https://github.com/genfeedai/genfeed.ai/tree/main/.agents/skills/multitenancy-guard
Command: npx skills add https://github.com/genfeedai/genfeed.ai --skill multitenancy-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces tenant-scoped data guards and soft-delete rules in backend queries to prevent cross-tenant access and data leakage.

Core Features & Use Cases

  • Soft-delete guard enforcement: ensures isDeleted: false constraints are applied where required by existing patterns.
  • Tenant isolation enforcement: blocks cross-tenant reads/writes in enterprise ee/ code paths.
  • Organization guard checks: ensures organization guards are present for tenant-scoped queries in multi-tenant environments.
  • Use Case: When updating user data in apps/server, the guards ensure changes respect tenant boundaries and do not affect other tenants.

Quick Start

Audit recent backend data-access changes to verify tenant guards and soft-delete rules are applied consistently.

Frequently Asked Questions about multitenancy-guard

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

FAQPage Schema
How do I enforce tenant isolation in backend MongoDB queries?

Tenant isolation in backend MongoDB queries is enforced by injecting organization guards into every query, ensuring reads, updates, and deletes cannot cross tenant boundaries in multi-tenant environments.

What is the best way to enforce soft-delete rules in backend data access?

Soft-delete enforcement in backend data access is achieved by applying isDeleted: false constraints to queries, preventing application code from reading or modifying logically deleted records.

How do I prevent cross-tenant data leakage in enterprise code paths?

Cross-tenant data leakage is prevented by applying required organization guards and serialization checks to queries in ee/ paths, ensuring backend operations strictly respect tenant boundaries.

Does this multitenancy guard work with both enterprise and non-enterprise code?

Yes, tenant isolation and soft-delete enforcement apply to changes in apps/server/*, covering both ee/ and non-ee/ code paths to ensure consistent organization guards across the backend.

How do I audit backend data-access changes for tenant boundary violations?

Auditing backend data-access changes involves verifying that queries, reads, updates, and deletes include required organization guards and isDeleted constraints to prevent cross-tenant access and data leakage.