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

# Access management in Cloud Interconnect

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 allow access to Cloud Interconnect 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 be [assigned](../../iam/operations/roles/grant.md) for a parent resource (folder or cloud) or an organization.

For more information about role inheritance, see [Inheriting access permissions](../../resource-manager/concepts/resources-hierarchy.md#access-rights-inheritance) for Yandex Resource Manager.

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

Roles for a resource can be assigned by users who have one of the following roles for that resource:

* `admin`
* `resource-manager.admin`
* `organization-manager.admin`
* `resource-manager.clouds.owner`
* `organization-manager.organizations.owner`

## Assigning roles {#grant-roles}

To assign a role for the cloud:

1. [Add](../../organization/operations/add-account.md) the appropriate user, if required.
1. In the [management console](https://console.yandex.cloud), on the left, [select](../../resource-manager/operations/cloud/switch-cloud.md) a cloud.
1. Navigate to the **Access bindings** tab.
1. Click **Configure access**.
1. In the window that opens, select **User accounts**.
1. Select a user from the list or use the user search option.
1. Click ![image](../../_assets/console-icons/plus.svg) **Add role** and select a role for the cloud.
1. Click **Save**.

For more information about assigning roles, see the [Yandex Identity and Access Management](../../iam/operations/roles/grant.md) documentation.

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


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

The list below shows all the roles used for access control in Cloud Interconnect.

```mermaid
%%{init: {"flowchart": {'defaultRenderer': 'elk'}} }%%
flowchart BT
    cic.auditor --> cic.viewer
    cic.viewer --> cic.editor
    cic.editor --> cic.admin
    cic.secretViewer --> cic.secretEditor
```

### Service roles {#service-roles}

#### cic.auditor {#cic-auditor}

The `cic.auditor` role enables viewing info on Cloud Interconnect resources.

{% cut "Users with this role can:" %}

* View info on the [points of presence](../concepts/pops.md).
* View info on [CIC partners](../concepts/partners.md).
* View info on [trunk links](../concepts/trunk.md).
* View info on [private connections](../concepts/priv-con.md).
* View info on [public connections](../concepts/pub-con.md).
* View info on Cloud Interconnect [quotas](../concepts/limits.md#interconnect-quotas).
* View info on the relevant [cloud](../../resource-manager/concepts/resources-hierarchy.md#cloud).
* View information on the relevant [folder](../../resource-manager/concepts/resources-hierarchy.md#folder).

{% endcut %}

#### cic.viewer {#cic-viewer}

The `cic.viewer` role enables viewing info on Cloud Interconnect resources.

{% cut "Users with this role can:" %}

* View info on the [points of presence](../concepts/pops.md).
* View info on [CIC partners](../concepts/partners.md).
* View info on [trunk links](../concepts/trunk.md).
* View info on [private connections](../concepts/priv-con.md).
* View info on [public connections](../concepts/pub-con.md).
* View info on Cloud Interconnect [quotas](../concepts/limits.md#interconnect-quotas).
* View info on the relevant [cloud](../../resource-manager/concepts/resources-hierarchy.md#cloud).
* View information on the relevant [folder](../../resource-manager/concepts/resources-hierarchy.md#folder).

{% endcut %}

This role includes the `cic.auditor` permissions.

#### cic.editor {#cic-editor}

The `cic.editor` role enables managing trunk links and private and public connections, as well as viewing info on Cloud Interconnect quotas and resources.

{% cut "Users with this role can:" %}

* View info on [trunk links](../concepts/trunk.md), as well as create, modify, and delete them.
* View info on [private connections](../concepts/priv-con.md), as well as create, modify, and delete them.
* View info on [public connections](../concepts/pub-con.md), as well as create, modify, and delete them.
* View info on the [points of presence](../concepts/pops.md).
* View info on [CIC partners](../concepts/partners.md).
* View info on Cloud Interconnect [quotas](../concepts/limits.md#interconnect-quotas).
* View info on the relevant [cloud](../../resource-manager/concepts/resources-hierarchy.md#cloud).
* View information on the relevant [folder](../../resource-manager/concepts/resources-hierarchy.md#folder).

{% endcut %}

This role includes the `cic.viewer` permissions.

#### cic.admin {#cic-admin}

The `cic.admin` role enables managing Cloud Interconnect resources.

{% cut "Users with this role can:" %}

* View info on [trunk links](../concepts/trunk.md), as well as create, modify, and delete them.
* View info on [private connections](../concepts/priv-con.md), as well as create, modify, and delete them.
* View info on [public connections](../concepts/pub-con.md), as well as create, modify, and delete them.
* View info on the [points of presence](../concepts/pops.md).
* View info on [CIC partners](../concepts/partners.md).
* View info on Cloud Interconnect [quotas](../concepts/limits.md#interconnect-quotas).
* View info on the relevant [cloud](../../resource-manager/concepts/resources-hierarchy.md#cloud).
* View information on the relevant [folder](../../resource-manager/concepts/resources-hierarchy.md#folder).

{% endcut %}

This role includes the `cic.editor` permissions.

#### cic.secretViewer {#cic-secretviewer}

The `cic.secretViewer` role enables getting Cloud Interconnect [private](../concepts/priv-con.md) and [public](../concepts/pub-con.md) connection secrets.

#### cic.secretEditor {#cic-secreteditor}

The `cic.secretEditor` role enables getting and modifying Cloud Interconnect [private](../concepts/priv-con.md) and [public](../concepts/pub-con.md) connection secrets.

This role includes the `cic.secretViewer` 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).