2
Multitenatcy support
Source: directus/directus#25869 · opened by @danny-mick
Summary 1. I want to be able to use directus as a SaaS 2. I want to allow refereing to collections between tenants is apossible if the ownning tenant approves that access to the requesting tenant Basic Example Multi-Tenant Setup: Tenant A: /a Tenant B: /b Tenant C: /c Each tenant has its own collections (e.g., products, orders). Cross-Tenant Reference Example: • Tenant B wants to reference Tenant A’s products collection. • Tenant A approves access → Tenant B sees Tenant A’s products as a read-only virtual collection. Motivation Directus is increasingly used by organizations as a backend for multiple clients or departments. However, there is currently no built-in multi-tenant architecture, which limits its ability to serve as a SaaS platform. Key motivations: 1. SaaS Multi-Tenancy: - Companies want to offer Directus as a service where each tenant has its own isolated workspace. - Avoids spinning up multiple Di…
No pledges yet. Be the first to back this.
Comments
Similar requests
http2 h2/c Support
24 votes · 0 comments
Support 'Features' from the GeoJSON spec to store address data in the Map Field
11 votes · 0 comments
MongoDB support (also with Atlas integration)
2 votes · 0 comments
Allow editing on the system fields
50 votes · 0 comments
MongoDB Database Support
45 votes · 0 comments
No comments yet.