Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • 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 Serverless Integrations
  • Comparing with other Yandex Cloud services
    • All guides
        • Making a workflow public
        • Making a workflow private
        • Viewing roles assigned for a workflow
        • Assigning roles for a workflow
        • Revoking roles assigned for a workflow
    • Viewing operations with service resources
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Public materials
  • Release notes
  1. Step-by-step guides
  2. Workflows
  3. Managing workflow access permissions
  4. Making a workflow private

Making a workflow private

Written by
Yandex Cloud
Updated at May 5, 2026

By default, all workflows are private and can only be run by users who have permissions to run them. If you have made a workflow public and want to make it private again:

Management console
CLI
API
  1. In the management console, select the folder containing the workflow.
  2. Go to Serverless Integrations.
  3. In the left-hand panel, click Workflows.
  4. Select the workflow.
  5. Disable Public workflow.
  6. 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. View the description of the CLI command for updating a workflow:

    yc serverless workflow update --help
    
  2. Get a list of workflows:

    yc serverless workflow list
    

    Result:

    workflows:
      - id: dfqdi6ic7c5j********
        folder_id: b1g681qpemb4********
        created_at: "2025-03-10T13:31:55.387059Z"
        name: workflow895
        status: ACTIVE
        log_options:
          folder_id: b1g681qpemb4********
      ...
      - id: dfqud9cbc4k5********
        folder_id: b1g681qpemb4********
        created_at: "2025-03-10T12:57:48.679682Z"
        name: workflow203
        status: ACTIVE
        log_options:
          folder_id: b1g681qpemb4********
    
  3. Make a workflow private:

    yc serverless workflow update \
      --name <workflow_name> \
      --remove-is-public
    

To make a workflow private, use the Update REST API method for the Workflows resource or the workflow/Update gRPC API call with isPublic: false.

Was the article helpful?

Previous
Making a workflow public
Next
Viewing roles assigned for a workflow
© 2026 Direct Cursus Technology L.L.C.