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
    • Cloud Desktop
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • 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
        • Creating an app
        • Updating an app
        • Setting up access to the application
        • Getting app information
        • Deactivating and deleting an app
    • Syncing users and groups with Active Directory
    • Billing management in Yandex Identity Hub
  • Access management
  • Pricing policy
  • Terraform reference
  • Audit Trails events
  • Release notes
  • Yandex Identity Hub Sync Agent release notes
  1. Step-by-step guides
  2. Managing apps (SSO)
  3. SAML apps
  4. Setting up access to the application

Setting up access to an SAML app in Yandex Identity Hub

Written by
Yandex Cloud
Updated at July 16, 2026
View in Markdown

To grant access to a SAML app, assign roles to subjects. Learn what roles the service has and assign the required ones.

Cloud Center UI
CLI
API
  1. Log in to Yandex Identity Hub.
  2. In the left-hand panel, click Apps and select your app.
  3. Navigate to the Access bindings tab.
  4. Click Assign roles.
  5. In the window that opens, select the group, user, or service account to which you want to give access to the app.
  6. Click Add role and select a role. Add other roles as needed.
  7. Click Save.

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. See the description of the CLI command for assigning roles to SAML app users:

    yc organization-manager idp application saml application set-access-bindings --help
    
  2. Get a list of SAML apps and their IDs:

    yc organization-manager idp application saml application list --organization-id <organization_ID>
    

    Where --organization-id is the ID of the organization you need the list of SAML apps for.

  3. Get the ID of the user, service account, or user group you are assigning roles to.

  4. Using the yc organization-manager idp application saml application set-access-bindings command, assign the following roles:

    • To a Yandex account user or local user:

      yc organization-manager idp application saml application set-access-bindings \
        --id <app_ID> \
        --access-binding role=<role>,user-account-id=<user_ID>
      
    • To all users of a federation:

      yc organization-manager idp application saml application set-access-bindings \
        --id <app_ID> \
        --access-binding role=<role>,federation-users=<federation_ID>
      
    • To all users of an organization:

      yc organization-manager idp application saml application set-access-bindings \
        --id <app_ID> \
        --access-binding role=<role>,organization-users=<organization_ID>
      
    • To a service account:

      yc organization-manager idp application saml application set-access-bindings \
        --id <app_ID> \
        --access-binding role=<role>,service-account-id=<service_account_ID>
      
    • To a user group:

      yc organization-manager idp application saml application set-access-bindings \
        --id <app_ID> \
        --access-binding role=<role>,group-members=<group_ID>
      
    • To all authenticated users (the All authenticated users public group):

      yc organization-manager idp application oauth application set-access-bindings \
        --id <app_ID> \
        --access-binding role=<role>,all-authenticated-users
      

    Provide a separate --access-binding parameter for each role. Here is an example:

    yc organization-manager idp application oauth application set-access-bindings \
      --id <app_ID> \
      --access-binding role=<role1>,service-account-id=<service_account_ID> \
      --access-binding role=<role2>,service-account-id=<service_account_ID> \
      --access-binding role=<role3>,service-account-id=<service_account_ID>
    

Use the Application.SetAccessBindings REST API method for the Application resource or the ApplicationService/SetAccessBindings gRPC API call.

Was the article helpful?

Previous
Updating an app
Next
Getting app information
© 2026 Direct Cursus Technology L.L.C.