Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fix broken fragment link to #operator-token (#6609) 

* Initial plan

* Change token type headings from h4 to h3 to fix fragment detection

Changed heading levels for Operator token, All Access token, and Read/Write token from level 4 to level 3. This ensures better compatibility with link checkers that may have issues detecting fragments in h4 headings.

Co-authored-by: jstirnaman <212227+jstirnaman@users.noreply.github.com>

* fix(v2): Clarify operator token auto- vs manual- generation

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: jstirnaman <212227+jstirnaman@users.noreply.github.com>
Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>
pull/6630/head^2
Copilot 2025-12-16 13:04:34 -06:00 committed by GitHub
parent c681491423
commit db6a96fc39
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 23 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
content/influxdb/v2/admin/tokens/_index.md
View File

@ -24,25 +24,37 @@ Learn how to create, view, update, or delete an API token.
- [All Access API token](#all-access-token)
- [Read/Write token](#readwrite-token)
#### Operator token
### Operator token
Grants full read and write access to **all organizations and all organization resources in InfluxDB OSS 2.x**.
Some operations, e.g. [retrieving the server configuration](/influxdb/v2/reference/config-options/), require operator permissions.
Operator tokens are created in the InfluxDB setup process.
Some operations--for example, [retrieving the server configuration](/influxdb/v2/reference/config-options/)--require _operator_ permissions.
#### Initial operator token
When you first initialize {{% product-name %}}, the [setup](/influxdb/v2/get-started/setup/) process creates an initial user, org, bucket, and an Operator token with full read/write access to all organizations.
When running setup, you can either:
- Supply the token value yourself ([`influx setup --token` flag](/influxdb/v2/reference/cli/influx/setup/) or the [setup API](/influxdb/v2/api/v2/#tag/Setup) `token` field), or
- Let InfluxDB auto-generate it. InfluxDB stores the generated token in the active influx CLI config so the CLI can use it later.
#### Creating operator tokens after setup
To [create an operator token manually](/influxdb/v2/admin/tokens/create-token/) with the InfluxDB UI, `api/v2` API, or `influx` CLI after the setup process is completed, you must use an existing [Operator token](/influxdb/v2/admin/tokens/#operator-token).
To create a new Operator token without using an existing one, see how to use the [`influxd recovery auth`](/influxdb/v2/reference/cli/influxd/recovery/auth/) CLI.
{{% note %}}
Because Operator tokens have full read and write access to all organizations in the database,
we recommend [creating an All Access token](/influxdb/v2/admin/tokens/create-token/)
for each organization and using those to manage InfluxDB.
This helps to prevent accidental interactions across organizations.
{{% /note %}}
> [!Tip]
> Because Operator tokens have full read and write access to all organizations in the database,
> we recommend [creating an All Access token](/influxdb/v2/admin/tokens/create-token/)
> for each organization and using those to manage InfluxDB.
> This helps to prevent accidental interactions across organizations.
### All Access token
#### All Access token
Grants full read and write access to all resources in an organization.
#### Read/Write token
### Read/Write token
Grants read access, write access, or both to specific buckets in an organization.
{{< children hlevel="h2" >}}