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

# Access management in Yandex IoT Core

{% note warning %}

Yandex IoT Core is no longer available to new users. 

Current users can create resources until November 1, 2026. Afterwards, the service will go read-only and cease to operate on December 1, 2026. For more information on the timing and procedure, see [Service shutdown](../sunset.md).

{% endnote %}

In this section, you will learn about:

* [Resources supporting role assignment](#resources).
* [Roles available in the service](#roles-list).

## Access management {#about-access-control}

[Yandex Identity and Access Management](../../iam/index.md) checks all operations in Yandex Cloud. If an entity does not have required permissions, IAM returns an error.


To grant permissions for a resource, [assign](../../iam/operations/roles/grant.md) the relevant resource roles to an entity performing operations. You can assign roles to a [Yandex account](../../iam/concepts/users/accounts.md#passport), [service account](../../iam/concepts/users/service-accounts.md), [local user](../../iam/concepts/users/accounts.md#local), [federated user](../../iam/concepts/federations.md), [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). For more information, see [How access management works in Yandex Cloud](../../iam/concepts/access-control/index.md).

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`

## Resources supporting role assignment {#resources}

You can assign a role for a [cloud](../../resource-manager/concepts/resources-hierarchy.md#cloud) or [folder](../../resource-manager/concepts/resources-hierarchy.md#folder). These roles also apply to nested resources.

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

The list below shows all the roles used for access control in Yandex IoT Core.

```mermaid
flowchart BT
    iot.registries.writer --> iot.editor
    iot.viewer --> iot.editor
    iot.devices.writer --> iot.editor
    iot.auditor --> iot.viewer
```

### Service roles {#service-roles}

#### iot.devices.writer {#iot-devices-writer}

The `iot.devices.writer` role grants permission to send [gRPC messages](../concepts/mqtt-grpc.md) to Yandex IoT Core on behalf of a [device](../concepts/index.md#device).

#### iot.registries.writer {#iot-registries-writer}

The `iot.registries.writer` role grants permission to send [gRPC messages](../concepts/mqtt-grpc.md) to Yandex IoT Core on behalf of a [registry](../concepts/index.md#registry).

#### iot.auditor {#iot-auditor}

The `iot.auditor` role allows you to view metadata of [devices](../concepts/index.md#device), device [registries](../concepts/index.md#registry), and [brokers](../concepts/index.md#broker), as well as information on [quotas](../concepts/limits.md#iot-quotas) in Yandex IoT Core.

#### iot.viewer {#iot-viewer}

The `iot.viewer` role allows you to view all Yandex IoT Core resources.

#### iot.editor {#iot-editor}

The `iot.editor` role allows users to create, edit, and delete all Yandex IoT Core resources.

For more information about service roles, see [Roles](../../iam/concepts/access-control/roles.md) in the Yandex Identity and Access Management documentation.

### 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).