roles

Related topics

• IAM permissions is part of roles From the official documentation: “IAM permissions are [grouped into roles](/document-ai/docs/access-control/iam-roles), and you assign roles to users and groups.”
• IAM permissions depends on roles From the official documentation: “Permissions are not granted directly to users; permissions are instead granted indirectly through roles, which group permissions.”
• IAM policies configures roles From the official documentation: “IAM policies grant specific roles to a project member, which gives the identity certain permissions.”
• Identity and Access Management (IAM) configures roles From the official documentation: “IAM allows you to grant specific **roles** to users, groups, and service accounts, giving them the necessary **permissions** to perform their tasks.”
• roles is part of Looker From the official documentation: “If you need to, Looker lets you create roles to manage which users have access to features and data.”
• roles configures service accounts From the official documentation: “To manage permissions within your project, you grant roles to individuals and service accounts.”
• BigQuery works with Looker From the official documentation: “Connect Looker to the BigQuery project.”
• BigQuery works with Bigtable From the official documentation: “BigQuery lets you query your Bigtable data from BigQuery.”
• IAM permissions is part of IAM roles From the official documentation: “IAM roles that apply to Cloud SQL and the permissions contained in each role.”
• IAM roles is part of Identity and Access Management From the official documentation: “IAM roles give the principals permissions to perform tasks on your App Topology resources.”
• AlloyDB for PostgreSQL works with BigQuery From the official documentation: “Datastream lets you stream from AlloyDB for PostgreSQL to BigQuery using the Free Tier, providing up to 100 GiB of change data capture data free every month.”
• BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• IAM roles configures service accounts From the official documentation: “You can grant IAM roles to users, groups, and service accounts. These roles define what they can do with your resources.”
• Identity and Access Management (IAM) secures BigQuery From the official documentation: “BigQuery uses IAM for fine-grained access control.”
• AlloyDB for PostgreSQL works with Identity and Access Management From the official documentation: “The AlloyDB Auth Proxy and AlloyDB Language Connectors let you use [Identity and Access Management](/iam/docs/overview) (IAM) to control who has access to your data.”
• AlloyDB for PostgreSQL works with Identity and Access Management (IAM) From the official documentation: “Provide Google Cloud integrations for [Identity and Access Management (IAM)](/alloydb/docs/manage-iam-authn), [tags](/alloydb/docs/manage-tags), [Cloud Key Management Service](/alloydb/docs/cmek), and [Network Intelligence Center](/network-intelligence-center/docs).”
• AlloyDB for PostgreSQL works with Looker From the official documentation: “Looker supports connections to [AlloyDB for PostgreSQL](/alloydb/docs/overview), a fully managed, cloud-native database service from Google Cloud that is compatible with PostgreSQL.”
• Bigtable works with Identity and Access Management (IAM) From the official documentation: “Bigtable uses [IAM](/iam) for access control.”
• IAM permissions works with IAM roles From the official documentation: “This page lists the IAM roles and permissions for Apigee Registry.”
• IAM policies configures Bigtable From the official documentation: “Bigtable uses [IAM](/iam) for access control. To control who has access a resource, set IAM policies on the resource.”
• IAM policies is part of Identity and Access Management (IAM) From the official documentation: “To prevent test disruptions, ensure that your Identity and Access Management (IAM) roles, policies, and failover configurations are correctly set up.”
• IAM roles secures Bigtable From the official documentation: “Access to your Bigtable tables is controlled by your Google Cloud project and the [Identity and Access Management (IAM) roles](/bigtable/docs/access-control#roles) that you assign to users.”
• IAM roles is part of Identity and Access Management (IAM) From the official documentation: “To prevent test disruptions, ensure that your Identity and Access Management (IAM) roles, policies, and failover configurations are correctly set up.”
• Identity and Access Management secures BigQuery From the official documentation: “Security in BigQuery is intrinsically linked to [Identity and Access Management (IAM)](/iam/docs/overview) in Google Cloud.”
• Identity and Access Management secures Bigtable From the official documentation: “Bigtable uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management configures IAM permissions From the official documentation: “You can use IAM to manage who can access your project and what they are allowed to do.”
• Identity and Access Management configures IAM policies From the official documentation: “IAM lets you control **who** (identity) has **what access** (roles) to **which resource** by setting IAM policies.”
• Identity and Access Management configures service accounts From the official documentation: “To manage this access, you grant specific Identity and Access Management (IAM) roles to the service accounts that receive events and invoke your target workloads.”
• service accounts is part of Identity and Access Management From the official documentation: “The Organization Policy Service provides constraints that can be used in [organization policies](/organization-policy/overview) to limit the usage of Identity and Access Management (IAM) [service accounts](/iam/docs/service-accounts).”
• service accounts is part of Looker From the official documentation: “On January 12, 2026, we introduced service accounts in Looker (original) to help manage workflows for API credentials.”