Skip to content

docs(influxdb3-cloud): document managing tokens in the Admin UI - #7939

Open
ritwika314 wants to merge 3 commits into
masterfrom
ritwika/cloud-console-tokens
Open

ritwika314 wants to merge 3 commits into
masterfrom
ritwika/cloud-console-tokens

Conversation

@ritwika314

Copy link
Copy Markdown
Collaborator

Adds Admin UI steps to the Cloud tokens page for creating resource and admin tokens, saving the secret, listing, and deleting tokens.
Each section now has Admin UI and influxdb3 CLI tabs, with five Admin UI screenshots; the CLI content is unchanged.
Co-Authored-By: Claude

@github-actions

Copy link
Copy Markdown
Contributor

Vale Style Check Results

Metric Count
Errors 0
Warnings 0

✅ Check passed

@ritwika314 ritwika314 added the product:v3-distributed InfluxDB 3 Cloud Serverless, Cloud Dedicated, Clustered label Oct 23, 2026
@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

🔗 Link Check Results — Link Check Bot

✅ All links are valid

Metric Value
Files Checked 1
Total Links 165
Errors 0
Warnings 1
Success Rate 98.18182%
⚠️ 1 warning(s) (do not fail CI)
Source File URL Issue
content/influxdb3/cloud/admin/tokens/_index.md https://support.influxdata.com/ Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…

Full details: workflow run summary and artifact. Last updated: 2026-10-29 13:59:51 UTC

@ritwika314 ritwika314 added product:v3-cloud InfluxDB 3 Cloud (hosted Enterprise) and removed product:v3-distributed InfluxDB 3 Cloud Serverless, Cloud Dedicated, Clustered labels Oct 23, 2026
Comment on lines +115 to +116
Admin tokens have full access to the instance.
Use them carefully and don't share them publicly.

@sanderson sanderson Oct 27, 2026 •

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe wrap this in an important block:

Suggested change
Admin tokens have full access to the instance.
Use them carefully and don't share them publicly.
> [!Important]
> Admin tokens have full access to the instance.
>Use them carefully and don't share them publicly.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Applied in 4eed31e as an Important callout inside step 2 (with a space after the second >); the list numbering still renders correctly. (automated follow-up)

Comment thread content/influxdb3/cloud/admin/tokens/_index.md Outdated
@ritwika314
ritwika314 force-pushed the ritwika/cloud-console-tokens branch from 4eed31e to e4c086f Compare October 29, 2026 12:26
Put the admin token warning in an Important callout and say "enable"
for the Show Expired Tokens toggle.

Co-Authored-By: Claude
@ritwika314
ritwika314 force-pushed the ritwika/cloud-console-tokens branch from e4c086f to b69ef18 Compare October 29, 2026 13:57
@ritwika314
ritwika314 marked this pull request as ready for review October 29, 2026 14:07
@ritwika314
ritwika314 requested a review from a team as a code owner October 29, 2026 14:07
@ritwika314
ritwika314 requested review from jstirnaman and removed request for a team October 29, 2026 14:07
@github-actions

Copy link
Copy Markdown
Contributor

📦 PR Preview — Preview Bot

Status Details
Result ✅ DEPLOYED (full site)
Preview View preview
Build time 115s
Last updated 2026-10-29 14:15:06 UTC
Changed pages (1)

Preview auto-deploys on push. Will be cleaned up when PR closes.
The preview's deployed-commit meta tag names GitHub's temporary merge commit for this PR, not a commit on the PR branch.

* docs(influxdb3-cloud): fix token page headings and delete warning

What changed: Promote the Admin UI token-creation subsections from h4 to
h3, add a pointer to "Save the token secret" after the token-type
choice, and move the deletion warning into a Warning callout before the
delete steps.

Why: The h4 subsections skipped a heading level under "Create a token".
Readers creating either token type need to know they must save the
secret. A warning placed after the final step arrives too late to act on.

Impact: InfluxDB 3 Cloud "Manage tokens" page only.

Verification: Code-block lint passes for the page.

* docs(influxdb3-cloud): correct token edit and management token claims

What changed: Change the named admin token bullet from "Can be created,
edited, and deleted" to "Can be created and deleted". Add a callout
that management tokens, listed under Account in the Admin UI, are
account-level tokens separate from instance admin and database tokens.
Replace the closing paragraph that said token management "works the
same way" as Enterprise with links to the Cloud influxdb3 CLI token
reference pages.

Why: The Admin UI has no edit action for instance tokens, and the
token API supports only create, operator-token regenerate, and delete.
The Admin UI shows a separate Management Tokens page that the docs
didn't mention, so readers could confuse it with admin tokens. The
Enterprise token pages cover operator-token regeneration and offline
token files, which don't apply to Cloud.

Impact: InfluxDB 3 Cloud "Manage tokens" page only. What management
tokens authorize is still to be confirmed and documented
(#7664).

Verification: Checked Tokens and Management Tokens action menus in the
Admin UI at console.influxdata.com. Code-block lint passes. The three
linked CLI reference pages exist on this branch.

* Update content/influxdb3/cloud/admin/tokens/_index.md

Co-authored-by: Dustin Eaton <eatondustin1@gmail.com>

---------

Co-authored-by: Dustin Eaton <eatondustin1@gmail.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:v3-cloud InfluxDB 3 Cloud (hosted Enterprise)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants