Control de acceso con la gestión de identidades y accesos
Organízate con las colecciones
Guarda y clasifica el contenido según tus preferencias.
En esta página se describen los roles de Gestión de Identidades y Accesos (IAM) necesarios para configurar el Administrador de contextos de acceso.
Roles obligatorios
En la siguiente tabla se indican los permisos y roles necesarios para crear y enumerar políticas de acceso:
Acción
Permisos y roles necesarios
Crear una política de acceso a nivel de organización o políticas con ámbito
Permiso: accesscontextmanager.policies.create
Rol que proporciona el permiso: rol Editor del Administrador de contextos de acceso
(roles/accesscontextmanager.policyEditor)
Mostrar una política de acceso a nivel de organización o políticas con ámbito
Permiso: accesscontextmanager.policies.list
Roles que proporcionan el permiso: rol Editor del Administrador de contextos de acceso
(roles/accesscontextmanager.policyEditor)
Rol Lector del Administrador de contextos de acceso
(roles/accesscontextmanager.policyReader)
Solo puedes crear, enumerar o delegar políticas con ámbito si tienes esos permisos a nivel de organización. Después de crear una política de ámbito, puedes conceder permiso para gestionar la política añadiendo enlaces de gestión de identidades y accesos a la política de ámbito.
Los permisos concedidos a nivel de organización se aplican a todas las políticas de acceso, incluida la política a nivel de organización y las políticas con ámbito.
Los siguientes roles de gestión de identidades y accesos seleccionados proporcionan los permisos necesarios para ver o configurar niveles de acceso, o bien para conceder permisos a administradores delegados en políticas con ámbito mediante la herramienta de línea de comandos gcloud:
Administrador de contextos de acceso: roles/accesscontextmanager.policyAdmin
Editor del Administrador de contextos de acceso: roles/accesscontextmanager.policyEditor
Lector del Administrador de contextos de acceso: roles/accesscontextmanager.policyReader
Además, para permitir que los usuarios gestionen Access Context Manager mediante laGoogle Cloud consolaroles/resourcemanager.organizationViewer, se necesita el rol Lector de la organización de Resource Manager (roles/resourcemanager.organizationViewer).
[[["Es fácil de entender","easyToUnderstand","thumb-up"],["Me ofreció una solución al problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Es difícil de entender","hardToUnderstand","thumb-down"],["La información o el código de muestra no son correctos","incorrectInformationOrSampleCode","thumb-down"],["Me faltan las muestras o la información que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-08-21 (UTC)."],[[["\u003cp\u003eSuper administrators have default permissions for Access Context Manager roles, but require the Resource Manager Organization Viewer role to manage it via the Google Cloud console.\u003c/p\u003e\n"],["\u003cp\u003eCreating or listing access policies requires the \u003ccode\u003eaccesscontextmanager.policies.create\u003c/code\u003e or \u003ccode\u003eaccesscontextmanager.policies.list\u003c/code\u003e permission, which are provided by the Access Context Manager Editor or Reader roles respectively.\u003c/p\u003e\n"],["\u003cp\u003eScoped policy management is independent of folder or project permissions, and permissions must be granted at the organization level.\u003c/p\u003e\n"],["\u003cp\u003eThe Access Context Manager Admin, Editor, and Reader roles provide read-write or read-only access for managing access levels or delegating permissions, and the Resource Manager Organization Viewer role is required for console management.\u003c/p\u003e\n"],["\u003cp\u003eUsers with resource ownership in the organization can potentially learn access level names without having the proper permissions, as seen in cases like Identity-Aware Proxy generating JWTs.\u003c/p\u003e\n"]]],[],null,["# Access control with IAM\n\nThis page describes the Identity and Access Management (IAM) roles required to\nconfigure to Access Context Manager.\n\nRequired roles\n--------------\n\n| **Note:** [Super administrators](/resource-manager/docs/super-admin-best-practices) are granted the permissions provided by the Access Context Manager roles by default. However, if you want the super admin to be able to manage Access Context Manager using the Google Cloud console, you must still assign the Resource Manager Organization Viewer role.\n\nThe following table lists the permissions and roles required to create and list\naccess policies:\n\nYou can only create, list, or delegate scoped policies if you have those permissions\nat the organization level. After you create a scoped policy, you can grant permission to\nmanage the policy by adding IAM bindings on the scoped policy.\n\nPermissions granted at the organization-level apply to all access policies, including\nthe organization-level policy and any scoped policies.\n| **Note:** Any Access Context Manager permissions granted on folders or projects have no effect on scoped policies as permissions can only be granted at the organization-level or on individual policies. The access control for scoped policies is independent of the projects or folders in their scopes.\n\nThe following curated IAM roles provide the necessary permissions\nto view or configure access levels or grant permissions to delegated administrators\non scoped policies using the `gcloud` command-line tool:\n\n- Access Context Manager Admin: `roles/accesscontextmanager.policyAdmin`\n- Access Context Manager Editor: `roles/accesscontextmanager.policyEditor`\n- Access Context Manager Reader: `roles/accesscontextmanager.policyReader`\n\nAdditionally, to let your users manage Access Context Manager using the\nGoogle Cloud console, the Resource Manager Organization Viewer\n(`roles/resourcemanager.organizationViewer`) role is required.\n| **Note:** Users that own resources in the organization could learn the names of access levels even without the required permissions. For example, Identity-Aware Proxy generates a JWT with a [`google.accessLevels`](/iap/docs/signed-headers-howto#verifying_the_jwt_payload) claim that contains the access level names satisfied by the request.\n\nTo grant one of these roles, [use the Google Cloud console](/iam/docs/granting-changing-revoking-access) or\nuse the `gcloud` command-line tool:\n\n### Admin allows read-write access\n\n```bash\ngcloud organizations add-iam-policy-binding ORGANIZATION_ID \\\n --member=\"user:example@customer.org\" \\\n --role=\"roles/accesscontextmanager.policyAdmin\"\n```\n\n### Editor allows read-write access\n\n```bash\ngcloud organizations add-iam-policy-binding ORGANIZATION_ID \\\n --member=\"user:example@customer.org\" \\\n --role=\"roles/accesscontextmanager.policyEditor\"\n```\n\n### Reader allows read-only access\n\n```bash\ngcloud organizations add-iam-policy-binding ORGANIZATION_ID \\\n --member=\"user:example@customer.org\" \\\n --role=\"roles/accesscontextmanager.policyReader\"\n```\n\n### Organization Viewer allows access to VPC Service Controls using the Google Cloud console\n\n```bash\ngcloud organizations add-iam-policy-binding ORGANIZATION_ID \\\n --member=\"user:example@customer.org\" \\\n --role=\"roles/resourcemanager.organizationViewer\"\n```\n\nWhat's next\n-----------\n\n- [Access Context Manager overview](/access-context-manager/docs/overview)\n- [Create an access policy](/access-context-manager/docs/create-access-policy)"]]
