-
Notifications
You must be signed in to change notification settings - Fork 3.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
Host administration access #2202
Comments
i think this is great idea |
this has been discussed in paid project repo. in fact it's not only the superadmin feature, but also shared Entities that should be seen by all tenants and stored in one shared database only. the team said they would implement it but never did. in fact, it is one of the reasons i stopped using the paid framework. |
Thanks for the feedback. So I guess the only solution at the moment is to implement this manually. |
This is only possible when different tenant share the same database. In my case, I create a middleware to disable multitenant datafilter when 'super admin' is detected.
You can write your own logic to determine when to disable this filter |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
When logged in as the default host admin (admin@abp.io, 1q2w3E*), I am not able to see tenant users. I.e., the
/api/identity/users
endpoint returns only users whose tenant ID is alsonull
, excluding users who indeed have a tenant ID.Should I be creating functionality for this myself, like creating repositories that disable the multi-tenancy filter based on the user's role? Or, what is the correct way to handle this?
Basically, I need a "super admin" role that can do CRUD on all entities for all tenants.
The text was updated successfully, but these errors were encountered: