Access management in Yandex Search API

In this section, you will learn about:

• Resources you can assign a role for.
• Roles existing in this service.

Access managementAccess management

Yandex Identity and Access Management checks all operations in Yandex Cloud AI Studio. If an entity does not have required permissions, IAM returns an error.

To grant permissions for a resource, assign the relevant resource roles to an entity performing operations. You can assign roles to a Yandex account, service account, local user, federated user, user group, system group, or public group. For more information, see How access management works in Yandex Cloud.

Resources you can assign a role forResources you can assign a role for

You can assign a role to an organization, cloud, or folder. The roles assigned to organizations, clouds, and folders also apply to their nested resources.

Roles existing in this serviceRoles existing in this service

Service rolesService roles

search-api.webSearch.usersearch-api.webSearch.user

The search-api.webSearch.user role enables running search queries in Yandex Search API, as well as viewing info on the cloud, folder, and Yandex Search API quotas.

search-api.executorsearch-api.executor

The search-api.executor role was used by an API that is now deprecated.

The search-api.executor role is no longer available.

search-api.auditorsearch-api.auditor

The search-api.auditor role was used by an API that is now deprecated. The role enables viewing Yandex Search API quotas, as well as information on the relevant cloud and folder.

The search-api.auditor role should no longer be used.

search-api.viewersearch-api.viewer

The search-api.viewer role was used by an API that is now deprecated. The role enables viewing Yandex Search API quotas, as well as information on the relevant cloud and folder.

The search-api.viewer role should no longer be used.

search-api.editorsearch-api.editor

The search-api.editor role was used by an API that is now deprecated. The role enables viewing Yandex Search API quotas, as well as information on the relevant cloud and folder.

The search-api.editor role should no longer be used.

search-api.adminsearch-api.admin

The search-api.admin role was used by an API that is now deprecated. The role enables viewing Yandex Search API quotas, as well as information on the relevant cloud and folder.

The search-api.admin role should no longer be used.

Primitive rolesPrimitive roles

Primitive roles allow users to perform actions in all Yandex Cloud services.

auditorauditor

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.
• 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 data. This role suits the users who need minimum access to the Yandex Cloud resources.

viewerviewer

The viewer role grants the permissions to read the info on any Yandex Cloud resources.

This role includes the auditor permissions.

Unlike auditor, the viewer role provides access to service data in read mode.

editoreditor

The editor role provides permissions to manage any Yandex Cloud resources, except for assigning roles to other users, transferring organization ownership, removing an organization, and deleting Key Management Service encryption keys.

For instance, users with this role can create, modify, and delete resources.

This role includes the viewer permissions.

adminadmin

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 (except for transferring organization ownership and removing an organization).

Prior to assigning the admin role for an organization, cloud, or billing account, make sure to check out the information on protecting privileged accounts.

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.