Manage GCP BigQuery Data Policy IAM Bindings

The gcp:bigquery/datapolicyv2DataPolicyIamBinding:Datapolicyv2DataPolicyIamBinding resource, part of the Pulumi GCP provider, manages IAM role bindings for BigQuery data policies, controlling which identities can access policy-protected data. This guide focuses on two capabilities: granting roles to multiple members and adding individual members incrementally.

IAM bindings reference existing data policies and require project/location context. The examples are intentionally small. Combine them with your own data policy resources and organizational identity structure.

Grant a role to multiple members at once

Teams managing data policy access often need to grant the same role to multiple users, service accounts, or groups simultaneously.

import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";

const binding = new gcp.bigquery.Datapolicyv2DataPolicyIamBinding("binding", {
    project: basicDataPolicy.project,
    location: basicDataPolicy.location,
    dataPolicyId: basicDataPolicy.dataPolicyId,
    role: "roles/viewer",
    members: ["user:jane@example.com"],
});

import pulumi
import pulumi_gcp as gcp

binding = gcp.bigquery.Datapolicyv2DataPolicyIamBinding("binding",
    project=basic_data_policy["project"],
    location=basic_data_policy["location"],
    data_policy_id=basic_data_policy["dataPolicyId"],
    role="roles/viewer",
    members=["user:jane@example.com"])

package main

import (
	"github.com/pulumi/pulumi-gcp/sdk/v9/go/gcp/bigquery"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := bigquery.NewDatapolicyv2DataPolicyIamBinding(ctx, "binding", &bigquery.Datapolicyv2DataPolicyIamBindingArgs{
			Project:      pulumi.Any(basicDataPolicy.Project),
			Location:     pulumi.Any(basicDataPolicy.Location),
			DataPolicyId: pulumi.Any(basicDataPolicy.DataPolicyId),
			Role:         pulumi.String("roles/viewer"),
			Members: pulumi.StringArray{
				pulumi.String("user:jane@example.com"),
			},
		})
		if err != nil {
			return err
		}
		return nil
	})
}

using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Gcp = Pulumi.Gcp;

return await Deployment.RunAsync(() => 
{
    var binding = new Gcp.BigQuery.Datapolicyv2DataPolicyIamBinding("binding", new()
    {
        Project = basicDataPolicy.Project,
        Location = basicDataPolicy.Location,
        DataPolicyId = basicDataPolicy.DataPolicyId,
        Role = "roles/viewer",
        Members = new[]
        {
            "user:jane@example.com",
        },
    });

});

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gcp.bigquery.Datapolicyv2DataPolicyIamBinding;
import com.pulumi.gcp.bigquery.Datapolicyv2DataPolicyIamBindingArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
        var binding = new Datapolicyv2DataPolicyIamBinding("binding", Datapolicyv2DataPolicyIamBindingArgs.builder()
            .project(basicDataPolicy.project())
            .location(basicDataPolicy.location())
            .dataPolicyId(basicDataPolicy.dataPolicyId())
            .role("roles/viewer")
            .members("user:jane@example.com")
            .build());

    }
}

resources:
  binding:
    type: gcp:bigquery:Datapolicyv2DataPolicyIamBinding
    properties:
      project: ${basicDataPolicy.project}
      location: ${basicDataPolicy.location}
      dataPolicyId: ${basicDataPolicy.dataPolicyId}
      role: roles/viewer
      members:
        - user:jane@example.com

The Binding resource is authoritative for the specified role: it replaces all members for that role with the list you provide. The members array accepts various identity formats including user emails, service accounts, groups, and special identifiers like allUsers. The dataPolicyId, location, and project properties identify which data policy receives the binding.

Add a single member to a role incrementally

When access needs evolve, you often add individual users without affecting existing members.

import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";

const member = new gcp.bigquery.Datapolicyv2DataPolicyIamMember("member", {
    project: basicDataPolicy.project,
    location: basicDataPolicy.location,
    dataPolicyId: basicDataPolicy.dataPolicyId,
    role: "roles/viewer",
    member: "user:jane@example.com",
});

import pulumi
import pulumi_gcp as gcp

member = gcp.bigquery.Datapolicyv2DataPolicyIamMember("member",
    project=basic_data_policy["project"],
    location=basic_data_policy["location"],
    data_policy_id=basic_data_policy["dataPolicyId"],
    role="roles/viewer",
    member="user:jane@example.com")

package main

