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

# Access management in Managed Service for GitLab

In this section, you will learn about:
* [Resources you can assign a role for](#resources).
* [Roles this service has](#roles-list).
* [Roles required](#required-roles) for specific actions.


To use Managed Service for GitLab, 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 `gitlab.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 for an organization, [cloud](../../resource-manager/concepts/resources-hierarchy.md#cloud), or [folder](../../resource-manager/concepts/resources-hierarchy.md#folder). Their nested resources will automatically inherit the roles.

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

```mermaid
flowchart BT
    gitlab.auditor --> gitlab.viewer
    gitlab.viewer --> gitlab.editor
    gitlab.editor --> gitlab.admin
```

### Service roles {#service-roles}

#### gitlab.auditor {#gitlab-auditor}

The `gitlab.auditor` role enables viewing info on the Managed Service for GitLab [instances](../concepts/index.md#instance) and [quotas](../concepts/limits.md#quotas).

#### gitlab.viewer {#gitlab-viewer}

The `gitlab.viewer` role enables viewing info on the Managed Service for GitLab [instances](../concepts/index.md#instance) and [quotas](../concepts/limits.md#quotas).

This role includes the `gitlab.auditor` permissions.

#### gitlab.editor {#gitlab-editor}

The `gitlab.editor` role enables managing the Managed Service for GitLab instances and migrating them to other availability zones.

Users with this role can:
* View info on the Managed Service for GitLab [instances](../concepts/index.md#instance), as well as create, modify, and delete such instances.
* Migrate instances to another [availability zones](../../overview/concepts/geo-scope.md).
* View info on the [quotas](../concepts/limits.md#quotas) for Managed Service for GitLab.

This role includes the `gitlab.viewer` permissions.

To create Managed Service for GitLab instances, you also need the `vpc.user` role.

#### gitlab.admin {#gitlab-admin}

The `gitlab.admin` role enables managing the Managed Service for GitLab instances and migrating them to other availability zones.

Users with this role can:
* View info on the Managed Service for GitLab [instances](../concepts/index.md#instance), as well as create, modify, and delete such instances.
* Migrate instances to another [availability zones](../../overview/concepts/geo-scope.md).
* View info on the [quotas](../concepts/limits.md#quotas) for Managed Service for GitLab.

This role includes the `gitlab.editor` permissions.

To create Managed Service for GitLab instances, 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 [gitlab.editor role or higher](../../iam/concepts/access-control/roles.md) for the folder where you want to create projects. With the `gitlab.viewer` role, you can only view the list of the projects and the contents of uploaded files.

To create a Managed Service for GitLab instance, you need the [vpc.user](../../vpc/security/index.md#vpc-user) role and the `gitlab.editor` role or higher.

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