Access control can be configured at the project level and at the queue level. For example:
You can grant access with limited capabilities, like to create and add tasks to a queue,
but not to delete the queue. Or you can grant access to all Cloud Tasks resources within
a project to a group of developers.
Every Cloud Tasks method requires the caller to have the necessary permissions.
See below for a list of the permissions and roles supported. The Cloud Tasks
IAM permissions are also checked when queue.yaml/xml is updated or when the Google Cloud console
is used.
Roles
The following table lists the Cloud Tasks IAM roles with a corresponding list of
all the permissions each role includes. Note that every permission is applicable
to a particular resource type.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-12 UTC."],[],[]]
