New to configuration?See the Setup Configuration Overview for the complete workflow:install extras → create
.env
→ choose providers → handle pruning.Enable Multi-Tenant Mode
Multi-tenant mode is controlled by theENABLE_BACKEND_ACCESS_CONTROL
environment variable:
Database Override: When multi-tenant mode is enabled, Cognee automatically overrides your graph and vector store configurations to use Kùzu and LanceDB respectively, regardless of your custom settings.
Database Configuration
Multi-tenant mode enforces Kùzu (graph) and LanceDB (vector) stores. Choose your relational database:- SQLite — Perfect for local development and testing
- Postgres — Recommended for production deployments
Data Storage Layout
Data is automatically organized by user and dataset. See Multi-Tenant Architecture for details.Authentication Setup
Multi-tenant mode requires authentication:Start the API server:Authentication Methods:
- Bearer token (API clients)
- Cookie authentication (web frontend)
- Username:
default_user@example.com
- Password:
default_password
Permission System
Multi-tenant mode enforces dataset-level permissions. See Multi-Tenant Architecture for permission details.Troubleshooting
Permission Denied: Verify user has required permission on the dataset. Data Isolation Verification: Check database files exist per user:Current Limitations
- Supported databases: SQLite/Postgres (relational), LanceDB (vector), Kùzu (graph)
- Custom providers: Graph/vector database providers are locked to Kùzu/LanceDB when multi-tenant mode is enabled