setting permission for users
- Thread starter Algon
- Start date
Objects and Paths
Access permissions are assinged to objects, such as a virtual machines (/vms/{vmid}) or a storage (/storage/{storeid}). We use filesystem like paths to address those objects. Those paths forms a natural tree, and permissions can be inherited down that hierachy.
from: http://pve.proxmox.com/wiki/User_Management#Objects_and_Paths
Access permissions are assinged to objects, such as a virtual machines (/vms/{vmid}) or a storage (/storage/{storeid}). We use filesystem like paths to address those objects. Those paths forms a natural tree, and permissions can be inherited down that hierachy.
from: http://pve.proxmox.com/wiki/User_Management#Objects_and_Paths
Are you referring to the path in the Permissions tab of datacenter?
If so, that is a way to restrict access to specific items in Proxmox.
Here is the documentation: http://pve.proxmox.com/wiki/User_Management#Objects_and_Paths
Basically a path of '/' means that user has access to everything tho read/write access is controlled via the roles.
You could also set a path like '/vms/101' and that permission would only have access to vm 101.
I think the documentation is incomplete.
It mentions /vms and /storage
There must be other paths.
Proxmox team, are the other paths documented somewhere?
If not, can you please update the wiki page with a complete list of paths?
If so, that is a way to restrict access to specific items in Proxmox.
Here is the documentation: http://pve.proxmox.com/wiki/User_Management#Objects_and_Paths
Basically a path of '/' means that user has access to everything tho read/write access is controlled via the roles.
You could also set a path like '/vms/101' and that permission would only have access to vm 101.
I think the documentation is incomplete.
It mentions /vms and /storage
There must be other paths.
Proxmox team, are the other paths documented somewhere?
If not, can you please update the wiki page with a complete list of paths?
I have some questions what I cannot figure out even I read that manual again and again.
1)
How I make permission what gives user right to add and migrate vm:s to only one node?
looks that /node/kvm9 does not work
2)
How I make permission what give user right to one local disk. Not for all local disks?
looks that /storage/kvm9/local does not work
3)
Is there any command what shows all valid paths? When documentation is very limited and web UI does not show path where you are I think some kind list command helps that you do not need use hours to trying guess what path give you wanted result.
-
Feature request:
permission path to web UI
Tweak request:
if storage type is ISO images then content tab can be visible on UI (naturally without menu).
1)
How I make permission what gives user right to add and migrate vm:s to only one node?
looks that /node/kvm9 does not work
2)
How I make permission what give user right to one local disk. Not for all local disks?
looks that /storage/kvm9/local does not work
3)
Is there any command what shows all valid paths? When documentation is very limited and web UI does not show path where you are I think some kind list command helps that you do not need use hours to trying guess what path give you wanted result.
-
Feature request:
permission path to web UI
Tweak request:
if storage type is ISO images then content tab can be visible on UI (naturally without menu).
