[Yandex Cloud documentation](../../index.md) > [Yandex Cloud Postbox](../index.md) > Access management

# Access management in Yandex Cloud Postbox

Yandex Cloud users can only perform operations on resources within the permissions of the [roles](../../iam/concepts/access-control/roles.md) assigned to them. With no roles assigned, almost no operations are allowed.

To grant access to Yandex Cloud Postbox resources, assign the relevant roles from the list below to a Yandex account, [service account](../../iam/concepts/users/service-accounts.md), [federated](../../iam/concepts/users/accounts.md#saml-federation) or [local](../../iam/concepts/users/accounts.md#local) users, [user group](../../organization/operations/manage-groups.md), [system group](../../iam/concepts/access-control/system-group.md), or [public group](../../iam/concepts/access-control/public-group.md). 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](../../resource-manager/concepts/resources-hierarchy.md#access-rights-inheritance) in the Resource Manager documentation.

## Roles this service has {#roles-list}

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

```mermaid
%%{
  init: {
    "flowchart": { "defaultRenderer": "elk" }
  }
}%%
flowchart BT
    postbox.editor --> postbox.admin
    postbox.viewer --> postbox.editor
    postbox.sender --> postbox.editor
    postbox.auditor --> postbox.viewer
    postbox.messages.reader --> postbox.admin
    postbox.statistics.reader --> postbox.admin
```

### Service roles {#service-roles}

#### postbox.sender {#postbox-sender}

The `postbox.sender` role allows you to send emails from Yandex Cloud Postbox.

#### postbox.auditor {#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](../concepts/glossary.md#adress) and their [configurations](../concepts/glossary.md#configuration).
* Get lists of addresses and their configurations.

#### postbox.viewer {#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](../concepts/glossary.md#adress) and their [configurations](../concepts/glossary.md#configuration).
* Get lists of addresses and their configurations.

This role includes the `postbox.auditor` permissions.

#### postbox.editor {#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](../concepts/glossary.md#adress) and their [configurations](../concepts/glossary.md#configuration).
* View information about addresses and their configurations.
* Get a list of addresses and their configurations.
* Send emails.

This role includes the `postbox.viewer` permissions.

#### postbox.messages.reader {#postbox-messages-reader}

The `postbox.messages.reader` role enables viewing info on sent emails in the **Sent emails** section of the [management console](https://console.yandex.cloud), including data on the sender, receivers, subject, sending date, deliverability and engagement [metrics](../concepts/statistics.md#metrics), complaints, and unsubscriptions.

#### postbox.statistics.reader {#postbox-statistics-reader}

The `postbox.statistics.reader` role enables viewing [statistics](../concepts/statistics.md) on sent emails in the **Statistics** section of the [management console](https://console.yandex.cloud).

#### postbox.admin {#postbox-admin}

The `postbox.admin` role enables managing Yandex Cloud Postbox addresses, sending emails, and viewing info on sent emails as well as their statistics.

Users with this role can:
* Create, modify, and delete [addresses](../concepts/glossary.md#adress) and their [configurations](../concepts/glossary.md#configuration).
* View info on addresses and their configurations.
* Get a list of addresses and their configurations.
* Send emails.
* View [statistics](../concepts/statistics.md) on sent emails in the **Statistics** section of the [management console](https://console.yandex.cloud).
* View info on sent emails in the **Sent emails** section of the management console, including data on the sender, receivers, subject, sending date, deliverability and engagement [metrics](../concepts/statistics.md#metrics), complaints, and unsubscriptions.

This role includes the `postbox.editor`, `postbox.messages.reader`, and `postbox.statistics.reader` permissions.

### Primitive roles {#primitive-roles}

Primitive roles allow users to perform actions in all Yandex Cloud [services](../../overview/concepts/services.md).

#### auditor {#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](../../resource-manager/concepts/resources-hierarchy.md).
* 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](../../overview/concepts/services.md) data. This role suits the users who need minimum access to the Yandex Cloud resources.

#### viewer {#viewer}

The `viewer` role grants the permissions to read the info on any Yandex Cloud [resources](../../resource-manager/concepts/resources-hierarchy.md).

This role includes the `auditor` permissions.

Unlike `auditor`, the `viewer` role provides access to [service](../../overview/concepts/services.md) data in read mode.

#### editor {#editor}

The `editor` role provides permissions to manage any Yandex Cloud [resources](../../resource-manager/concepts/resources-hierarchy.md), except for assigning roles to other users, transferring [organization](../../organization/concepts/organization.md) ownership, removing an organization, and deleting Key Management Service [encryption keys](../../kms/concepts/index.md).

For instance, users with this role can create, modify, and delete resources.

This role includes the `viewer` permissions.

#### admin {#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](../../resource-manager/concepts/resources-hierarchy.md) (except for transferring [organization](../../organization/concepts/organization.md) ownership and removing an organization).

Prior to assigning the `admin` role for an organization, [cloud](../../resource-manager/concepts/resources-hierarchy.md#cloud), or [billing account](../../billing/concepts/billing-account.md), make sure to check out the information on protecting [privileged accounts](../../security/standard/all.md#privileged-users).

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](../../security/standard/all.md#min-privileges).

For more information on primitive roles, see the [Yandex Cloud role reference](../../iam/roles-reference.md#primitive-roles).

## Useful links {#see-also}

[Hierarchy of Yandex Cloud resources](../../resource-manager/concepts/resources-hierarchy.md)