gcloud storage buckets remove-iam-policy-binding

NAME
gcloud storage buckets remove-iam-policy-binding - remove an IAM policy binding from a bucket
SYNOPSIS
gcloud storage buckets remove-iam-policy-bindingURL--member=PRINCIPAL--role=ROLE[--all    |--condition=[KEY=VALUE,…]    |--condition-from-file=PATH_TO_FILE][GCLOUD_WIDE_FLAG]
DESCRIPTION
Removes a policy binding from the IAM policy of a bucket, given a bucket URL andthe binding. For more information, seeCloud Identityand Access Management.
EXAMPLES
To remove an IAM policy binding from the role of roles/storage.objectCreator forthe user john.doe@example.com on BUCKET:
gcloudstoragebucketsremove-iam-policy-bindinggs://BUCKET--member=user:john.doe@example.com--role=roles/storage.objectCreator
POSITIONAL ARGUMENTS
URL
URL of bucket to remove IAM policy binding from.
REQUIRED FLAGS
--member=PRINCIPAL
The principal to remove the binding for. Should be of the formuser|group|serviceAccount:email ordomain:domain.

Examples:user:test-user@gmail.com,group:admins@example.com,serviceAccount:test123@example.domain.com, ordomain:example.domain.com.

Deleted principals have an additionaldeleted: prefix and a?uid=UID suffix, whereUID isa unique identifier for the principal. Example:deleted:user:test-user@gmail.com?uid=123456789012345678901.

Some resources also accept the following special values:

  • allUsers - Special identifier that represents anyone who is on theinternet, with or without a Google account.
  • allAuthenticatedUsers - Special identifier that represents anyonewho is authenticated with a Google account or a service account.
--role=ROLE
The role to remove the principal from.
OPTIONAL FLAGS
At most one of these can be specified:
--all
Remove all bindings with this role and principal, irrespective of anyconditions.
--condition=[KEY=VALUE,…]
The condition of the binding that you want to remove. When the condition isexplicitly specified asNone (--condition=None), abinding without a condition is removed. Otherwise, only a binding with acondition that exactly matches the specified condition (including the optionaldescription) is removed. For more on conditions, refer to the conditionsoverview guide:https://cloud.google.com/iam/docs/conditions-overview

When using the--condition flag, include the following key-valuepairs:

expression
(Required) Condition expression that evaluates to True or False. This uses asubset of Common Expression Language syntax.

If the condition expression includes a comma, use a different delimiter toseparate the key-value pairs. Specify the delimiter before listing the key-valuepairs. For example, to specify a colon (:) as the delimiter, do thefollowing:--condition=^:^title=TITLE:expression=EXPRESSION. Formore information, seehttps://cloud.google.com/sdk/gcloud/reference/topic/escaping.

title
(Required) A short string describing the purpose of the expression.
description
(Optional) Additional description for the expression.
--condition-from-file=PATH_TO_FILE
Path to a local JSON or YAML file that defines the condition. To see availablefields, see the help for--condition. Use a full or relative pathto a local file containing the value of condition.
GCLOUD WIDE FLAGS
These flags are available to all commands:--access-token-file,--account,--billing-project,--configuration,--flags-file,--flatten,--format,--help,--impersonate-service-account,--log-http,--project,--quiet,--trace-token,--user-output-enabled,--verbosity.

Run$gcloud help for details.

NOTES
This variant is also available:
gcloudalphastoragebucketsremove-iam-policy-binding

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-05-07 UTC.