import (
	"github.com/pulumi/pulumi-gcp/sdk/v9/go/gcp/bigquery"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := bigquery.NewDatapolicyv2DataPolicyIamMember(ctx, "member", &bigquery.Datapolicyv2DataPolicyIamMemberArgs{
			Project:      pulumi.Any(basicDataPolicy.Project),
			Location:     pulumi.Any(basicDataPolicy.Location),
			DataPolicyId: pulumi.Any(basicDataPolicy.DataPolicyId),
			Role:         pulumi.String("roles/viewer"),
			Member:       pulumi.String("user:jane@example.com"),
		})
		if err != nil {
			return err
		}
		return nil
	})
}

using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Gcp = Pulumi.Gcp;

return await Deployment.RunAsync(() => 
{
    var member = new Gcp.BigQuery.Datapolicyv2DataPolicyIamMember("member", new()
    {
        Project = basicDataPolicy.Project,
        Location = basicDataPolicy.Location,
        DataPolicyId = basicDataPolicy.DataPolicyId,
        Role = "roles/viewer",
        Member = "user:jane@example.com",
    });

});

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gcp.bigquery.Datapolicyv2DataPolicyIamMember;
import com.pulumi.gcp.bigquery.Datapolicyv2DataPolicyIamMemberArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
        var member = new Datapolicyv2DataPolicyIamMember("member", Datapolicyv2DataPolicyIamMemberArgs.builder()
            .project(basicDataPolicy.project())
            .location(basicDataPolicy.location())
            .dataPolicyId(basicDataPolicy.dataPolicyId())
            .role("roles/viewer")
            .member("user:jane@example.com")
            .build());

    }
}

resources:
  member:
    type: gcp:bigquery:Datapolicyv2DataPolicyIamMember
    properties:
      project: ${basicDataPolicy.project}
      location: ${basicDataPolicy.location}
      dataPolicyId: ${basicDataPolicy.dataPolicyId}
      role: roles/viewer
      member: user:jane@example.com

The Member resource is non-authoritative: it adds one identity to a role without replacing existing grants. This lets you manage access incrementally across multiple Pulumi stacks or alongside manual grants. The member property takes a single identity string, while role and dataPolicyId specify where to grant access.

Beyond these examples

These snippets focus on specific IAM binding features: role-based access control, batch member grants, and incremental member additions. They’re intentionally minimal rather than full access management solutions.

The examples reference pre-existing infrastructure such as BigQuery data policies (dataPolicyId references) and GCP project and location configuration. They focus on configuring IAM bindings rather than provisioning the underlying data policies.

To keep things focused, common IAM patterns are omitted, including:

Conditional IAM bindings (condition property)
Policy-level management (IamPolicy resource)
Custom role definitions
Federated identity configuration

These omissions are intentional: the goal is to illustrate how each IAM binding feature is wired, not provide drop-in access control modules. See the Datapolicyv2DataPolicyIamBinding resource reference for all available configuration options.

Let's manage GCP BigQuery Data Policy IAM Bindings

Get started with Pulumi Cloud, then follow our quick setup guide to deploy this infrastructure.

Try Pulumi Cloud for FREE

Frequently Asked Questions

Resource Selection & Conflicts

Can I use IamPolicy together with IamBinding or IamMember resources?

No, Datapolicyv2DataPolicyIamPolicy cannot be used with Datapolicyv2DataPolicyIamBinding or Datapolicyv2DataPolicyIamMember because they will conflict over policy management. Use either IamPolicy alone for full control, or IamBinding/IamMember for granular control.

Can I use IamBinding and IamMember resources together?

Yes, but only if they grant different roles. Using both Datapolicyv2DataPolicyIamBinding and Datapolicyv2DataPolicyIamMember for the same role will cause conflicts.

Which IAM resource should I use for my data policy?

Choose based on your needs: Datapolicyv2DataPolicyIamPolicy for full policy control (replaces entire policy), Datapolicyv2DataPolicyIamBinding for role-level control (preserves other roles), or Datapolicyv2DataPolicyIamMember for member-level control (preserves other members for the role).

IAM Configuration

What format do custom roles need to follow?

Custom roles must use the format [projects|organizations]/{parent-name}/roles/{role-name}, for example projects/my-project/roles/my-custom-role.

What member identity formats are supported?

Supported formats include allUsers, allAuthenticatedUsers, user:{email}, serviceAccount:{email}, group:{email}, domain:{domain}, projectOwner:projectid, projectEditor:projectid, projectViewer:projectid, and federated identities like principal://iam.googleapis.com/locations/global/workforcePools/example-contractors/subject/joe@example.com.

Import & Migration

What identifier formats can I use when importing IAM bindings?

You can use the full path projects/{{project}}/locations/{{location}}/dataPolicies/{{data_policy_id}}, or shorter forms like {{location}}/{{data_policy_id}} or just {{data_policy_id}}. Any missing values are taken from the provider configuration.

Using a different cloud?

Explore security guides for other cloud providers:

AWS Guides Azure Guides