qdrant-multitenancy

# Qdrant Multitenancy [Multitenancy](https://skills.qdrant.tech/md/documentation/manage-data/multitenancy/) is how you isolate data across multiple users or tenants within a single Qdrant deployment. - The question to ask is: **how many tenants, and how unevenly sized are they?** That answer picks the isolation strategy. - Understand the three isolation levels before choosing: payload-based, shard-based and collection-based. - For almost everyone the right default is a single collection partitioned by payload, NOT a collection per tenant. ## Many Small Tenants (Default: Payload Partitioning) Use when: you have many tenants of roughly similar, modest size. This is the recommended default for most users. One collection holds every tenant. A payload field marks ownership, and a filter on that field at query time is what isolates each tenant's results. ### How It Works - Create a keyword payload index on the tenant field with `is_tenant=true` (the flag requires v1.11+). `is_tenant` tells Qdrant the field identifies tenants, so each tenant's vectors are stored together and served by sequential reads. Check [](https://api.qdrant.tech/api-reference/indexes/create-field-index). - At query time, isolate each tenant with a `must` filter on the tenant field. Without it, a query searches every tenant's data. Check [Payload-based multitenancy](https://skills.qdrant.tech/md/documentation/manage-data/multitenancy/?s=partition-by-payload). - With this strategy, the indexing speed migh...