-
Notifications
You must be signed in to change notification settings - Fork 273
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
[Self] Force automatic sharing #3948
Comments
Maybe add an option in the Self Service to either:
|
Let's keep in mind that a VM is being shared during the creation and that new users/groups added in the self service afterward will not have access to this VM. |
About your suggestion I agree it would be nice to be able to set this for the whole self service, maybe simply the ability to set the |
This could be a thing but the main idea was to prevent Self users from creating non shared VMs. |
I don't think so, as I understand it, the user simply do not want to rely on the users explicitly sharing their VMs. |
Hi i put this support tick in, i new to Xen Orchestra( think it's a great product) but if you could create a ACL that give you the ability to choose the "Resource set name" as a object in the rule. I guess this would achieve what i was trying to do. |
Hi @MattM3542! So you'd want to assign ACLs for resource sets, is that correct? Could you tell us why you'd want to do that? Also, if it's not related to this issue, please open a new one :) |
Fixed by #6838 |
See support#1251
Related to #3908
The text was updated successfully, but these errors were encountered: