Access management in SpeechKit
In this section, you will learn:
About access management
In Yandex Cloud, all transactions are checked in Yandex Identity and Access Management. If a subject does not have the required permission, the service returns an error.
To grant permissions for a resource, assign roles for this resource to the subject that will perform the operations. You can assign roles to a Yandex account, service account, federated users, user group, system group, or public group. For more information, see How access management works in Yandex Cloud.
Which resources you can assign a role for
You can assign a role to an organization, cloud, or folder. The roles assigned for organizations, clouds, or folders also apply to nested resources.
Which roles exist in the service
Service roles
ai.speechkit-stt.user
The ai.speechkit-stt.user role allows you to use Yandex SpeechKit for speech recognition, as well as view info on the relevant cloud, folder, and quotas.
ai.speechkit-tts.user
The ai.speechkit-tts.user role allows you to use Yandex SpeechKit for speech synthesis, as well as view info on the relevant cloud, folder, and quotas.
ai.auditor
The ai.auditor role enables you to view quotas for Yandex Translate, Yandex Vision, Yandex SpeechKit, and Yandex Foundation Models, view information on AI assistants, as well as read the folder metadata.
This role also includes the ai.assistants.auditor permissions.
ai.viewer
The ai.viewer role enables you to view quotas for Yandex Translate, Yandex Vision, Yandex SpeechKit, and Yandex Foundation Models, as well as view information on AI assistants and the relevant folder.
This role also includes the ai.auditor and ai.assistants.viewer permissions.
ai.editor
The ai.editor role allows you to use Yandex Translate, Yandex Vision, Yandex SpeechKit, and Yandex Foundation Models.
Users with this role can:
- Use Yandex Translate to translate texts.
- Use Yandex Vision OCR to analyze images.
- Use Yandex SpeechKit for speech recognition and synthesis.
- Use YandexGPT API language models for text generation, YandexART models for image generation, as well as AI assistants within Yandex Foundation Models.
- View information on the relevant cloud and folder.
- View information on Translate, Vision, SpeechKit, and Foundation Models quotas.
This role also includes the following roles' permissions: ai.viewer, ai.translate.user, ai.vision.user, ai.speechkit-stt.user, ai.speechkit-tts.user, ai.languageModels.user, ai.imageGeneration.user, ai.assistants.editor.
ai.admin
The ai.admin role allows you to use Yandex Translate, Yandex Vision, Yandex SpeechKit, and Yandex Foundation Models.
Users with this role can:
- Use Yandex Translate to translate texts.
- Use Yandex Vision OCR to analyze images.
- Use Yandex SpeechKit for speech recognition and synthesis.
- Use YandexGPT API language models for text generation, YandexART models for image generation, as well as AI assistants within Yandex Foundation Models.
- View information on the relevant cloud and folder.
- View information on Translate, Vision, SpeechKit, and Foundation Models quotas.
This role also includes the ai.editor and ai.assistants.admin permissions.
For more information about service roles, see Roles in the Yandex Identity and Access Management service documentation.
Roles of other services
When working with SpeechKit, you may need roles of other services, for example, to upload results and source materials to an Object Storage bucket.
resource-manager.clouds.owner
The resource-manager.clouds.owner role enables running any operations within the cloud and its child resources, as well as viewing the list of billing accounts and linking the cloud to them. This role must be assigned for a billing account. By default, the users with this role get notifications on what happens to the cloud and its folders.
This role also includes the admin and resource-manager.clouds.member permissions.
The role can only be assigned for a cloud.
storage.uploader
The storage.uploader role enables you to upload objects to a bucket and overwrite previously uploaded ones. Since the storage.uploader role inherits the permissions of the storage.viewer role, it also grants permission to list bucket objects and download them.
This role does not allow you to delete objects or configure buckets.
kms.keys.encrypterDecrypter
The kms.keys.encrypterDecrypter role enables viewing info on symmetric encryption keys and using such keys to encrypt or decrypt data.
This role also includes the kms.keys.encrypter and kms.keys.decrypter permissions.
Primitive roles
Primitive roles allow users to perform actions in all Yandex Cloud services.
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.
- 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.
viewer
The viewer role grants the permissions to read the info on any Yandex Cloud resources.
This role also includes the auditor permissions.
Unlike auditor, the viewer role provides access to service data in read mode.
editor
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 also includes the viewer permissions.
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 (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 also includes the editor permissions.
Instead of primitive roles, we recommend using service roles. This ensures more selective access control and implementation of the principle of least privilege.
For more information about primitive roles, see the Yandex Cloud role reference.