Use IAM Policy Conditions

Run projects list command (Windows/macOS/Linux) with custom output filters to list the ID of each project available in your Google Cloud Platform (GCP) account:

gcloud projects list
	--format="table(projectId)"

The command output should return the requested GCP project IDs:

PROJECT_ID
cc-web-project-123123
cc-iot-project-112233

Run tasks queues list command (Windows/macOS/Linux) with the ID of the GCP project that you want to examine as the identifier parameter and custom output filters to describe the ID (i.e., fully qualified identifier) of each Cloud Tasks queue created for the selected project, in the specified region:

gcloud tasks queues list
	--project="cc-web-project-123123"
	--location="us-central1"
	--format="default(name)"

The command output should return the requested queue IDs:

---
name: projects/cc-web-project-123123/locations/us-central1/queues/cc-user-notification-queue
---
name: projects/cc-web-project-123123/locations/us-central1/queues/cc-invoice-generation-queue

Run tasks queues get-iam-policy command (Windows/macOS/Linux) with the ID of the Cloud Tasks queue that you want to examine as the identifier parameter, to describe the IAM policy defined for the selected queue:

gcloud tasks queues get-iam-policy projects/cc-web-project-123123/locations/us-central1/queues/cc-user-notification-queue
	--format="json"

The command output should return the requested IAM policy in JSON format:

{
	"bindings": [
		{
			"members": [
				"user:username1@domain.com"
			],
			"role": "roles/cloudtasks.enqueuer"
		},
		{
			"members": [
				"user:username2@domain.com"
			],
			"role": "roles/cloudtasks.taskRunner"
		},
		{
			"members": [
				"user:username3@domain.com"
			],
			"role": "roles/cloudtasks.viewer"
		}
	],
	"etag": "ABCD1234ABCD",
	"version": 1
}

Check the IAM policy document returned by the get-iam-policy command output for "condition" elements. A "condition" element has the following format: "condition": {"title": "TITLE", "description": "DESCRIPTION", "expression": "EXPRESSION"}. If there are no "condition" elements defined for IAM policy bindings, the policy associated with the selected Cloud Tasks queue is not using IAM conditions fine-grained access control.

Repeat steps no. 5 and 6 for each Cloud Tasks queue available in the selected GCP project.

Repeat steps no. 3 – 7 for each GCP project deployed in your Google Cloud account.

To add an IAM condition to a role binding, you must define the "condition" element, as shown in the policy example below. A "condition" element has the following format: "condition": {"title": "TITLE", "description": "DESCRIPTION", "expression": "EXPRESSION"}. For more details about the "condition" element structure, see the official documentation. Save the modified policy document to a JSON file named cc-iam-policy.json:

{
	"bindings": [
		{
			"members": [
				"user:username1@domain.com"
			],
			"role": "roles/cloudtasks.enqueuer",
			"condition": {
				"title": "time-based-access-control",
				"description": "Allow access to create tasks only until June 1, 2025",
				"expression": "request.time < timestamp('2025-06-01T00:00:00.000Z')"
			}
		},
		{
			"members": [
				"user:username2@domain.com"
			],
			"role": "roles/cloudtasks.taskRunner"
		},
		{
			"members": [
				"user:username3@domain.com"
			],
			"role": "roles/cloudtasks.viewer"
		}
	],
	"etag": "ABCD1234ABCD",
	"version": 1
}

Run tasks queues set-iam-policy command (Windows/macOS/Linux) with the ID of the Cloud Tasks queue that you want to configure as the identifier parameter, to set the IAM policy modified at the previous step (i.e., cc-iam-policy.json) to the selected queue:

gcloud tasks queues set-iam-policy projects/cc-web-project-123123/locations/us-central1/queues/cc-user-notification-queue cc-iam-policy.json

The command output should return the modified IAM policy:

bindings:
	- members:
		- user:username1@domain.com
	role: roles/cloudtasks.enqueuer
	condition:
		title: time-based-access-control
		description: Allow access to create tasks only until June 1, 2025
		expression: request.time < timestamp('2025-06-01T00:00:00.000Z')
	- members:
		- user:username2@domain.com
	role: roles/cloudtasks.taskRunner
	- members:
		- user:username3@domain.com
	role: roles/cloudtasks.viewer
etag: ABCD1234ABCD
version: 1

Repeat steps no. 1 - 3 for each Cloud Tasks queue that you want to configure, available in the selected GCP project.

Repeat steps no. 1 – 4 for each GCP project deployed in your Google Cloud account.