multi-tenant

What problem does it solve?

This Skill provides built-in multi-tenant data isolation for document storage and search by enforcing owner_id across all operations, ensuring tenants cannot access each other's data.

Core Features & Use Cases

• Automatic owner_id filtering for all document operations (add, list, search, delete)
• Optional schema-per-tenant or single-database tenancy to meet regulatory or scaling needs
• Hierarchical tenancy support (organization → workspace → user) with full isolation guarantees
• Practical guidance for secure multi-tenant patterns in SaaS apps, including auditability and export/delete workflows
• Use Case: A SaaS app serving multiple organizations can store each organization's documents under its owner_id and safely query within the same tenant without cross-tenant leakage.

Quick Start

Install llmemory and initialize a shared pool. Create a memory instance scoped to a tenant using owner_id, then add a document and perform a tenant-scoped search to verify isolation.