Access management in Yandex Cloud Desktop

Cloud Desktop leverages Yandex Identity and Access Management roles and access control lists (ACLs) to manage access. This example shows how access management works in Cloud Desktop.

In this section, you will learn:

• What resources you can assign a role for.
• What roles exist in the service.

Access managementAccess management

Yandex Identity and Access Management checks all operations in Yandex Cloud. If an entity does not have required permissions, this service returns an error.

To grant permissions for a resource, assign the appropriate resource roles to an entity performing operations, such as a Yandex account, service account, federated users, user group, system group, or public group. For more information, see How access management works in Yandex Cloud.

Resources you can assign a role forResources you can assign a role for

You can assign a role to an organization, cloud, or folder. The roles assigned to organizations, clouds, and folders also apply to their nested resources.

You can assign a role for a desktop group via the management console, Yandex Cloud CLI, or API.

Roles existing in this serviceRoles existing in this service

Service rolesService roles

vdi.viewervdi.viewer

The vdi.viewer role allows using desktops and viewing information on desktops and desktop groups.

Users with this role can:

• View information on desktop groups and access permissions granted for such groups.
• View information on desktops and use them.
• View information on Cloud Desktop quotas.

vdi.editorvdi.editor

The vdi.editor role allows managing desktop groups and desktops as well as using desktops.

Users with this role can:

• View information on desktop groups, create, update, and delete desktop groups.
• View information on access permissions granted for desktop groups.
• View information on desktops and use them.
• Create, update, start, restart, stop, and delete desktops.
• View information on Cloud Desktop quotas.

The role also includes the vdi.viewer permissions.

vdi.adminvdi.admin

The vdi.admin role allows managing desktop groups and access to them, as well as managing and using desktops.

Users with this role can:

• View information on and update access permissions granted for desktop groups.
• View information on desktop groups, create, update, and delete desktop groups.
• View information on desktops and use them.
• Create, update, start, restart, stop, and delete desktops.
• View information on Cloud Desktop quotas.
• View info on the relevant folder.

The role also includes the vdi.editor permissions.

For more information about service roles, see Roles in the Yandex Identity and Access Management documentation.

Primitive rolesPrimitive roles

Primitive roles allow users to perform actions in all Yandex Cloud services.

auditorauditor

The auditor role grants a permission to read configuration and metadata of any Yandex Cloud resources without any access to data.

For instance, users with this role can:

• View info on a resource.
• View the resource metadata.
• View the list of operations with a resource.

auditor is the most secure role that does not grant any access to the service data. This role suits the users who need minimum access to the Yandex Cloud resources.

viewerviewer

The viewer role grants the permissions to read the info on any Yandex Cloud resources.

This role also includes the auditor permissions.

Unlike auditor, the viewer role provides access to service data in read mode.

editoreditor

The editor role provides permissions to manage any Yandex Cloud resources, except for assigning roles to other users, transferring organization ownership, removing an organization, and deleting Key Management Service encryption keys.

For instance, users with this role can create, modify, and delete resources.

This role also includes the viewer permissions.

adminadmin

The admin role enables assigning any roles, except for resource-manager.clouds.owner and organization-manager.organizations.owner, and provides permissions to manage any Yandex Cloud resources (except for transferring organization ownership and removing an organization).

Prior to assigning the admin role for an organization, cloud, or billing account, make sure to check out the information on protecting privileged accounts.

This role also includes the editor permissions.

Instead of primitive roles, we recommend using service roles with more granular access control, allowing you to implement the least privilege principle.

For more information about primitive roles, see the Yandex Cloud role reference.

What's nextWhat's next

• How to assign a role.
• How to revoke a role.
• Learn more about access management in Yandex Cloud.
• Learn more about inheriting roles.