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.”
• roles secures Cloud Trace API From the official documentation: “To use the Cloud Trace API, you or the service account must have authorization to do so. [Identity and Access Management](/iam/docs) defines permissions and roles you can use for authorization.”
• roles configures principal From the official documentation: “IAM roles give the principals permissions to perform tasks on your Agent Registry resources.”
• roles configures service accounts From the official documentation: “To manage permissions within your project, you grant roles to individuals and service accounts.”
• IAM role is part of Identity and Access Management From the official documentation: “This page explains the [Identity and Access Management](/iam) roles that are available for the Cloud Billing APIs.”
• 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.”
• IAM policies configures principal From the official documentation: “IAM policies grant specific roles to principals, thereby giving them certain permissions.”
• 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.”
• principal depends on IAM permissions From the official documentation: “When you grant an IAM *role* to a *principal*, such as a user account, that principal obtains certain *permissions* that allow them to perform actions.”
• principal works with role From the official documentation: “A binding binds one or more members, or principals, to a single role.”
• role is part of Identity and Access Management From the official documentation: “IAM operates on the security principle of least privilege and controls who can access given resources using IAM roles and permissions.”
• IAM permissions is part of IAM role From the official documentation: “Each role contains a list of permissions that let the member interact with the resource.”
• IAM permissions works with IAM roles From the official documentation: “This page lists the IAM roles and permissions for Apigee Registry.”
• IAM permissions is part of role From the official documentation: “Each role is a collection of one or more *permissions*.”
• IAM role works with principal From the official documentation: “To give a principal the required permissions, you grant an IAM role to the principal.”
• IAM role configures principal From the official documentation: “When you grant a role to a principal, you grant them all the permissions that the role contains.”
• IAM roles configures principal From the official documentation: “To control who can view, create, or update Security Command Center resources, you grant IAM roles to principals, such as users, groups, or service accounts.”
• 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.”
• role configures IAM permissions From the official documentation: “When you grant an IAM *role* to a *principal*, such as a user account, that principal obtains certain *permissions* that allow them to perform actions.”
• role configures principal From the official documentation: “You should set the minimum role needed to give the principal the required access.”
• 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 principal From the official documentation: “Cloud Run functions supports two different kinds of identities, which are also called **principals**: - Service accounts: These are special accounts that serve as the identity of a non-person, like a function or an application or a VM.”