---
title: Reassign a token
description: Reassign an API token from one user to another in Telegraf Controller.
url: https://docs.influxdata.com/telegraf/controller/tokens/reassign/
estimated_tokens: 1521
product: Telegraf
version: v1
---

# Reassign a token

#### Telegraf Controller is in Public Beta

Telegraf Controller is in public beta and will be part of the future Telegraf Enterprise offering. While in beta, Telegraf Controller is **not meant for production use**. The Telegraf Controller documentation is a work in progress, and we are actively working to improve it. If you have any questions or suggestions, please [submit an issue](https://github.com/influxdata/docs-v2/issues/new?labels=Telegraf%20Controller). We welcome any and all contributions.

Beta expectations

-   **No configuration or agent limits**  
    While in beta, Telegraf Controller doesn't place any limits on the number of configurations you can store or the number of Telegraf agents you can track. However, upon being generally available, the free distribution of Telegraf Controller will have limits introduced, with the option to increase limits through a Telegraf Enterprise license.
-   **Potential breaking changes**  
    While in beta, we will do our best to no longer make breaking changes to Telegraf Controller, however, they may be necessary. The majority of changes we make will be additive and non-breaking, and include any necessary migrations. When we do need to make breaking changes, we will do our best to communicate them clearly and in advance to minimize disruption.
-   **Flexible release schedule**  
    While in beta, we will continue to create new releases of Telegraf Controller, but likely at irregular intervals. We will provide [Telegraf Controller release notes](/telegraf/controller/reference/release-notes/) to make it easy to track updates.

Provide beta feedback

-   Use the **Feedback** feature in the Telegraf Controller UI.
-   [Join the InfluxDB Community Slack](https://influxdata.com/slack) and post feedback in the **#telegraf-enterprise-alpha** channel.
-   Post feedback in the [InfluxData Community](https://community.influxdata.com).

Join our public channels

-   [InfluxDB Community Slack *(Preferred)*](https://influxdata.com/slack)
-   [InfluxData Community](https://community.influxdata.com)
-   [InfluxDB Subreddit](https://reddit.com/r/influxdb)

Reassigning an API token from one user to another in Telegraf Controller lets you transfer ownership of that token to another user without disrupting any external clients using the token.

#### Required permissions

To reassign an API token, you must have the **Owner** or **Administrator** role in Telegraf Controller.

## Reassign a token

You can reassign an individual token from one user to another directly from the token’s detail view or the tokens list.

1. In Telegraf Controller, navigate to the **API Tokens** page or open the detail page for the token you want to reassign.
2. Click **Reassign** on the token you want to transfer. If on the token detail page, select the **Manage** tab to reveal the **Reassign** action.
3. In the dialog that appears, select the target user you want to assign the token to.
4. Click **Confirm** to complete the reassignment.

When you reassign a token, its permissions are automatically restricted to match the target user’s role. For example, a token with full access reassigned to a Viewer becomes a read-only token.

## Bulk reassign

If you need to reassign multiple tokens at once, use the bulk reassign option.

1. On the **API Tokens** page, select the checkboxes next to the tokens you want to reassign.
2. Click the **Reassign** option in the bulk actions bar.
3. Select the target user you want to assign the selected tokens to.
4. Click **Confirm** to reassign all selected tokens.

The same permission restriction applies during bulk reassignment. Each token’s permissions are adjusted to align with the target user’s role.

## When to reassign

Reassigning tokens lets you transfer ownership without revoking and recreating tokens. This is useful in several common scenarios:

-   **Offboarding a user**: A user is leaving the organization and their tokens should continue working under another account. Reassigning ensures active integrations are not disrupted.
-   **Reorganizing responsibilities**: Team members are shifting roles or responsibilities and token ownership should reflect the new structure.
-   **Consolidating ownership after role changes**: After updating user roles, you may want to consolidate tokens under a single account to simplify token management.

#### Related

-   [Authorization](/telegraf/controller/reference/authorization/)