Enforces owner_id to isolate documents and search across tenants.
npx skills add https://github.com/juanre/llmemory --skill multi-tenant
Please help me install this Agent Skill. Skill: multi-tenant Source: https://github.com/juanre/llmemory/tree/main/skills/multi-tenant Command: npx skills add https://github.com/juanre/llmemory --skill multi-tenant
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.
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.
High-intent search queries and answers about installing and using this skill.
Tenant isolation for document storage is enforced by applying a deterministic owner_id filter across all add, list, search, and delete operations. This guarantees that tenants querying a shared PostgreSQL-backed layer cannot access each other's data.
Yes, multi-tenant data isolation supports hierarchical tenancy structures like organization, workspace, and user. It maintains full isolation guarantees by scoping all document and embedding operations to the specific hierarchical owner_id.
To isolate tenant data, initialize a shared pool with the llmemory library and a PostgreSQL storage layer. Create a memory instance scoped to a specific owner_id, then add documents and execute searches to verify deterministic tenant filtering.
The best way to prevent cross-tenant data leakage is enforcing automatic owner_id filtering on every query. You can also choose between schema-per-tenant or single-database tenancy models to meet specific regulatory or scaling requirements.
Single-database multi-tenant architectures rely entirely on deterministic owner_id filtering for security. While easier to manage, they may not satisfy strict regulatory isolation requirements compared to schema-per-tenant approaches, requiring careful auditability planning.
Yes, you can securely export and delete tenant documents by following the provided multi-tenant workflow patterns. These patterns ensure that export and delete operations remain strictly scoped to the correct tenant owner_id without data leakage.
PremModhaOfficialImplement tenant-scoped PostgreSQL CRUD with pgxpool and search_path.
burakdmirConfigure ABP Framework multi-tenancy with tenant resolution and data filtering.
BaraArdiwinataConfigures multi-tenancy in DaaS applications via the built-in scope management system.
zinohomeEnforce PostgreSQL Row Level Security policies for multi-tenant data isolation.
