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

# Managing access to Managed Service for Trino


In this section, you will learn about the following:

* [Resources you can assign a role for](#resources).
* [Roles this service has](#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, you need the `managed-trino.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 you can assign a role for {#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 Trino resources, such as clusters and accounts, give the user the relevant roles for the folder, cloud, or organization containing those resources.

You can assign a role for an individual cluster in the [management console](https://console.yandex.cloud), via the [CLI](../cli/index.md), or [API](api-ref/authentication.md).

## Roles existing in this service {#roles-list}

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

```mermaid
%%{
  init: {
    "flowchart": { "defaultRenderer": "elk" }
  }
}%%
flowchart BT
    managed-trino.viewer --> managed-trino.user
    managed-trino.user --> managed-trino.editor
    managed-trino.editor --> managed-trino.admin
    managed-trino.auditor --> managed-trino.viewer
    managed-trino.auditor --> managed-trino.maintenanceTask.viewer["`managed-trino.
    maintenanceTask.viewer`"]
    managed-trino.maintenanceTask.viewer --> managed-trino.maintenanceTask.editor["`managed-trino.
    maintenanceTask.editor`"]
    managed-trino.maintenanceTask.viewer --> managed-trino.viewer
    managed-trino.maintenanceTask.editor --> managed-trino.editor
    managed-trino.integrationProvider["`managed-trino.
    integrationProvider`"]
```

### Service roles {#service-roles}

#### managed-trino.auditor {#managed-trino-auditor}

The `managed-trino.auditor` role enables viewing info on [Trino clusters](concepts/index.md), [access permissions](../iam/concepts/access-control/index.md) granted for them, and on [quotas](concepts/limits.md#quotas) for Managed Service for Trino.

#### managed-trino.viewer {#managed-trino-viewer}

The `managed-trino.viewer` role enables viewing info on Trino clusters and quotas for Managed Service for Trino.

Users with this role can:
* View info on [Trino clusters](concepts/index.md) and [access permissions](../iam/concepts/access-control/index.md) granted for them.
* View info on [maintenance](concepts/maintenance.md) tasks for Trino clusters.
* View info on [quotas](concepts/limits.md#quotas) for Managed Service for Trino.

This role includes the `managed-trino.auditor` and `managed-trino.maintenanceTask.viewer` permissions.

#### managed-trino.user {#managed-trino-user}

The `managed-trino.user` role enables performing basic operations on Trino clusters.

Users with this role can:
* Use the Trino web UI.
* Send requests to the Trino API.
* View info on [Trino clusters](concepts/index.md) and [access permissions](../iam/concepts/access-control/index.md) granted for them.
* View info on [maintenance](concepts/maintenance.md) tasks for Trino clusters.
* View info on quotas for Managed Service for Trino.

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

#### managed-trino.editor {#managed-trino-editor}

The `managed-trino.editor` role enables managing Trino clusters.

Users with this role can:
* View info on [Trino clusters](concepts/index.md) and [access permissions](../iam/concepts/access-control/index.md) granted for them.
* Create, modify, start, stop and delete Trino clusters.
* View info on [maintenance](concepts/maintenance.md) tasks for Trino clusters and modify such tasks.
* Use the Trino web UI.
* Send requests to the Trino API.
* View info on [quotas](concepts/limits.md#quotas) for Managed Service for Trino.

This role includes the `managed-trino.user` and `managed-trino.maintenanceTask.editor` permissions.

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

#### managed-trino.admin {#managed-trino-admin}

The `managed-trino.admin` role enables managing Trino clusters and access to them.

Users with this role can:
* View info on [access permissions](../iam/concepts/access-control/index.md) granted for [Trino clusters](concepts/index.md) and modify such permissions.
* View info on Trino clusters, as well as create, modify, run, stop, and delete them.
* View info on [maintenance](concepts/maintenance.md) tasks for Trino clusters and modify such tasks.
* Use the Trino web UI.
* Send requests to the Trino API.
* View info on [quotas](concepts/limits.md#quotas) for Managed Service for Trino.

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

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

#### managed-trino.maintenanceTask.viewer {#managed-trino-maintenanceTask-viewer}

The `managed-trino.maintenanceTask.viewer` role enables viewing info on [Trino clusters](concepts/index.md), [access permissions](../iam/concepts/access-control/index.md) granted for them, their [maintenance](concepts/maintenance.md) tasks, and on [quotas](concepts/limits.md#quotas) for Managed Service for Trino.

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

#### managed-trino.maintenanceTask.editor {#managed-trino-maintenanceTask-editor}

The `managed-trino.maintenanceTask.editor` role enables viewing info on [maintenance](concepts/maintenance.md) tasks for Trino clusters and modifying such tasks, as well as viewing info on [Trino clusters](concepts/index.md), [access permissions](../iam/concepts/access-control/index.md) granted for them, and on [quotas](concepts/limits.md#quotas) for Managed Service for Trino.

This role includes the `managed-trino.maintenanceTask.viewer` permissions.

#### managed-trino.integrationProvider {#managed-trino-integrationProvider}

The `managed-trino.integrationProvider` role enables a Trino cluster to work with user resources required for its operation on behalf of a service account. You need to assign this role to a service account linked to a Trino cluster.

Users with this role can:
* Add entries to [log groups](../logging/concepts/log-group.md).
* View info on log groups.
* View info on log sinks.
* View info on granted [access permissions](../iam/concepts/access-control/index.md) for Cloud Logging resources.
* View info on log exports.
* View info on [metrics](../monitoring/concepts/data-model.md#metric) and their [labels](../monitoring/concepts/data-model.md#label), as well as upload and download metrics.
* View lists of [dashboards](../monitoring/concepts/visualization/dashboard.md) and [widgets](../monitoring/concepts/visualization/widget.md) and info on them, as well as create, modify, and delete them.
* View [notification](../monitoring/concepts/alerting/notification-channel.md) history.
* View details on [Monitoring quotas](../monitoring/concepts/limits.md#monitoring-quotas).
* View info on the relevant [cloud](../resource-manager/concepts/resources-hierarchy.md#cloud) and [folder](../resource-manager/concepts/resources-hierarchy.md#folder).

This role includes the `logging.writer` and `monitoring.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 {#required-roles}

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

To create an Managed Service for Trino 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-trino.admin` or higher.

You can always assign a role with more permissions, e.g., `managed-trino.admin` instead of `managed-trino.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).