Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
En esta página, se describen las funciones de administración de identidades y accesos (IAM) necesarias para configurarse en Access Context Manager.
Funciones requeridas
En la siguiente tabla, se enumeran los permisos y los roles que se necesitan para crear y enumerar políticas de acceso:
Acción
Funciones y permisos obligatorios
Crea una política de acceso a nivel de la organización o políticas con alcance
Permiso: accesscontextmanager.policies.create
Rol que proporciona el permiso: rol de editor de Access Context Manager (roles/accesscontextmanager.policyEditor)
Enumera una política de acceso a nivel de la organización o políticas con alcance
Permiso: accesscontextmanager.policies.list
Roles que proporcionan el permiso: rol de editor de Access Context Manager (roles/accesscontextmanager.policyEditor)
Rol de lector de Access Context Manager (roles/accesscontextmanager.policyReader)
Solo puedes crear, enumerar o delegar políticas con alcance si tienes esos permisos a nivel de la organización. Después de crear una política con alcance, puedes otorgar permiso para administrar la política si agregas vinculaciones de IAM en la política con alcance.
Los permisos otorgados a nivel de la organización se aplican a todas las políticas de acceso, incluida la política a nivel de la organización y cualquier política con alcance.
Los siguientes roles de IAM seleccionados proporcionan los permisos necesarios para ver o configurar los niveles de acceso, o bien otorgar permisos a los administradores delegados en políticas centradas con la herramienta de línea de comandos de gcloud:
Administrador de Access Context Manager: roles/accesscontextmanager.policyAdmin
Editor de Access Context Manager: roles/accesscontextmanager.policyEditor
Lector de Access Context Manager: roles/accesscontextmanager.policyReader
Además, para permitir que tus usuarios administren Access Context Manager con la consola deGoogle Cloud , se requiere el rol de visualizador de organizaciones de Resource Manager (roles/resourcemanager.organizationViewer).
Para otorgar uno de estos roles, usa la Google Cloud consola o la herramienta de línea de comandos de gcloud:
El administrador permite el acceso de lectura y escritura
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (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)"]]
