Access management in Yandex Cloud Notification Service

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 allow access to Cloud Notification Service 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, such as a folder or cloud. Roles are inherited by nested resources.

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

Roles existing in this serviceRoles existing in this service

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

Service rolesService roles

notifications.auditornotifications.auditor

The notifications.auditor role enables viewing metadata for all notification channels, topic metadata, and info on Cloud Notification Service quotas.

notifications.viewernotifications.viewer

The notifications.viewer role enables viewing info on topics, notification channels, and Cloud Notification Service quotas.

Users with this role can:

• View info on topics and subscriptions in them.
• View info on mobile push notification channels and their endpoints.
• View info on browser push notification channels and their endpoints.
• View info on text message (SMS) channels, SMS templates, and test phone numbers.
• View info on Cloud Notification Service quotas.

This role includes the notifications.auditor permissions.

notifications.publishernotifications.publisher

The notifications.publisher role enables sending notifications to all channels and topics.

notifications.editornotifications.editor

The notifications.editor role enables managing all notification channels and topics, as well as sending notifications to all channels and topics.

Users with this role can:

• View info on topics and create, modify, and delete them.
• View info on subscriptions in topics, as well as create and delete them.
• View info on mobile push notification channels and their endpoints, as well as create, modify, and delete such channels and endpoints.
• View info on browser push notification channels and their endpoints, as well as create, modify, and delete such channels and endpoints.
• View info on text message (SMS) notification channels, as well as create, modify, and delete them.
• View info on text message (SMS) templates and test phone numbers, as well as modify them.
• Send notifications to all topics and channels.
• View info on Cloud Notification Service quotas.

This role includes the notifications.viewer and notifications.publisher permissions.

notifications.adminnotifications.admin

The notifications.admin role enables managing all notification channels and topics, as well as sending notifications to all channels and topics.

Users with this role can:

• View info on topics and create, modify, and delete them.
• View info on subscriptions in topics, as well as create and delete them.
• View info on mobile push notification channels and their endpoints, as well as create, modify, and delete such channels and endpoints.
• View info on browser push notification channels and their endpoints, as well as create, modify, and delete such channels and endpoints.
• View info on text message (SMS) notification channels, as well as create, modify, and delete them.
• View info on text message (SMS) templates and test phone numbers, as well as modify them.
• Send notifications to all topics and channels.
• View info on Cloud Notification Service quotas.

This role includes the notifications.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