Runtime Configurator는 리소스의 기본 역할을 지원합니다. 즉, 소유자, 편집자 또는 뷰어 역할을 부여하여 다른 사용자에게 Runtime Configurator 리소스에 대한 적절한 액세스 권한을 제공할 수 있습니다. 이러한 권한을 프로젝트 수준 또는 구성 리소스 수준에서 부여해야 합니다.
Runtime Configurator에는 사전 정의된 역할이 없습니다.
권한
IAM의 경우, 각 API 메소드를 호출하기 위해서는 특정 권한이 필요합니다.
아래 표를 사용하여 원하는 API 메소드에 필요한 권한을 확인하세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-03(UTC)"],[[["\u003cp\u003eThis page explains how to manage access control for Runtime Configurator resources using Google Identity and Access Management (IAM).\u003c/p\u003e\n"],["\u003cp\u003eRuntime Configurator, currently in beta, supports basic IAM roles (owner, editor, viewer), which must be granted at the project or Config resource level.\u003c/p\u003e\n"],["\u003cp\u003eSpecific permissions are required to call each Runtime Configurator API method, and the necessary permissions for each method are listed in a provided table.\u003c/p\u003e\n"],["\u003cp\u003eNo predefined roles exist for Runtime Configurator, but existing roles can be applied to grant permissions.\u003c/p\u003e\n"],["\u003cp\u003eThe beta status of the Runtime Configurator is subject to the "Pre-GA Offerings Terms" with limited support available.\u003c/p\u003e\n"]]],[],null,["# Runtime Configurator Access Control Options\n\n| **Beta**\n|\n|\n| This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products and features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nThis page describes how to set access control on your Runtime Configurator\nresources using [Google Identity and Access Management](/iam). For information\nabout Runtime Configurator, read the\n[Runtime Configurator Fundamentals](/deployment-manager/runtime-configurator).\n\nBefore you begin\n----------------\n\n- If you want to use the command-line examples in this guide, install the [\\`gcloud\\` command-line tool](/sdk).\n- If you want to use the API examples in this guide, set up [API access](/deployment-manager/docs/reference/latest).\n- Understand [Google Cloud console](https://support.google.com/cloud/answer/6158853?hl=en&ref_topic=6158848) projects.\n- Understand [Google Identity and Access Management](/iam).\n\nIAM Roles\n---------\n\nRuntime Configurator supports [basic roles](/iam/docs/understanding-roles#basic)\nfor its resources. That means you can grant either the owner, editor, or viewer\nrole to give other users the right amount of access to Runtime Configurator\nresources. You must grant these permissions on the project level or on the\n[Config resource level](/deployment-manager/runtime-configurator/reference/rest/v1beta1/projects.configs/setIamPolicy).\n\nThere are no predefined roles for Runtime Configurator.\n\nPermissions\n-----------\n\nWith IAM, Each API method requires a specific permission in order to be called.\nUse the table below to determine which permissions are necessary for the desired\nAPI method.\n\nWhat's next\n-----------\n\n- Learn about [IAM](/iam).\n- Learn about [basic roles](/iam/docs/understanding-roles#basic)."]]
