Access management in Yandex Cloud Apps

Yandex Cloud users can only perform operations on resources within the permissions of the roles assigned to them. With no roles assigned, almost no operations are allowed.

To grant access to Cloud Apps resources, assign the relevant roles from the list below to a Yandex account, service account, federated or local users, user group, system group, or public group. Currently, a role can only be assigned for a parent resource, i.e., folder or cloud, whose roles are inherited by nested resources.

For more information about role inheritance, see Inheritance of access permissions in the Resource Manager documentation.

Roles this service hasRoles this service has

In Cloud Apps, you can manage access using both service and primitive roles.

Service rolesService roles

cloudapps.auditorcloudapps.auditor

The cloudapps.auditor role enables viewing the metadata of installed Cloud Apps.

cloudapps.viewercloudapps.viewer

The cloudapps.viewer role enables viewing info on installed Cloud Apps.

This role includes the cloudapps.auditor permissions.

cloudapps.editorcloudapps.editor

The cloudapps.editor role enables viewing info on installed Cloud Apps, as well as creating, modifying, and deleting them.

This role includes the cloudapps.viewer permissions.

cloudapps.admincloudapps.admin

The cloudapps.admin role enables viewing info on installed Cloud Apps, as well as creating, modifying, and deleting them.

This role includes the cloudapps.editor permissions.

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 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 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 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 on primitive roles, see the Yandex Cloud role reference.

See alsoSee also

Hierarchy of Yandex Cloud resources