We have a master organization that we manage all resources and sub-organization as well as their members. We associate master user with the master organization. We would like to build a multi-tenant system in which tenants can manage their own members.
When we log in to the sub-organization we create, we can see the master organization (in other words master user). Also, we can delete master user from the sub-organization among the members.After deleting the master user from the sub-organization, we log in to the master user account (master organization), we can see all of the resources (members, buckets etc.) under sub-organization.However, I would like to get to know that if there is a bug with the influxdb system. Normally, it is supposed to give warning or not accept the master to be deleted.If there is no mistake, I would like to go with these set-up and build my application according to that. Could you please help me?
Firstly it’s not clear which InfluxDB you’re using, multi-tenancy is supported in Serverless. For managing users etc please have a look here: Manage users in your InfluxDB Cloud organization | InfluxDB Cloud Serverless Documentation
1 Like
