> [!CAUTION]
> **Caution** : Document AI Warehouse is deprecated and will no longer be available on Google Cloud after January 16, 2025. To safeguard your data, migrate any documents currently saved in Document AI Warehouse to an alternative like Cloud Storage. Verify that your data migration is completed before the discontinuation date to prevent any data loss. See [Deprecations](https://docs.cloud.google.com/document-warehouse/docs/deprecations) for details.

<br />

## Predefined roles

The following table describes Identity and Access Management (IAM)
[roles](https://cloud.google.com/iam/docs/understanding-roles) that are
associated with Document AI Warehouse and lists the permissions that are contained in
each role. Unless otherwise noted, these roles can be applied either to entire
projects or specific documents.

| Role | Permissions |
|---|---|
| `contentwarehouse.documentCreator` | resourcemanager.projects.get resourcemanager.projects.list contentwarehouse.documentSchemas.get contentwarehouse.documentSchemas.list contentwarehouse.documents.create |
| `contentwarehouse.documentViewer` | resourcemanager.projects.get resourcemanager.projects.list contentwarehouse.documentSchemas.get contentwarehouse.documents.get contentwarehouse.documents.getIamPolicy |
| `contentwarehouse.documentEditor` | **Role** `contentwarehouse.documentViewer` contentwarehouse.documents.update |
| `contentwarehouse.documentAdmin` | **Role** `contentwarehouse.documentEditor` contentwarehouse.documents.create contentwarehouse.documents.delete contentwarehouse.documents.setIamPolicy |
| `contentwarehouse.admin` | **Role** `contentwarehouse.documentAdmin` contentwarehouse.documentSchemas.create contentwarehouse.documentSchemas.delete contentwarehouse.ruleSets.create contentwarehouse.ruleSets.get contentwarehouse.ruleSets.list contentwarehouse.ruleSets.update contentwarehouse.ruleSets.delete |

> [!NOTE]
> **Note:** The role `roles/contentwarehouse.documentCreator` is a parent level role. Under Document AI Warehouse's current [resource hierarchy](https://cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy) setting (Organization -\> Folders -\> Projects -\> \[Locations\] -\> Documents), this role will only be applied at the project level and not the document level. All the other roles can be applied at both the project level and the document level.

## Basic roles

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 objects within the project.
- Basic roles contain additional permissions for other Google Cloud services that are not covered in this section. For a general discussion of the permissions that basic roles grant, see [basic roles](https://cloud.google.com/iam/docs/roles-overview#basic).
- 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.

## Custom roles

You might want to define your own roles that contain bundles of permissions that
you specify. To support this, IAM offers
[custom roles](https://cloud.google.com/iam/docs/creating-custom-roles).

> [!NOTE]
> **Note:** Custom roles are not supported if you choose [Document-level access control](https://docs.cloud.google.com/document-warehouse/docs/manage-access-control#document-level-access-control) mode for your project.