gcloud projects remove-iam-policy-binding Stay organized with collections Save and categorize content based on your preferences.
- NAME
- gcloud projects remove-iam-policy-binding - remove IAM policy binding for a project
- SYNOPSIS
gcloud projects remove-iam-policy-bindingPROJECT_ID--member=PRINCIPAL--role=ROLE[--all|--condition=[KEY=VALUE,…] |--condition-from-file=PATH_TO_FILE][GCLOUD_WIDE_FLAG …]
- DESCRIPTION
- Removes a policy binding to the IAM policy of a project, given a project ID andthe binding. One binding consists of a member, a role and an optional condition.
- EXAMPLES
- To remove an IAM policy binding for the role of
roles/editorforthe usertest-user@gmail.comon project with identifierexample-project-id-1, run:gcloudprojectsremove-iam-policy-bindingexample-project-id-1--member='user:test-user@gmail.com'--role='roles/editor'To remove an IAM policy binding for the role of
roles/editorfromall authenticated users on projectexample-project-id-1, run:gcloudprojectsremove-iam-policy-bindingexample-project-id-1--member='allAuthenticatedUsers'--role='roles/editor'To remove an IAM policy binding with a condition of
expression='request.time < timestamp("2019-01-01T00:00:00Z")',title='expires_end_of_2018', and description=Expires at midnight on2018-12-31for the role ofroles/browserfor the usertest-user@gmail.comon project with identifierexample-project-id-1, run:gcloudprojectsremove-iam-policy-bindingexample-project-id-1--member='user:test-user@gmail.com'--role='roles/browser'--condition='expression=request.time<timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\tion=Expires at midnight on 2018-12-31'To remove all IAM policy bindings regardless of the condition for the role of
roles/browserand for the usertest-user@gmail.comonproject with identifierexample-project-id-1, run:gcloudprojectsremove-iam-policy-bindingexample-project-id-1--member='user:test-user@gmail.com'--role='roles/browser'--allSeehttps://cloud.google.com/iam/docs/managing-policiesfor details of policy role and member types.
- POSITIONAL ARGUMENTS
- Project resource - The project to remove the IAM policy binding from. Thisrepresents a Cloud resource.
This must be specified.
PROJECT_ID- ID of the project or fully qualified identifier for the project.
To set the
project_idattribute:- provide the argument
project_idon the command line.
- provide the argument
- Project resource - The project to remove the IAM policy binding from. Thisrepresents a Cloud resource.
- REQUIRED FLAGS
--member=PRINCIPAL- The principal to remove the binding for. Should be of the form
user|group|serviceAccount:emailordomain:domain.Examples:
user:test-user@gmail.com,group:admins@example.com,serviceAccount:test123@example.domain.com, ordomain:example.domain.com.Deleted principals have an additional
deleted:prefix and a?uid=UIDsuffix, whereisa unique identifier for the principal. Example:UIDdeleted: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 as
None(--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-overviewWhen using the
--conditionflag, 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.
- At most one of these can be specified:
- 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 helpfor details. - API REFERENCE
- This command uses the
cloudresourcemanager/v1API. The fulldocumentation for this API can be found at:https://cloud.google.com/resource-manager - NOTES
- These variants are also available:
gcloudalphaprojectsremove-iam-policy-bindinggcloudbetaprojectsremove-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.