# Authentication (https://depot.dev/docs/cache/authentication)

Depot Cache supports authenticating with **user** tokens and **organization** tokens. Additionally, [Depot GitHub Actions runners](/docs/github-actions/overview) are pre-configured with a token that is active for a single job, which is set as environment variable called `DEPOT_CACHE_TOKEN`.

Project tokens are **not** supported for Depot cache because only [container builds](/docs/container-builds/overview) use projects.

## Token types

* **User tokens** are used to authenticate as a specific user and can be generated from your [user settings](/settings) page.

* **Organization tokens** are used to authenticate as an organization. These tokens can be generated from your organization's settings page.

* **Depot GitHub Actions runners** are pre-configured with a token that is active for a single job (`DEPOT_CACHE_TOKEN`). If you are using the automatic Depot Cache integration with Depot runners, you do not need to manually configure authentication.

## Configuring build tools

For specific details on how to configure your build tools to authenticate with Depot Cache, refer to the following guides:

* [Bazel](/docs/cache/integrations/bazel)
* [Go](/docs/cache/integrations/gocache)
* [Gradle](/docs/cache/integrations/gradle)
* [Pants](/docs/cache/integrations/pants)
* [sccache](/docs/cache/integrations/sccache)
* [Turborepo](/docs/cache/integrations/turbo)

## For AI Agents

The full site index is at [llms.txt](https://depot.dev/llms.txt). Append `.md` to any documentation, blog, changelog, or customer URL to fetch its markdown source directly.