Namespace Google.Cloud.Iam.V1 (3.0.0)



Specifies the audit configuration for a service. The configuration determines which permission types are logged, and what identities, if any, are exempted from logging. An AuditConfig must have one or more AuditLogConfigs.

If there are AuditConfigs for both allServices and a specific service, the union of the two AuditConfigs is used for that service: the log_types specified in each AuditConfig are enabled, and the exempted_members in each AuditLogConfig are exempted.

Example Policy with multiple AuditConfigs:

{ "audit_configs": [ { "service": "allServices", "audit_log_configs": [ { "log_type": "DATA_READ", "exempted_members": [ "" ] }, { "log_type": "DATA_WRITE" }, { "log_type": "ADMIN_READ" } ] }, { "service": "", "audit_log_configs": [ { "log_type": "DATA_READ" }, { "log_type": "DATA_WRITE", "exempted_members": [ "" ] } ] } ] }

For sampleservice, this policy enables DATA_READ, DATA_WRITE and ADMIN_READ logging. It also exempts from DATA_READ logging, and from DATA_WRITE logging.


One delta entry for AuditConfig. Each individual change (only one exempted_member in each entry) to a AuditConfig will be a separate entry.


Container for nested types declared in the AuditConfigDelta message type.


Provides the configuration for logging a type of permissions. Example:

{ "audit_log_configs": [ { "log_type": "DATA_READ", "exempted_members": [ "" ] }, { "log_type": "DATA_WRITE" } ] }

This enables 'DATA_READ' and 'DATA_WRITE' logging, while exempting from DATA_READ logging.


Container for nested types declared in the AuditLogConfig message type.


Associates members, or principals, with a role.


One delta entry for Binding. Each individual change (only one member in each entry) to a binding will be a separate entry.


Container for nested types declared in the BindingDelta message type.


Request message for GetIamPolicy method.


Encapsulates settings provided to GetIamPolicy.


API Overview

Manages Identity and Access Management (IAM) policies.

Any implementation of an API that offers access control features implements the google.iam.v1.IAMPolicy interface.

Data model

Access control is applied when a principal (user or service account), takes some action on a resource exposed by a service. Resources, identified by URI-like names, are the unit of access control specification. Service implementations can choose the granularity of access control and the supported permissions for their resources. For example one database service may allow access control to be specified only at the Table level, whereas another might allow access control to also be specified at the Column level.

Policy Structure

See google.iam.v1.Policy

This is intentionally not a CRUD style API because access control policies are created and deleted implicitly with the resources to which they are attached.


Base class for server-side implementations of IAMPolicy


Client for IAMPolicy


IAMPolicy client wrapper, for convenient use.


Builder class for IAMPolicyClient to provide simple configuration of credentials, endpoint etc.


IAMPolicy client wrapper implementation, for convenient use.


Settings for IAMPolicyClient instances.


An Identity and Access Management (IAM) policy, which specifies access controls for Google Cloud resources.

A Policy is a collection of bindings. A binding binds one or more members, or principals, to a single role. Principals can be user accounts, service accounts, Google groups, and domains (such as G Suite). A role is a named list of permissions; each role can be an IAM predefined role or a user-created custom role.

For some types of Google Cloud resources, a binding can also specify a condition, which is a logical expression that allows access to a resource only if the expression evaluates to true. A condition can add constraints based on attributes of the request, the resource, or both. To learn which resources support conditions in their IAM policies, see the IAM documentation.

JSON example:

{ "bindings": [ { "role": "roles/resourcemanager.organizationAdmin", "members": [ &quot;", &quot;", "", &quot;" ] }, { "role": "roles/resourcemanager.organizationViewer", "members": [ &quot;" ], "condition": { "title": "expirable access", "description": "Does not grant access after Sep 2020", "expression": "request.time < timestamp('2020-10-01T00:00:00.000Z')", } } ], "etag": "BwWWja0YfJA=", "version": 3 }

YAML example:


  • members:
    • role: roles/resourcemanager.organizationAdmin
  • members:
    • role: roles/resourcemanager.organizationViewer condition: title: expirable access description: Does not grant access after Sep 2020 expression: request.time < timestamp('2020-10-01T00:00:00.000Z') etag: BwWWja0YfJA= version: 3

For a description of IAM and its features, see the IAM documentation.


The difference delta between two policies.


Request message for SetIamPolicy method.


Request message for TestIamPermissions method.


Response message for TestIamPermissions method.



The type of action performed on an audit configuration in a policy.


The list of valid permission types for which logging can be configured. Admin writes are always logged, and are not configurable.


The type of action performed on a Binding in a policy.