Access management
Yandex.Cloud users can only perform operations on resources that are allowed by the roles assigned to them.
If a user doesn't have any roles assigned, almost all operations are forbidden.
To allow access to Cloud Functions service resources (functions and their versions), assign users applicable roles from the list below. For now, a role can be assigned for a parent resource (folder or cloud) or a function.
Note
For more information about role inheritance, see Inheritance of access rights in the Yandex Resource Manager documentation.
Assigning roles
To assign a user a role:
-
Open the Access management page for the selected cloud. If necessary, switch to another cloud.
-
Select the user to assign the role to, click , and choose Configure roles.
-
To add a cloud role, click in the Roles for cloud
section. To add a folder role, select the folder and click Assign role in the Roles in folders section.
-
Choose a role from the list.
Roles
The list below shows all roles that are considered when verifying access rights in the Cloud Functions service.
resource-manager.clouds.member
When a new user is added to the cloud, they are automatically assigned the role of cloud member: resource-manager.clouds.member
.
Everyone needs this role to access the cloud resources, except the cloud owners and service accounts.
This role alone doesn't give you the right to perform any operations and is only used in combination with other roles, such as admin
, editor
, or viewer
.
resource-manager.clouds.owner
Theresource-manager.clouds.owner
is assigned for the cloud and makes the user the owner of the cloud. The owner can perform any operation with the cloud and its resources.
Only the cloud owner can assign users the resource-manager.clouds.owner
role.
A cloud must have at least one owner. The sole owner of a cloud may not give up this role.
serverless.functions.invoker
The serverless.functions.invoker
role grants permission to run functions.
For now, a role can only be assigned for a parent resource (folder or cloud), and roles are inherited by nested resources.
To find out how to assign this role, see Managing rights to access functions.
viewer
The user with the viewer
role can view information about resources, such as the list of functions or their versions and the function execution log.
editor
The user with the editor
role can manage functions and their versions, such as creating or deleting a version or editing information about a function.
The editor
role also includes all viewer
role permissions.
admin
The user with the admin
role can manage access rights to resources, such as allow other users to invoke functions or work with their versions.
The admin
role also includes all editor
role permissions.