액세스 제어는 프로젝트 수준 및 큐 수준에서 구성 가능합니다. 예를 들어 작업을 생성하고 큐에 추가하는 것과 같은 제한된 역량은 있지만 큐를 삭제할 수는 없는 액세스 권한을 부여할 수 있습니다. 또는 개발자 그룹에 프로젝트 내의 모든 Cloud Tasks 리소스에 대한 액세스 권한을 부여할 수 있습니다.
[[["이해하기 쉬움","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-04(UTC)"],[],[],null,["# Control access using IAM\n\nCloud Tasks uses [Identity and Access Management (IAM)](/iam) for\naccess control.\n\nAccess control can be configured at the project level and at the queue level. For example:\nYou can grant access with limited capabilities, like to create and add tasks to a queue,\nbut not to delete the queue. Or you can grant access to all Cloud Tasks resources within\na project to a group of developers.\n\nFor a detailed description of IAM and its features, see the\n[IAM documentation](/iam/docs). In particular, see its\n[Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access) section.\n\nEvery Cloud Tasks method requires the caller to have the necessary permissions.\nSee below for a list of the permissions and roles supported. The Cloud Tasks\nIAM permissions are also checked when `queue.yaml/xml` is updated or when the Google Cloud console\nis used.\n| **Note:** To access and manage tasks via the Google Cloud console, an account must also have the `appengine.applications.get` permission. All of the [App Engine pre-defined roles](https://cloud.google.com/appengine/docs/standard/python3/roles) grant this permission.\n\nRoles\n-----\n\nThe following table lists the Cloud Tasks IAM roles with a corresponding list of\nall the permissions each role includes. Note that every permission is applicable\nto a particular resource type.\nCloud Tasks roles"]]
