Access management in Yandex Cloud Postbox
Yandex Cloud users can only perform operations on resources that are allowed by the roles assigned to them. If the user has no roles assigned, all operations are forbidden.
To allow access to Yandex Cloud Postbox resources, assign the required roles from the list below to a Yandex account, service account, federated users, user group, system group, or public group. Currently, a role can only be assigned for a parent resource (folder or cloud). Roles are inherited by nested resources.
Note
For more information about role inheritance, see Inheritance of access rights in the Resource Manager documentation.
Which roles exist in the service
In Yandex Cloud Postbox, you can manage access using both service and primitive roles.
Service roles
postbox.sender
The postbox.sender role allows you to send emails from Yandex Cloud Postbox.
postbox.auditor
The postbox.auditor role allows you to view information about Yandex Cloud Postbox addresses.
Users with this role can:
- View information about addresses and their configurations.
- Get lists of addresses and their configurations.
postbox.viewer
The postbox.viewer role allows you to view information about Yandex Cloud Postbox addresses.
Users with this role can:
- View information about addresses and their configurations.
- Get lists of addresses and their configurations.
This role also includes the postbox.auditor permissions.
postbox.editor
The postbox.editor role allows you to manage Yandex Cloud Postbox addresses and send emails.
Users with this role can:
- Create, modify, and delete addresses and their configurations.
- View information about addresses and their configurations.
- Get a list of addresses and their configurations.
- Send emails.
This role also includes the postbox.viewer permissions.
postbox.admin
The postbox.admin role allows you to manage Yandex Cloud Postbox addresses and send emails.
Users with this role can:
- Create, modify, and delete addresses and their configurations.
- View information about addresses and their configurations.
- Get a list of addresses and their configurations.
- Send emails.
This role also includes the postbox.editor permissions.
Primitive roles
Primitive roles allow users to perform actions in all Yandex Cloud services.
auditor
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.
viewer
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.
editor
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.
admin
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.