Stay organized with collections
Save and categorize content based on your preferences.
Predefined roles
The following table describes Identity and Access Management (IAM) roles
that are associated with Document AI and lists the permissions that are
contained in each role. Unless otherwise noted, these roles can be applied
either to entire projects or specific processors.
Role
Description
Permissions
Document AI Administrator
(roles/documentai.admin)
Grants full access to all resources in Document AI.
Role: roles/documentai.editor
Document AI Editor
(roles/documentai.editor)
Grants access to use all resources in Document AI.
Basic roles are roles that existed prior to IAM. These roles have
unique characteristics:
Basic roles can only be granted for an entire project, not for individual
buckets within the project. Like other roles that you grant for a project,
basic roles apply to all buckets and objects in the project.
Basic roles contain additional permissions for other Google Cloud
services that are not covered in this section. See basic roles for a
general discussion of the permissions that basic roles grant.
In some cases, basic roles can be used as if they were groups, which causes
any principal that has the basic role to get additional access for some
resources.
A basic role can be used as if it were a group when granting roles for
buckets.
A basic role can be used as if it were a group when setting ACLs on
objects.
For a discussion of additional access that principals with basic roles
typically gain due to this behavior, see
modifiable behavior.
Custom roles
You may wish to define your own roles which contain bundles of permissions that
you specify. To support this, IAM offers custom roles.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eDocument AI offers four predefined IAM roles: Administrator, Editor, Viewer, and API User, each with distinct access levels and permissions.\u003c/p\u003e\n"],["\u003cp\u003eBasic roles in IAM apply to entire projects and grant broader permissions across various Google Cloud services, unlike predefined roles.\u003c/p\u003e\n"],["\u003cp\u003eBasic roles can behave like groups in certain scenarios, granting additional access when applied to buckets or when setting ACLs on objects.\u003c/p\u003e\n"],["\u003cp\u003eCustom roles can be created to bundle specific permissions tailored to unique requirements, providing flexibility beyond the predefined roles.\u003c/p\u003e\n"]]],[],null,["# IAM roles for Document AI\n\nPredefined roles\n----------------\n\nThe following table describes Identity and Access Management (IAM) roles\nthat are associated with Document AI and lists the permissions that are\ncontained in each role. Unless otherwise noted, these roles can be applied\neither to entire projects or specific processors.\n\nBasic roles\n-----------\n\nBasic roles are roles that existed prior to IAM. These roles have\nunique characteristics:\n\n- Basic roles can only be granted for an entire project, not for individual\n buckets within the project. Like other roles that you grant for a project,\n basic roles apply to all buckets and objects in the project.\n\n- Basic roles contain additional permissions for other Google Cloud\n services that are not covered in this section. See [basic roles](/iam/docs/understanding-roles#basic) for a\n general discussion of the permissions that basic roles grant.\n\n- In some cases, basic roles can be used as if they were groups, which causes\n any principal that has the basic role to get additional access for some\n resources.\n\n - A basic role can be used as if it were a group when granting roles for\n buckets.\n\n - A basic role can be used as if it were a group when setting ACLs on\n objects.\n\n For a discussion of additional access that principals with basic roles\n typically gain due to this behavior, see\n [modifiable behavior](#basic-roles-modifiable).\n\nCustom roles\n------------\n\nYou may wish to define your own roles which contain bundles of permissions that\nyou specify. To support this, IAM offers [custom roles](/iam/docs/creating-custom-roles).\n\nWhat's next\n-----------\n\n- Learn about each [IAM permission for Document AI](/document-ai/docs/access-control/iam-permissions).\n\n- For a reference of other Google Cloud roles, see [Understanding Roles](/iam/docs/understanding-roles)."]]
