Security Groups

In this article

    Veeam ONE creates the following security groups on the machines where Veeam ONE Server and Veeam ONE Web Services components are installed:

    • Veeam ONE Administrators: members of this group can access monitoring data, generate reports and modify all Veeam ONE configuration settings.

    This group must include the Veeam ONE service account.

    • Veeam ONE Power Users: members of this group have read access to monitoring data and can generate reports but do not have access to Veeam ONE configuration settings.
    • Veeam ONE Read-Only Users: members of this group can generate reports and access monitoring data in read-only mode, but cannot modify any Veeam ONE configuration settings.

    You can access and manage security groups in the Computer Management console.

    Security Groups

    To provide access to Veeam ONE functionality for an administrator or operator, you must include this user either in the Veeam ONE Administrators, Veeam ONE Read-Only Users  or Veeam ONE Power Users group. Member of these groups have access to:

    • All Veeam ONE consoles (Client and Web Client)
    • All objects of the infrastructure inventory (including VMware vSphere, VMware vCloud Director and Microsoft Hyper-V)

    Multi-Tenant Monitoring and Reporting

    Veeam ONE supports multi-user access to its monitoring and reporting capabilities. Authorized users can concurrently access the same instance of Veeam ONE to monitor the health state of the virtual infrastructure and create reports.

    To restrict access to sensitive infrastructure data, you can limit the scope of virtual infrastructure objects and associated data that must be available to a Veeam ONE user. Thus you can control what subset of the managed virtual infrastructure the user can see and work with. In multi-tenant environments, you can configure restricted access to Veeam ONE for owners of virtualized systems or responsible personnel and delegate monitoring and reporting tasks.

    Note:

    Do not use security groups to enable for users possibilities of self-service monitoring and reporting on a restricted scope of the virtual infrastructure. Instead, configure permissions for multi-tenant access. For details, see Veeam ONE Multi-Tenant Monitoring and Reporting.

    I want to report a typo

    There is a misspelling right here:

     

    I want to let the Veeam Documentation Team know about that.