huagetai opened a new issue #9152: URL: https://github.com/apache/dolphinscheduler/issues/9152
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description Shouldn't all operations related to user authorization be restricted to the same tenant? For example: project authorization, alarm group authorization, resource authorization, etc. The current design can authorize users across multiple tenants.Tenants are effectively replaced by users. ### Use case Isolation of projects, resources, data sources, work groups, etc. through tenants ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
