> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/best-practices/google-labels/google-drive-labels.md).

# Google Drive labels

Google Drive labels are metadata or tags that add a layer of data governance to your Google files. Labels allow your company to organize, find and apply policies to files, especially if the content is sensitive or classified.

You can apply Google labels to any file in Google Drive owned by your organization, but not to folders, shortcuts, shared drives, or files owned by another organization. Drive labels can be just a tag, or they can have structured metadata fields that include selection fields, dates, numbers, or people.

Leveraging Google labels and Workspace DLP allows your organization to prevent external sharing of sensitive files based on the file’s classification label.

{% hint style="success" %}
**For example**: Your organization has defined a policy that all files tagged with the Confidential label cannot be shared with anyone outside your company. As an admin user, you can define a DLP rule in Google Admin Console that prevents any files with the Confidential label from being shared externally.
{% endhint %}

<div align="left"><figure><img src="https://2285563887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ8EVaJEzDNNBVDXvFrLt%2Fuploads%2F27SJI7PUuDd3gHJJnETN%2Fconfidential%20label.png?alt=media&#x26;token=6e1fa74b-cf37-4089-8ddc-2f8d3f434122" alt=""><figcaption><p>Google sheet with Confidential badge next to the file name</p></figcaption></figure></div>

## Label types

Google allows organizations to configure a maximum of 150 unique labels, including 1 badged label. Once configured, you can tag assets across your organization's Google Drive with badges and labels, either manually or automatically using Workspace DLP or Google AI classification.

<div align="left"><figure><img src="https://2285563887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ8EVaJEzDNNBVDXvFrLt%2Fuploads%2FbySFVB3OYmc9nGrqTOTR%2FGoogle%20label%20display.png?alt=media&#x26;token=d8d2cfa9-de60-4d52-8ec5-416d8870b0e7" alt=""><figcaption></figcaption></figure></div>

Google label types include badges and standard labels:

<table data-full-width="false"><thead><tr><th width="159">Label type</th><th width="323">Elements</th><th>Display</th></tr></thead><tbody><tr><td>Badge</td><td><p>A single badge indicates your organization’s most critical metadata. For example, a File Sensitivity badge can display these values each with a different color:</p><ul><li>Top Secret</li><li>Internal</li><li>Private</li><li>Public</li></ul></td><td>Colored badge next to asset name inside the file</td></tr><tr><td>Standard label</td><td><p>Each label can be structured, containing up to 10 fields, and each field can contain several values. For example, a contract status field can include these values:</p><ul><li>Draft</li><li>Awaiting signature</li><li>Rejected</li><li>Signed</li><li>Expired</li></ul></td><td>Metadata tags inside the file details</td></tr></tbody></table>

{% hint style="info" %}
Note: For more examples of label taxonomies, see [Google Workspace Admin Help](https://support.google.com/a/answer/9292382?hl=en\&ref_topic=13128179\&sjid=15599342535937119335-EU#examples).
{% endhint %}

## How many labels can a file have?

Only Google admins can configure labels.

* You can configure one unique badge with several values to apply across your Google Drive files. One badge value can be applied to each Google file.
* You can configure 149 structured labels, where each one contains fields and values.
* Labels can be applied to any file in Drive, but not to folders, shortcuts, shared drives, or files owned by another organization.
* A label can contain up to 10 fields. DLP rules only support fields of the Options type.
* You can apply labels either manually or automatically via DLP rules:
  * Files can have up to 5 user-applied labels.
  * You can apply up to 20 labels in total to a single file, including user-applied and rule-applied labels.

## Set up Google Drive labels

As a Google administrator, you can create labels to apply to files stored in your organization’s Google Drive. There are several ways to create and apply Google Drive labels:

* [Manual](https://apps.google.com/supportwidget/articlehome?hl=en\&article_url=https%3A%2F%2Fsupport.google.com%2Fa%2Fanswer%2F13127870%3Fhl%3Den\&assistant_id=generic-unu\&product_context=13127870\&product_name=UnuFlow\&trigger_context=a) - After a Google admin creates labels, end users with edit access can manually apply labels to files as necessary.
* [Data loss prevention (DLP) rules ](https://apps.google.com/supportwidget/articlehome?hl=en\&article_url=https%3A%2F%2Fsupport.google.com%2Fa%2Fanswer%2F13127870%3Fhl%3Den\&assistant_id=generic-unu\&product_context=13127870\&product_name=UnuFlow\&trigger_context=a)- Google admins can define DLP rules to automatically apply labels to the entire Google Drive estate.
* [Vault retention rules](https://support.google.com/vault/answer/7657465?fl=1\&sjid=12308467716317648070-NA) - Google admins can define Drive retention rules that can add labels, using fine-grained retention policies and configurable label conditions.
* [AI classification](https://apps.google.com/supportwidget/articlehome?hl=en\&article_url=https%3A%2F%2Fsupport.google.com%2Fa%2Fanswer%2F12676216%3Fhl%3Den\&assistant_id=generic-unu\&product_context=12676216\&product_name=UnuFlow\&trigger_context=a) - This new method (in beta) allows Google admins to define data training resulting in automatic classification and label creation powered by AI.

{% hint style="info" %}
Note: You can also use the [Labels API ](https://developers.google.com/drive/labels)to create, edit, apply, and remove labels programmatically.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docontrol.io/docontrol-user-guide/best-practices/google-labels/google-drive-labels.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.