Discuss with expertTry it for free
© 2026 Direct Cursus Technology L.L.C.

Managing log group access permissions

Written by
Updated at September 28, 2026
View in Markdown

You can view the roles assigned for a log group, revoke them, or assign new ones.

Note

The default log group inherits the roles assigned for the folder it resides in. To update the log group access permissions, assign or revoke the roles for the folder.

Viewing roles assigned for a log group

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.

To view the roles assigned for a custom log group, run this command:

yc logging group list-access-bindings --name=<log_group_name>

Result:

+---------+--------------+-----------------------+
| ROLE ID | SUBJECT TYPE |      SUBJECT ID       |
+---------+--------------+-----------------------+
| editor  | system       | allAuthenticatedUsers |
+---------+--------------+-----------------------+

To view the roles assigned for a custom log group, use the listAccessBindings REST API method for the LogGroup resource or the LogGroupService/ListAccessBindings gRPC API call.

Assigning roles for a log group

Run the following command to assign a role for a custom log group:

yc logging group add-access-binding \
  --name <log_group_name> \
  --role <role> \
  --subject <subject_type>:<subject_ID>

Where:

  • --role: Role.

  • --subject: Subject getting the role.

    Subject designations

    To indicate a subject, use the --subject parameter in <subject_type>:<ID> format. For some subject types, the Yandex Cloud CLI provides separate parameters instead of --subject, where you only need to specify the subject name or ID without the type. Possible subject designations and matching CLI parameters:

    Subject type

    Subject designation

    Yandex Cloud CLI parameter

    userAccount

    userAccount:<user_ID>

    --user-account-id or --user-yandex-login

    serviceAccount

    serviceAccount:<service_account_ID>

    --service-account-id or --service-account-name

    federatedUser

    federatedUser:<user_ID>

    --user-account-id

    group

    group:<group_ID>

    --group-members

    system

    system:allAuthenticatedUsers

    (All authenticated users group)

    --all-authenticated-users

    system:allUsers

    (All users group)

    —

    system:group:organization:<organization_ID>:users

    (All users in organization X group)

    --organization-users

    system:group:federation:<federation_ID>:users

    (All users in federation N group)

    --federation-users

    system:group:userpool:<pool_ID>:users

    (All users in userpool P group)

    —

To assign roles for a custom log group, use the setAccessBindings REST API method for the LogGroup resource or the LogGroupService/SetAccessBindings gRPC API call.

Revoking roles assigned for a log group

Run this command to revoke a role assigned for a custom log group:

yc logging group remove-access-binding \
  --name <log_group_name> \
  --role <role_ID> \
  --subject <subject_type>:<subject_ID>

Where:

  • --role: ID of the role you need to revoke.

  • --subject: Subject to revoke the role from.

    Subject designations

    To indicate a subject, use the --subject parameter in <subject_type>:<ID> format. For some subject types, the Yandex Cloud CLI provides separate parameters instead of --subject, where you only need to specify the subject name or ID without the type. Possible subject designations and matching CLI parameters:

    Subject type

    Subject designation

    Yandex Cloud CLI parameter

    userAccount

    userAccount:<user_ID>

    --user-account-id or --user-yandex-login

    serviceAccount

    serviceAccount:<service_account_ID>

    --service-account-id or --service-account-name

    federatedUser

    federatedUser:<user_ID>

    --user-account-id

    group

    group:<group_ID>

    --group-members

    system

    system:allAuthenticatedUsers

    (All authenticated users group)

    --all-authenticated-users

    system:allUsers

    (All users group)

    —

    system:group:organization:<organization_ID>:users

    (All users in organization X group)

    --organization-users

    system:group:federation:<federation_ID>:users

    (All users in federation N group)

    --federation-users

    system:group:userpool:<pool_ID>:users

    (All users in userpool P group)

    —

To revoke roles assigned to a custom log group, use the updateAccessBindings REST API method for the LogGroup resource or the LogGroupService/UpdateAccessBindings gRPC API call. In the request body, set the action property to REMOVE and specify the subject type and ID under subject.

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. Here are 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)
Previous
Reading records
Next
Getting a list of log groups