luganofer commented on issue #13975: URL: https://github.com/apache/cloudstack/issues/13975#issuecomment-5455519133
@DaanHoogland Thanks – accidental click while replying. Reopened now. About accounts without users – let me clarify. You're right that an empty account isn't practically useful, but the same could be said about a domain without an account, and CloudStack allows that purely for organizational hierarchy. So why not apply the same logic to accounts and users? The goal isn't to have empty accounts everywhere, but to **decouple the concepts** so users are added consciously and deliberately, avoiding confusion. That said, I'm not sure if this separation could affect other areas like SAML, LDAP, or external authentication integrations. That would need to be evaluated. The API can remain backward compatible – just make user fields optional – while the UI presents two clear workflows: "Create Account" and "Add User to Account". -- 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]
