Access management

Yandex.Cloud users can only perform operations on resources that are allowed by the roles assigned to them. If a user doesn't have any roles assigned, almost all operations are forbidden.

To allow access to resources of the Container Registry service (registries and Docker images), assign applicable roles to the user from the list below. For now, a role can only be assigned to a parent resource (folder or cloud), whose roles are inherited by nested resources.


For more information about role inheritance, see Access rights inheritance in the Yandex Resource Manager documentation.

Assigning roles

To assign a role to a user:

  1. Open the Access management page for the selected cloud. If necessary, switch to another cloud.

  2. Select the user to assign the role to, click image, and choose Configure roles.

  3. To add a cloud role, click image in the Roles for cloud section.

    To add a folder role, select the folder and click Assign role in the Roles in folders section.

  4. Choose a role from the list.


The list below shows all roles that are considered when verifying access rights in the Container Registry service.

Service roles

Service roles are roles that allow access to the resources of a particular service.


When a new user is added to the cloud, they are automatically assigned the role of cloud member: resource-manager.clouds.member.

This role must be assigned to everyone who needs to access cloud resources, except the owners of the cloud, service accounts, and system group allAuthenticatedUsers.

This role alone does not give you the right to perform any operations and is only used in combination with other roles, such as admin, editor, or viewer.


To enable a user to work in the cloud through the management console, assign them the resource-manager.clouds.member and viewer roles for the cloud. If you assign only the cloud member role for the cloud and other roles for the nested resources, the user will only be able to perform resource operations using the API or CLI.


The role of resource-manager.clouds.owner is assigned for the cloud and makes the user the owner of the cloud. The owner can perform any operation with the cloud and its resources.

Only the cloud owner can assign users the resource-manager.clouds.owner role or remove it from them.

A cloud must have at least one owner. The sole owner of a cloud may not give up this role.

Primitive roles

You can assign primitive roles to any resource in any service.


A user with the viewer role can view information about resources, for example, view a list of registries or pull a Docker image.


A user with the editor role can manage Docker images, for example, push or delete them.

In addition, the editor role includes all permissions of the viewer role.


A user with the admin role can manage access rights to resources, for example, allow other users to view registries or work with Docker images.

In addition, the admin role includes all permissions of the role of editor.