Access management in Monitoring

Yandex Cloud users can only perform operations on resources in accordance with the roles assigned to them. Without assigned roles, a user cannot perform most operations.

To allow access to Yandex Monitoring resources, assign 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, such as a folder or cloud. Roles are inherited by nested resources.

To assign roles for a resource, you need to have one of the following roles for that resource:

• admin
• resource-manager.admin
• organization-manager.admin
• resource-manager.clouds.owner
• organization-manager.organizations.owner

Assigning rolesAssigning roles

To assign a role to a user:

1. Add the appropriate user, if required.
2. In the management console, on the left, select a cloud.
3. Navigate to the Access bindings tab.
4. Click Configure access.
5. In the window that opens, select User accounts.
6. Select a user from the list or use the user search option.
7. Click Add role and select a role for the cloud.
8. Click Save.

Roles this service hasRoles this service has

The list below shows all roles used for access control in Yandex Monitoring.

Service rolesService roles

monitoring.viewermonitoring.viewer

The monitoring.viewer role enables downloading metrics and viewing info on metrics, dashboards, and widgets.

Users with this role can:

• View info on metrics and their labels, as well as download metrics.
• View the list of dashboards and widgets, as well as the info on those.
• View notification history.
• View details on Monitoring quotas.
• View info on the relevant folder.

monitoring.editormonitoring.editor

The monitoring.editor role enables managing dashboards and widgets, uploading and downloading metrics, and viewing the notification history and quota details.

Users with this role can:

• View info on metrics and their labels, as well as upload and download metrics.
• View lists of dashboards and widgets and info on them, as well as create, modify, and delete them.
• View notification history.
• View details on Monitoring quotas.
• View info on the relevant folder.

This role includes the monitoring.viewer permissions.

monitoring.adminmonitoring.admin

The monitoring.admin role enables managing dashboards and widgets, uploading and downloading metrics, and viewing the notification history, info on quotas, and folder metadata.

Users with this role can:

• View info on metrics and their labels, as well as upload and download metrics.
• View lists of dashboards and widgets and info on them, as well as create, modify, and delete them.
• View notification history.
• View details on Monitoring quotas.
• View info on the relevant folder.

This role includes the monitoring.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 about primitive roles, see the Yandex Cloud role reference.