-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to achieve multitenancy in superset using single instance #23306
Comments
I have similar use case, any advise how to handle? |
I too have similar usecase. |
Vote++ |
I guess it is more like feature request? |
Yes, when I first asked I assumed it was possible but it seems not. |
Any update on this? |
No update here, and I'd say it's not likely as a core feature. Closing this since it's not a bug, but a feature request. Typically, if people need multiple tenants, they spin up multiple instances (e.g. in Preset, we call these Workspaces). It is possible to do so, though non-trivial, and again not likely to be a Superset feature in the near future. If anyone is truly interested in implementing this, however, we'd be open to a SIP (Superset Improvement Proposal) and can provide more information on that process if needed. |
We can sponsor this achievement ( with certain conditions ). Please share the way forward. Thank you |
@busyboy77 this would be a large enough change that people will have myriad security concerns and want to thoroughly review/discuss any architectural/permissions changes. You can submit a SIP if you'd like to propose a technical approach for this. |
How do we have different database connections having separate metadatabase connections per tenant?
Example:-
Tenant-1: Database-1
Tenant-2: Database-2
If user login is of tenant-1
SQLALCHEMY_DATABASE_URI = 'postgresql+psycopg2:// dbusername:dbpassword@localhost/ Database-1'
else if user login is of tenant-2
SQLALCHEMY_DATABASE_URI = 'postgresql+psycopg2:// dbusername:dbpassword@localhost/ Database-2'
Therefore the user is login and belongs to whichever tenant SQLALCHEMY_DATABASE_URI database connection to be changed to according to that tenant
2.0.1
3.8.0
16.14.2
The text was updated successfully, but these errors were encountered: