Skip to content

Proxmox VE Permissions

cv4pve-admin connects to Proxmox VE through the API. The permissions it needs depend on the modules and features you use.


The simplest and recommended setup is to assign the built-in PVEAdmin role at path / to the Proxmox VE user or API token used by cv4pve-admin.

With this role every module has full functionality, with no further configuration.

Automatic API Token Creation: cv4pve-admin can create a dedicated Proxmox VE user and API token for you automatically. Learn more


If you prefer a least-privilege setup, assign a custom Proxmox VE role at path / with only the permissions required for the features you use.

These are the privileges of the built-in PVEAuditor role on Proxmox VE 9. Assigning that role is equivalent and simpler.

Privilege Purpose
Sys.Audit Cluster status, node info, tasks, firewall, HA
VM.Audit VM/CT list, status, config
VM.GuestAgent.Audit Information read through the QEMU Guest Agent (host name, IP addresses)
Datastore.Audit Storage list, status, content
Pool.Audit Resource pool list
SDN.Audit SDN zones, VNets, subnets
Mapping.Audit Resource mappings

This page describes Proxmox VE 9. Earlier releases use other privileges for some reads, for example VM.Monitor for the QEMU Guest Agent and the monitor: on those releases assign PVEAdmin, or check the privileges in the Proxmox VE documentation.

Before enabling an action on a VM/CT or on a node, cv4pve-admin reads the permissions of the Proxmox VE user or API token configured for the cluster. It then checks that the user or token holds the matching privilege. The privilege is accepted when it is granted on the object itself (/vms/<vmid> or /nodes/<node>), on /vms or /nodes, or on /. When it is missing, the button or tab is not available, even if the cv4pve-admin user has the application permission.

cv4pve-admin permission Proxmox VE privilege
VM: Audit VM.Audit
VM: Console VM.Console
VM: Power Management VM.PowerMgmt
VM: Snapshot manager VM.Snapshot
VM: Snapshot Rollback VM.Snapshot.Rollback
VM: Replication manager, Replication Schedule Now VM.Replicate
VM: Backup manager VM.Backup
VM: Backup Restore, Backup Restore File Datastore.AllocateSpace
VM: Migrate VM.Migrate
VM: Clone VM.Clone
VM: Resize disk VM.Config.Disk
VM: Convert to template VM.Allocate
VM: High Availability Sys.Console
Node: Audit Sys.Audit
Node: Console Sys.Console
Node: Power Management Sys.PowerMgmt
Node: Replication manager, Replication Schedule Now VM.Replicate
Storage: Delete Content Datastore.Allocate

The same checks apply in every module that offers these actions (Dashboard, Resources, Portal, Command Palette, AI Server, Workflow). In the web interface, migration and deletion of storage content are not available: they are used by AI Server tools and, for migration, by the Workflow activity. Clone, Resize disk, Convert to template and High Availability are used only by the Workflow activities, and among the built-in roles only Cluster.Admin (Cluster Admin User) includes them. A workflow runs its actions as the built-in system user.

What each module needs beyond the base. None means the base is enough. The page of each module says what each privilege is used for and what happens without it: click the name of the module.

ModuleBeyond the base
AI Server By tool: see the list
AutoSnapVM.Snapshot
Backup AnalyticsVM.Backup, Datastore.AllocateSpace
BotsVM.PowerMgmt, Sys.PowerMgmt
Command PaletteVM.PowerMgmt, VM.Console, VM.Snapshot
Dashboard By action: see Actions on guests and nodes
DiagnosticsSys.Modify, VM.Backup, Datastore.AllocateSpace
Metrics ExporterNone.
Node ProtectNone. It works over SSH.
Portal By action: see Actions on guests and nodes
Replication AnalyticsNone.
Resources By action: see Actions on guests and nodes
System ReportSys.Modify, Sys.Syslog, VM.Console, VM.Backup, Datastore.AllocateSpace, VM.Config.Disk
Update ManagerNone. It works over SSH.
UPS MonitorNone. It reads the UPS over SNMP.
VM PerformanceNone.
Workflow By activity: see the list

Proxmox VE lists a backup file only to an account that has both VM.Backup on the guest and Datastore.AllocateSpace on the storage. Without them the list of backups is empty, with no error. This is why Backup Analytics, the Backups tab of a guest, the backup checks of Diagnostics and the backup sections of System Report need these two privileges only to read.

Dashboard, Resources and Portal offer these actions. Each privilege is needed only for its action.

PrivilegeUsed for
VM.PowerMgmtStart, stop, shutdown, reboot, reset, suspend, resume a guest
VM.ConsoleGuest console
VM.SnapshotCreate, edit, delete a snapshot
VM.Snapshot.RollbackRoll back a snapshot
VM.ReplicateReplication: Schedule Now
VM.Backup, Datastore.AllocateSpaceBackups tab: list, configuration and deletion of backups
Sys.ConsoleNode console
Sys.PowerMgmtShut down, reboot a node

Example: monitoring + AutoSnap custom role

Section titled “Example: monitoring + AutoSnap custom role”
Sys.Audit
VM.Audit
VM.GuestAgent.Audit
VM.Snapshot
Datastore.Audit
Pool.Audit
SDN.Audit
Mapping.Audit

Assign the role at path / to the Proxmox VE user or API token used by cv4pve-admin.

On Proxmox VE 8 and earlier add Pool.Allocate if AutoSnap jobs select guests by pool.

A feature that lacks a required privilege shows errors or empty data. The other features keep working normally.