User access tokens

## What are User Access Tokens?

User Access Tokens are the preferred way to authenticate an application or notebook to Hugging Face services. You can manage your access tokens in your [settings](https://huggingface.co/settings/tokens).

<div class="flex justify-center">
<img class="block dark:hidden" src="https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/hub/User-Access-Token.png"/>
<img class="hidden dark:block" src="https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/hub/User-Access-Token-dark.png"/>
</div>

Access tokens allow applications and notebooks to perform specific actions specified by the scope of the roles shown in the following:

- `read`: tokens with this role can only be used to provide read access to repositories you could read. That includes public and private repositories that you, or an organization you're a member of, own. Use this role if you only need to read content from the Hugging Face Hub (e.g. when downloading private models or doing inference).

- `write`: tokens with this role additionally grant write access to the repositories you have write access to. Use this token if you need to create or push content to a repository (e.g., when training a model or modifying a model card).

Note that Organization API Tokens have been deprecated: 

<div class="flex justify-center">
<img class="block dark:hidden" src="https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/hub/API-token.png"/>
<img class="hidden dark:block" src="https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/hub/API-token_dark.png"/>
</div>

If you are a member of an organization with read/write/admin role, then your User Access Tokens will be able to read/write the resources according to the token permission (read/write) and organization membership (read/write/admin).

## How to manage User Access Tokens?
The context provides a clear explanation of the purpose of User Access Tokens in Hugging Face services. It states that these tokens are used to authenticate applications or notebooks to Hugging Face services. Additionally, it explains the specific actions that can be performed with these tokens, such as reading or writing to repositories, based on the roles assigned to the tokens. The context also mentions the deprecation of Organization API Tokens, which further clarifies the current use of User Access Tokens. Overall, the context provides sufficient information to answer the question unambiguously.


The question about the purpose of User Access Tokens in Hugging Face services is quite useful for machine learning developers working with the Hugging Face ecosystem. Understanding User Access Tokens is essential for developers as these tokens are crucial for authentication and authorization when accessing Hugging Face's APIs and services. This knowledge helps developers manage permissions, secure their applications, and integrate seamlessly with Hugging Face's platform, which is a common requirement in NLP application development.


The question "What is the purpose of User Access Tokens in Hugging Face services?" is context-independent because it clearly asks about the function or role of User Access Tokens within the specific framework of Hugging Face services. It does not rely on any additional context or specific document to be understood. An operator with access to Hugging Face documentation would be able to understand and answer this question without needing further information.

