Skip to main content

VMO Roles

PaletteAI VM Launchpad ships with four built-in VMO IAM roles: Platform Admin, Editor, Operator, and Viewer. Each role is a named bundle of permissions that controls what a user can view and do in the platform UI. Roles are read-only in this release. Use them to assign VMO access to users on the Users page or to groups on the Groups page.

Prerequisites​

  • A cluster created using VM Launchpad. Refer to Install VM Launchpad for guidance.

  • An account with the Platform Admin VMO role, or membership in a group mapped to Platform Admin.

VMO Roles Page​

From the left main menu, select Settings > Access Management > VMO Roles to view all built-in roles in the appliance.

The VMO Roles table lists the following columns.

ColumnDescription
NameThe role name.
DescriptionA short summary of the role's intent.
(unlabeled)Displays Default for built-in roles that ship with VM Launchpad.

Select a column header to sort. Use the Filter rows search box to filter by any field.

Built-in Roles​

The following table lists each built-in role, the description shown on the VMO Roles page, and a summary of the role's permissions.

RoleDescriptionSummary of permissions
Platform AdminFull platform control. All VMO permissions.All permissions across all namespaces.
EditorVM workflow and operational tooling. Templates, dashboards, packages.Full VM lifecycle (create, read, update, delete, operate, and snapshot), Image Catalog (read and write, including golden image upload, delete, and build), templates (read and write), instance types and preferences (read only), dashboards (read), audit, system and monitoring (read), CRD catalog (read), and Infrastructure (read only, required for the VM creation wizard's NAD, StorageClass, and namespace pickers). No Settings access. No Infrastructure write. No platform-content curation. No create, edit, or delete of instance types or preferences.
OperatorDay-to-day operations. Own dashboards, read audit and system.VMs (read, operate, and snapshot), templates (read), dashboards (read), audit, and system and monitoring (read). No Image Catalog. No Infrastructure (network, storage, or namespace). No Settings access.
ViewerRead-only with own dashboard config.VMs (read only), templates (read), dashboards (read), audit, and system and monitoring (read). No Image Catalog. No Infrastructure. No Settings. No operate or snapshot actions. No writes anywhere.

You cannot create a custom role or modify a built-in role in this release. Both the UI and the API reject these operations.

Each VMO role also binds a fixed Kubernetes ClusterRole that grants the underlying access to the KubeVirt API. VM Launchpad selects the matching ClusterRole automatically when you assign a role to a user or group.

VMO RoleKubernetes ClusterRole
Platform Adminspectro-vm-admin
Editorspectro-vm-power-user
Operatorspectro-vm-user
Viewerspectro-vm-viewer

Local users are an exception. A local user receives the VMO role without a matching ClusterRole binding, because local authentication reaches the Kubernetes API through the VMO Manager pod's ServiceAccount instead of a per-user binding.

Permission Format​

Every VMO permission follows the format vmo:<domain>:<action>.

PartDescription
vmoStatic prefix identifying the permission as a VMO IAM permission.
domainThe functional area the permission controls, such as config, storage, or network.
actionThe operation the permission grants. Most domains use read and write. Others define granular or domain-specific actions. Refer to Permission Actions.

For example, vmo:packages:write grants write access to the package repository, and vmo:audit:read grants read access to the audit log.

Permission Actions​

Most domains use read and write. The following table describes every other action and the domains that define it.

ActionDomainsDescription
create, read, update, deletenamespace, network, vmGranular access to create, read, update, and delete individual resources in the domain. These three domains do not define a write action.
operatevmStart, stop, restart, migrate, and open the console of a VM.
snapshotvmCreate, restore, and manage VM snapshots.
export, importconfig-bundleExport and import configuration bundles. This domain does not define read or write.
manage-manifestsdashboardsCreate, list, and delete dashboard manifests.
configuremonitoringChange the monitoring configuration.
device-discoverystorageDiscover devices available on cluster nodes.

Only the Platform Admin role includes the configure and device-discovery actions. No procedure in this section depends on either one.

Three domains define a single action. The audit domain defines only read, and the branding and instancetypes domains define only write.

Permission Domains​

The following table lists every VMO permission domain and the actions each domain defines.

DomainActionsDescription
vmcreate, read, update, delete, operate, snapshotVirtual machines, including lifecycle, console access, and snapshots.
configread, writePlatform configuration, including environment variables.
config-bundleexport, importExport and import configuration bundles.
brandingwriteBranding assets (logo, colors).
certificatesread, writeTLS certificates.
packagesread, writePackage repository. Golden image DataVolume operations (upload, delete, build) also use this domain.
templatesread, writeVM templates.
instancetypeswriteCluster-scoped instance types and preferences (Platform Admin only). Viewing them requires vmo:vm:read.
dashboardsread, manage-manifestsDashboards and metrics.
local-usersread, writeLocal authentication accounts.
api-keysread, writeAPI key creation and revocation. Refer to API Keys.
iamread, writeIAM roles, group mappings, and access policies.
auditreadAudit log.
systemread, writeSystem health and platform information.
crd-catalogread, writeCRD catalog.
monitoringread, configureMonitoring configuration.
storageread, write, device-discoveryStorageClasses, StoragePools, DataVolumes other than golden images, HA settings, and system storage resize.
networkcreate, read, update, deleteNetwork Attachment Definition (NAD) resources and network capabilities.
namespacecreate, read, update, deleteNamespaces and namespace policies.
rolesread, writeBuilt-in VMO role definitions. Roles are immutable in this release.
featuresread, writeFeature flags.
kubevirtread, writeCluster-level KubeVirt configuration.
admissionread, writeAdmission control policies.
info

The KubeVirt Configuration page in the UI is additionally gated on cluster-admin privileges and OIDC authentication. A user who holds only the kubevirt domain permissions cannot open the page.

Built-in Role Maintenance​

VM Launchpad maintains the definitions of the four built-in roles, so you do not need to take any action to keep them current. Their permission sets belong to the release rather than to your installation, which means an upgrade can change what a built-in role grants.

After an upgrade, review the Built-in Roles table for the version you run and confirm that each role still matches the access you intend to grant.

Next Steps​

  • Assign a VMO role to a user. Refer to Users.

  • Assign a VMO role to a group. Refer to Groups.

  • View existing role mappings and Kubernetes bindings. Refer to Access Mapping.