[Yandex Cloud documentation](../../index.md) > [Yandex Managed Service for YTsaurus](../index.md) > Access management

# Access management in Managed Service for YTsaurus

In this section, you will learn about:

* [Resources available for role assignment](#resources).
* [Available service roles](#roles-list).
* [Roles required for specific actions](#required-roles).

To use the service, log in to the management console with your [Yandex account](../../iam/concepts/users/accounts.md#passport), [federated account](../../iam/concepts/users/accounts.md#saml-federation), or [local account](../../iam/concepts/users/accounts.md#local).

## 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, a user should have the `managed-ytsaurus.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 available for role assignment {#resources}

You can assign a role to an [organization](../../organization/concepts/organization.md), [cloud](../../resource-manager/concepts/resources-hierarchy.md#cloud), or [folder](../../resource-manager/concepts/resources-hierarchy.md#folder). The roles assigned to organizations, clouds, and folders also apply to their nested resources.

To allow access to Managed Service for YTsaurus resources, such as clusters and accounts, give the user the relevant roles for the folder, cloud, or organization containing those resources.

## Available service roles {#roles-list}

The list below shows all the roles used for access control in this service.

```mermaid
%%{
  init: {
    "flowchart": { "defaultRenderer": "elk" },
    "elk": { "nodePlacementStrategy": "SIMPLE" }
  }
}%%
flowchart BT
    managed-ytsaurus.auditor --> managed-ytsaurus.viewer
    managed-ytsaurus.viewer --> managed-ytsaurus.user
    managed-ytsaurus.user --> managed-ytsaurus.editor
    managed-ytsaurus.editor --> managed-ytsaurus.admin
```

### Service roles {#service-roles}

#### managed-ytsaurus.auditor {#managed-ytsaurus-auditor}

The `managed-ytsaurus.auditor` role enables viewing info on YTsaurus clusters as well as data on the [quotas](../concepts/limits.md#quotas) and resource operations for Managed Service for YTsaurus.

#### managed-ytsaurus.viewer {#managed-ytsaurus-viewer}

The `managed-ytsaurus.viewer` role enables viewing info on YTsaurus clusters, [quotas](../concepts/limits.md#quotas), and resource operations for Managed Service for YTsaurus.

This role includes the `managed-ytsaurus.auditor` permissions.

#### managed-ytsaurus.user {#managed-ytsaurus-user}

The `managed-ytsaurus.user` role enables performing basic operations on YTsaurus clusters.

Users with this role can:
* Use the YTsaurus web UI.
* View info on YTsaurus clusters.
* View info on the [quotas](../concepts/limits.md#quotas) for Managed Service for YTsaurus.
* View info on resource operations for Managed Service for YTsaurus.

This role includes the `managed-ytsaurus.viewer` permissions.

#### managed-ytsaurus.editor {#managed-ytsaurus-editor}

The `managed-ytsaurus.editor` role enables managing YTsaurus clusters, as well as getting info on the quotas and service resource operations.

Users with this role can:
* View information on YTsaurus clusters, as well as create, modify, delete, run, and stop them.
* View info on the [quotas](../concepts/limits.md#quotas) for Managed Service for YTsaurus.
* View info on resource operations for Managed Service for YTsaurus.
* Use the YTsaurus web UI.

This role includes the `managed-ytsaurus.user` permissions.

To create YTsaurus clusters, you also need the `vpc.user` role.

#### managed-ytsaurus.admin {#managed-ytsaurus-admin}

The `managed-ytsaurus.admin` role enables managing YTsaurus clusters, as well as getting info on the quotas and service resource operations for Managed Service for YTsaurus.

Users with this role can:
* View info on YTsaurus clusters, as well as create, modify, run, stop, and delete them.
* View info on the [quotas](../concepts/limits.md#quotas) for Managed Service for YTsaurus.
* View info on resource operations for Managed Service for YTsaurus.
* Use the YTsaurus web UI.

This role includes the `managed-ytsaurus.editor` permissions.

To create YTsaurus clusters, you also need the `vpc.user` role.

### 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 {#required-roles}

As a user, you need the `managed-ytsaurus.editor` role or higher for the folder that will contain the new cluster. The `managed-ytsaurus.viewer` role only allows you to view the cluster list.

To create an Managed Service for YTsaurus cluster, the following roles are required: [vpc.user](../../vpc/security/index.md#vpc-user), [iam.serviceAccounts.user](../../iam/security/index.md#iam-serviceAccounts-user), and `managed-ytsaurus.admin` or higher.

You can always assign a role with more permissions, e.g., `managed-ytsaurus.admin` instead of `managed-ytsaurus.editor`.

## What's next {#whats-next}

* [How to assign a role](../../iam/operations/roles/grant.md).
* [How to revoke a role](../../iam/operations/roles/revoke.md).
* [Learn more about access management in Yandex Cloud](../../iam/concepts/access-control/index.md).
* [Learn more about role inheritance](../../resource-manager/concepts/resources-hierarchy.md#access-rights-inheritance).