Assigning a role to a user

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

1. Select the role you want to assign.

2. Get the user ID.

3. Assign a role using this command:

   yc organization-manager organization add-access-binding <organization_name_or_ID> \
     --role <role_ID> \
     --user-account-id <user_ID>
   

   Where:

   • --role: Role ID.
   • --user-account-id: User ID. You can also use the --user-yandex-login parameter and specify the username instead of the ID.

   For example, assign a user the administrator role for an organization with the b1gmit33ngp3******** ID:

   yc organization-manager organization add-access-binding b1gmit33ngp3******** \
     --role resource-manager.admin \
     --user-account-id aje6o61dvog2********
   

If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), authenticate using the appropriate method.

1. Select the role you want to assign.

2. Get the user ID.

3. Describe the roles you are assigning in the configuration file:

   Example of configuration file structure for assigning a role for an organization:

   resource "yandex_organizationmanager_organization_iam_binding" "editor" {
     organization_id = "<organization_ID>"
     role            = "<role_ID>"
     member          = "userAccount:<user_ID>"
   }
   

   Where:

   • organization_id: Organization ID.

   • role: Role you want to assign. For each role, you can only use one yandex_organizationmanager_organization_iam_binding resource.

   • member: Subject getting the role.

     Subject designations

     To indicate a subject, use a combination of its type and unique ID, i.e., <subject_type>:<ID>. How you can designate a subject:

     Subject type	Subject designation
     userAccount	userAccount:<user_ID>
     serviceAccount	serviceAccount:<service_account_ID>
     federatedUser	federatedUser:<user_ID>
     group	group:<group_ID>
     system	system:allAuthenticatedUsers (All authenticated users group)
     	system:allUsers (All users group)
     	system:group:organization:<organization_ID>:users (All users in organization X group)
     	system:group:federation:<federation_ID>:users (All users in federation N group)
     	system:group:userpool:<pool_ID>:users (All users in userpool P group)

   For more on the properties of the yandex_organizationmanager_organization_iam_binding resource, see this provider guide.

4. Create the resources:

   1. In the terminal, navigate to the configuration file directory.

   2. Make sure the configuration is correct using this command:

      terraform validate
      

      If the configuration is valid, you will get this message:

      Success! The configuration is valid.
      

   3. Run this command:

      terraform plan
      

      You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration.

   4. Apply the configuration changes:

      terraform apply
      

   5. Type yes and press Enter to confirm the changes.

The specified user will then get roles in the organization. You can check the role assignment using the Cloud Center UI.

To assign the user a role for the organization, use the updateAccessBindings REST API method for the Organization resource or the OrganizationService/UpdateAccessBindings gRPC API call.

1. Select the role you want to assign.

2. Get the user ID.

3. Create the request body, e.g., in the body.json file. In the action property, enter ADD and specify the userAccount or federatedUser type and user ID under subject.

   body.json:

   {
     "accessBindingDeltas": [{
       "action": "ADD",
       "accessBinding": {
         "roleId": "<role_ID>",
         "subject": {
           "id": "<user_ID>",
           "type": "userAccount"
         }
       }
     }]
   }
   

   Where:

   • ADD in the accessBindingDeltas[].action parameter indicates you need to add a role.

   • accessBindingDeltas[].accessBinding.roleId: ID of the role you need to assign.

   • accessBindingDeltas[].accessBinding.subject.id: ID of the subject the role is assigned to.

   • accessBindingDeltas[].accessBinding.subject.type: Type of subject the role is assigned to.

     Subject designations

     To indicate a subject, use a combination of its type and unique ID in the subject.type and subject.id fields of the request. Possible combinations:

     subject.type	subject.id
     userAccount	<user_ID>
     serviceAccount	<service_account_ID>
     federatedUser	<user_ID>
     group	<group_ID>
     system	allAuthenticatedUsers (All authenticated users group)
     	allUsers (All users group)
     	group:organization:<organization_ID>:users (All users in organization X group)
     	group:federation:<federation_ID>:users (All users in federation N group)
     	group:userpool:<pool_ID>:users (All users in userpool P group)

4. Assign the role. For example, for an organization with the bpf3crucp1v2******** ID:

   export ORGANIZATION_ID=bpf3crucp1v2********
   export IAM_TOKEN=<IAM_token>
   curl \
     --request POST \
     --header "Content-Type: application/json" \
     --header "Authorization: Bearer ${IAM_TOKEN}" \
     --data '@body.json' \
     "https://organization-manager.api.cloud.yandex.net/organization-manager/v1/organizations/${ORGANIZATION_ID}:updateAccessBindings"