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

# Access management in SmartCaptcha

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 a role for a resource, you need the `smart-captcha.admin` role or 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 roles for [organizations](../../organization/index.md), [clouds](../../resource-manager/concepts/resources-hierarchy.md#cloud), or [folders](../../resource-manager/concepts/resources-hierarchy.md#folder). Roles assigned for organizations, clouds, and folders also apply to the CAPTCHAs within them.

## Roles available in the service {#roles-list}

The chart below shows service’s roles and their permission inheritance. For example, `editor` inherits all `viewer` permissions. You can find role descriptions below the chart.

```mermaid
flowchart BT
    smart-captcha.editor --> smart-captcha.admin
    smart-captcha.viewer --> smart-captcha.editor
    smart-captcha.auditor --> smart-captcha.viewer
```

### Service roles {#service-roles}

#### smart-captcha.auditor {#smart-captcha-auditor}

The `smart-captcha.auditor` role enables viewing info on [CAPTCHAs](../concepts/validation.md) and [access permissions](../../iam/concepts/access-control/index.md) assigned to them.

#### smart-captcha.viewer {#smart-captcha-viewer}

The `smart-captcha.viewer` role enables viewing info on [CAPTCHAs](../concepts/validation.md) and [access permissions](../../iam/concepts/access-control/index.md) assigned to them, as well as getting CAPTCHA [keys](../concepts/keys.md).

This role includes the `smart-captcha.auditor` permissions.

#### smart-captcha.editor {#smart-captcha-editor}

The `smart-captcha.editor` role enables you to manage CAPTCHAs, view info on them, and get CAPTCHA keys.

Users with this role can:
* View info on [CAPTCHAs](../concepts/validation.md) and create, modify, and delete them.
* View info on CAPTCHA [access permissions](../../iam/concepts/access-control/index.md).
* Get [CAPTCHA keys](../concepts/keys.md).

This role includes the `smart-captcha.viewer` permissions.

#### smart-captcha.admin {#smart-captcha-admin}

The `smart-captcha.admin` role enables managing CAPTCHAs and access to them, as well as getting CAPTCHA keys.

Users with this role can:
* View info on [CAPTCHAs](../concepts/validation.md) and create, modify, and delete them.
* View info on [access permissions](../../iam/concepts/access-control/index.md) assigned for CAPTCHAs and modify such permissions.
* Get [CAPTCHA keys](../concepts/keys.md).

This role includes the `smart-captcha.editor` 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).

## Required roles {#choosing-roles}

The table below maps actions to the minimum roles required to perform them. You are free to assign a role with broader permissions than the one listed in the table, e.g., `smart-captcha.editor` instead of `smart-captcha.viewer`.

Action | Role
----- | -----
Viewing CAPTCHA details | `smart-captcha.viewer`
Creating a CAPTCHA | `smart-captcha.editor`
Editing a CAPTCHA | `smart-captcha.editor`
Deleting a CAPTCHA | `smart-captcha.editor`
Managing CAPTCHA user roles | `smart-captcha.admin`