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.”
• roles configures permissions From the official documentation: “You can grant permissions by granting roles to a principal.”
• roles configures principal From the official documentation: “IAM roles give the principals permissions to perform tasks on your Agent Registry resources.”
• custom roles is part of roles From the official documentation: “Type of roles to list. Valid values are 'custom', 'predefined', or 'all'.”
• Google Cloud console configures roles From the official documentation: “You can grant these IAM roles using the Google Cloud console or the IAM API.”
• 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.”
• predefined role is part of roles From the official documentation: “Type of roles to list. Valid values are 'custom', 'predefined', or 'all'.”
• roles configures service accounts From the official documentation: “To manage permissions within your project, you grant roles to individuals and service accounts.”
• custom roles is an alternative to predefined roles From the official documentation: “Generally, we recommend that you [use predefined roles](/iam/docs/choose-predefined-roles) instead of basic or custom roles.”
• custom roles is an alternative to predefined role From the official documentation: “Consolidate multiple predefined roles into fewer custom roles to reduce the space consumed.”
• custom roles is part of IAM roles From the official documentation: “This requirement applies to both [predefined roles](/iam/docs/roles-permissions) and [custom roles](/iam/docs/roles-overview#custom).”
• 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.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• custom roles is part of Identity and Access Management From the official documentation: “To support this, IAM offers [custom roles](/iam/docs/creating-custom-roles).”
• IAM policies configures principal From the official documentation: “IAM policies grant specific roles to principals, thereby giving them certain permissions.”
• 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.”
• predefined roles is part of IAM roles From the official documentation: “This requirement applies to both [predefined roles](/iam/docs/roles-permissions) and [custom roles](/iam/docs/roles-overview#custom).”
• 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.”
• Cloud Storage works with custom roles From the official documentation: “VPC Service Controls supports [custom roles](/iam/docs/creating-custom-roles) for Cloud Storage in ingress and egress rules, but doesn't support the [predefined Cloud Storage roles](/storage/docs/access-control/iam-roles#standard-roles).”
• Cloud Storage works with Google Cloud console From the official documentation: “The browser-based Google Cloud console tool lets you manage your Cloud Storage resources through a graphical interface.”
• Cloud Storage works with IAM From the official documentation: “Use IAM and Cloud Storage Terraform resources to create a public Cloud Storage bucket.”
• Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
• custom roles is part of IAM From the official documentation: “To support this, IAM offers [custom roles](/iam/docs/creating-custom-roles).”
• Google Cloud console works with Identity and Access Management (IAM) From the official documentation: “You can get and set IAM policies using the Google Cloud console, the Identity and Access Management API, or the Google Cloud CLI.”
• Google Cloud console configures permissions From the official documentation: “You can edit permissions and labels for multiple secrets using the Google Cloud console.”
• Google Cloud console works with role From the official documentation: “You can view the permissions granted by each role using the gcloud CLI or the Google Cloud console.”
• IAM configures Cloud Storage From the official documentation: “Apply IAM policies consistently across all relevant assets and resources in your AI and ML systems, including the following: - Cloud Storage buckets that contain sensitive data or model artifacts.”
• IAM secures Google Cloud console From the official documentation: “For information about the various user roles and getting access control to Google Cloud console see [Access control with IAM](https://cloud.google.com/support/docs/access-control).”
• IAM secures service accounts From the official documentation: “Authorized access: to ensure that only authorized service accounts can query external data, use Identity and Access Management (IAM) for centralized access control.”
• IAM permissions is part of custom roles From the official documentation: “A role is a collection of permissions.”
• IAM permissions is part of role From the official documentation: “Each role is a collection of one or more *permissions*.”
• 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 policies configures predefined roles From the official documentation: “Predefined roles, which you grant by using IAM policies, contain permissions that let principals perform specific actions.”
• IAM roles secures Cloud Storage From the official documentation: “**Fine-grained access control**: Control agent access to Cloud Storage precisely using [IAM roles](/storage/docs/access-control/iam-roles).”
• 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.”
• IAM roles configures permissions From the official documentation: “Assign one or more IAM roles to a principal to grant permissions.”
• IAM roles configures service accounts From the official documentation: “You must grant specific IAM roles to the AlloyDB cluster service account to define which datasets and tables can be queried.”
• 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 permissions From the official documentation: “Your administrator can give you the required permissions through Identity and Access Management (IAM).”
• 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.”
• Identity and Access Management (IAM) secures Cloud Storage From the official documentation: “Cloud Storage supports two methods for granting users access to your buckets and objects: Identity and Access Management (IAM) and access control lists (ACLs).”
• permissions configures role From the official documentation: “The `permissions` and `models` parameters create a [role](/looker/docs/admin-panel-users-roles) for the embed user.”
• predefined role is part of Identity and Access Management From the official documentation: “To make it easier to give these users the permissions that they need, Identity and Access Management (IAM) offers predefined roles that are designed for specific job functions.”
• predefined roles configures IAM permissions From the official documentation: “IAM predefined roles let you manage the permissions available to users.”
• predefined roles is part of Identity and Access Management From the official documentation: “There are three types of roles in IAM: - **Predefined roles** provide granular access for a specific service and are managed by Google Cloud.”
• predefined roles configures permissions From the official documentation: “Predefined roles contain permissions that allow Google Cloud project members to perform specific actions on Oracle Database@Google Cloud resources.”
• 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.”