--- title: "Overview" description: "This guide describes the permissions that the accounts used by Veeam Backup & Replication must have in a VMware vSphere environment." canonical: "https://helpcenter.veeam.com/docs/vbr/permissions/overview.html" breadcrumb: "Permissions for VMware vSphere > Overview" dateModified: "2026-11-19" --- # Overview This guide describes the permissions that the accounts used by Veeam Backup & Replication must have in a VMware vSphere environment. It helps you grant these accounts only the permissions that Veeam Backup & Replication needs for the operations you plan to perform, instead of assigning them full administrative rights. The guide covers the following: - Accounts and permissions required to install and use Veeam Backup & Replication. For details, see [Installation and Operation](installation.md). - Granular vCenter Server permissions required for particular operations, such as backup, replication, restore and migration. Each operation has its own section, for example, [Backup](backup.md) and [Replication](replication.md). - Cumulative vCenter Server permissions that cover all operations at once. For details, see [Cumulative Permissions](cumulativepermissions.md). ## Permission Level Assign the permissions at the vCenter Server level and propagate them to child objects. To do this, in VMware vSphere Client, add the account to the vCenter Server object with the required role and select the **Propagate to children** check box. Granular permissions required for an operation apply to different types of vCenter Server objects, for example, datastores, hosts, clusters, resource pools, folders and VMs. Depending on the operation, Veeam Backup & Replication works with some or all of them. The vCenter Server controls which objects are visible to the account, and Veeam Backup & Replication can work only with the objects that the account can access. When you assign the permissions at the vCenter Server level and propagate them, the account gets access to all objects in the inventory, including the objects that you add later. If you assign permissions on individual objects instead, for example, only on VMs or on a VM folder, make sure that the account also has the required permissions on all other objects involved in the operation. These objects include the parent objects of the VMs (datacenter, cluster and host) and the datastores where the VM files reside. Otherwise, the operation may fail because Veeam Backup & Replication cannot access some of the objects. ::: note Some permissions cannot be propagated from a lower level. For example, the permissions to create and edit tag categories can be granted only at the root level. For details, see [Cumulative Permissions](cumulativepermissions.md). :::