> 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/create-labels.md).

# Create labels

As a Google admin, you can [create and manage](https://support.google.com/a/answer/13127870?hl=en) Google Drive labels in Google Drive. You can create up to 150 labels, including one badged label. Each label can have up to 10 fields.

{% hint style="success" %}
For example, a **Department** label can have a field with a list of options such as Finance, Engineering, HR, and Legal.
{% endhint %}

## Enable label creation

A Google admin first needs to turn on label creation, and then create labels. End users can manually apply these predefined labels to files as necessary. This method allows end users to classify files on-the-go, but it’s not scalable and prone to classification inconsistencies.

{% hint style="warning" %}
For users to apply labels to files in your organization’s Google Drive, a Google admin first needs to [enable](https://support.google.com/a/answer/13127868?sjid=17684973744186951761-EU) this feature.
{% endhint %}

1. In **Google Admin Console**, go to **Apps > Google Workspace > Drive & Docs**.
2. Under labels, select **Turn labels on**, and click **Save**.
3. Continue to the next step: [Add labels](#add-labels).

## Add labels

Google admins can create labels in Labels Manager.

{% hint style="warning" %}
**Prerequisite**: Make sure you have the [Manage Labels](https://support.google.com/a/answer/1219251#drive_and_docs) privilege that allows Google admins to create custom label types for Drive files and folders.
{% endhint %}

1. In Google Drive, go to [Labels Manager](https://drive.google.com/labels).
2. Follow [these steps](https://support.google.com/a/answer/13127870?hl=en) to create a new label.
3. Optionally, add fields to a label. You can add up to 10 fields to standard labels to allow more granular classification.
4. Define who can view or use a label. By default, everyone in your organization can view and apply labels. You can edit label permissions to control who can view, apply, edit field values, and search by the label.
5. Publish a label. New labels are created as a draft so you can review how your label will appear to users before publishing.
6. Continue to the next step: [Apply labels automatically](/docontrol-user-guide/best-practices/google-labels/google-drive-labels/apply-labels-automatically.md).


---

# 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/create-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.