Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Identity Hub
    • All guides
    • Subscribing a user to notifications
      • Overview
      • Creating an organization
      • Getting organization ID
      • Editing organization data
      • Managing multiple organizations
      • Managing access policies
      • Hiding information about organization members
      • Deleting an organization
      • Creating a controlled organization
      • Configuring branding
    • Billing management in Yandex Identity Hub
  • Access management
  • Pricing policy
  • Terraform reference
  • Audit Trails events
  • Release notes
  • Yandex Identity Hub Sync Agent release notes

In this article:

  • Creating an access policy for an organization
  • Viewing the list of your organization's access policies
  • Deleting an access policy created for an organization
  1. Step-by-step guides
  2. Managing organizations
  3. Managing access policies

Organization access policy management

Written by
Yandex Cloud
View in Markdown
  • Creating an access policy for an organization
  • Viewing the list of your organization's access policies
  • Deleting an access policy created for an organization

Access policies are a Yandex Identity and Access Management mechanism that allows you to manage permissions for specific operations with Yandex Cloud resources. Access policies are based on templates and complement the role system for more flexible access management.

An organization's access policies can be managed by a user with the organization-manager.admin or admin role.

Creating an access policy for an organizationCreating an access policy for an organization

To create an access policy for an organization based on a template without parameters:

CLI
Terraform
API

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

  1. Get a list of supported access policy templates with their IDs.

  2. Run this command:

    yc organization-manager organization bind-access-policy \
      --name <organization_name> \
      --access-policy-template-id=<policy_template_ID>
    

    Where:

    • --name: Name of the organization you want to create a policy for. Instead of the organization name, you can provide its ID in the --id parameter.
    • --access-policy-template-id: ID of the template you want to use as the basis for the new access policy for the organization.
  3. Make sure the policy was created.

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

For more information about the provider resources, see the guides on the Terraform website or its mirror.

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. Get the ID of the access policy template without parameters.

  2. Add the yandex_organization_manager_organization_iam_policy_binding resource to the configuration:

    resource "yandex_organization_manager_organization_iam_policy_binding" "policy" {
      organization_id = "<organization_ID>"
      access_policy_template_id = "<policy_template_ID>"
    }
    

    Where organization_id is the organization ID, and access_policy_template_id, the access policy template ID. This resource creates a policy template binding rather than assigning a role to a subject.

    For more information, see this provider guide.

  3. Apply the configuration:

    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.

Use the bindAccessPolicy REST API method for the Organization resource or the OrganizationService/BindAccessPolicy gRPC API call.

The new access policy will apply to resources within all clouds in the specified organization.

Viewing the list of your organization's access policiesViewing the list of your organization's access policies

To view a list of access policies created for an organization:

CLI
API

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

Run the following command, specifying the name or ID of the organization for which you want to view the created policies:

yc organization-manager organization list-access-policy-bindings <organization_name_or_ID>

Result:

+------------------------------+
|  ACCESS POLICY TEMPLATE ID   |
+------------------------------+
| organization.denyUserListing |
+------------------------------+

Use the listAccessPolicyBindings REST API method for the Organization resource or the OrganizationService/ListAccessPolicyBindings gRPC API call.

Deleting an access policy created for an organizationDeleting an access policy created for an organization

To delete an access policy created for an organization, follow these steps:

CLI
Terraform
API

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

  1. Get a list of IDs of access policy templates assigned for the organization.

  2. Run this command:

    yc organization-manager organization unbind-access-policy \
      --name <organization_name> \
      --access-policy-template-id=<policy_template_ID>
    

    Where:

    • --name: Name of the organization to delete the policy for. Instead of the organization name, you can provide its ID in the --id parameter.
    • --access-policy-template-id: ID of the access policy template you want to delete for the specified organization.
  3. Make sure the policy was deleted.

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

For more information about the provider resources, see the guides on the Terraform website or its mirror.

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. In the configuration, locate the yandex_organization_manager_organization_iam_policy_binding resource with the IDs of the policy template in access_policy_template_id and organization in organization_id.

  2. Remove the section of that resource. The organization resource itself should not be deleted.

  3. Apply the configuration:

    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.

    Make sure the plan removes only the correct policy binding. These steps apply to the binding managed by the current Terraform configuration.

Use the unbindAccessPolicy REST API method for the Organization resource or the OrganizationService/UnbindAccessPolicy gRPC API call.

The access policy will no longer apply to resources within all clouds in the specified organization.

Useful linksUseful links

  • Access policies

Was the article helpful?

Previous
Managing multiple organizations
Next
Hiding information about organization members
© 2026 Direct Cursus Technology L.L.C.