docs(iam): add Manage API keys page, new management UX - #3060
Conversation
…controls Adds a primary page for API key management covering the consolidated API Keys tab, the key visibility model by role, and the two admin settings that restrict key creation and use. Deployment split verified against wandb/core master and server-release-0.83.x: - requireOrgScopedAPIKeys is Multi-tenant Cloud only, Enterprise non-academic orgs, behind a per-org Statsig gate. - disableApiKeyCreation is Dedicated Cloud and Self-Managed only, new in v0.84.0. - Search, filter, key creation, and bulk delete in the API Keys tab are new for Dedicated Cloud and Self-Managed in v0.84.0. Also disambiguates "organization-scoped API key" from "organization-scoped service account", which the docs already used for a different concept. Refs DOCS-3071, WB-25038, WB-37180 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
No preview available (1)
Updated 2026-08-21 22:59:35 UTC for deployment · 847bc0c. |
Readability impactWord-weighted Flesch-Kincaid grade change across 3 changed pages: +0.0 (unchanged). Lower Flesch-Kincaid grade and higher reading ease both mean easier to read. This check is informational and never blocks a PR. Human readability
AI agent comprehensionRated 0-3 (higher is easier for an agent to parse and act on).
Curated-docs baseline median FK grade by type: conceptual 10.5, procedural 8.8, reference 9.4. |
🔗 Link Checker Results✅ All links are valid! No broken links were detected. Preview: https://wb-21fd5541-docs-3071-org-scoped-api-keys.mintlify.site |
- Give step-wise UI navigation to the API Keys tab for both Multi-tenant Cloud and the onprem Organization Dashboard, reusing the URL patterns already used in org_dashboard.mdx. - Correct the billing admin claim. The tab is hidden for the BILLING_ONLY org role in Multi-tenant Cloud only; the onprem Organization Dashboard renders the tab with no billing guard. - Add a billing admin row to the visibility table. - Add "Rotate an API key". W&B has no single rotate action, so the section documents the create, migrate, verify, delete workflow. - Add "Rename an API key" for the row Edit action. - Replace the inferred single-key delete wording with the actual control: the row actions menu offers Edit and Delete. Refs DOCS-3071 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HiveMind Sessions1 session · 46m · $23
View all sessions in HiveMind → Run |
Product doesn't want to lean into "scope" as a controllable dimension for API keys yet. Reword "organization-scoped API key" to "organization API key" and similar phrasing throughout the new Manage API keys page and its cross-references, while leaving unrelated pre-existing "team-scoped"/"organization-scoped" service account terminology intact. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ud9P2d5HKyfiFhi7bpBD6x
Requested by Matt Linville · Slack thread
Adds a primary Manage API keys page and links the existing API key content to it.
Related: DOCS-3071, WB-25038, WB-37180, DOCS-2902
Why now
What changed
platform/hosting/iam/api-keys.mdxplatform/app/settings-page/user-settings.mdxplatform/hosting/iam/service-accounts.mdxplatform/hosting/iam/advanced_env_vars.mdxGORILLA_DISABLE_TEAM_SERVICE_ACCOUNT_CREATIONto the new page.docs.jsonWhy a new page
The product consolidated key management into one API Keys tab covering personal, organization-scoped, team service account, and organization service account keys under a single visibility model. Our docs split that across user settings (personal) and service accounts (service accounts). The new page matches the product; the existing pages now point at it.
It also gave the terminology problem somewhere to live: the docs already used "organization-scoped" for service accounts, which is a different concept from an organization-scoped API key held by a person.
Deployment split as documented
Derived from
wandb/coremastervsserver-release-0.83.x. Please confirm this table above all else.requireOrgScopedAPIKeysdisableApiKeyCreationReasoning:
showCreateKey = (envIsPublicCloud && canCreateOrgScopedKeys) || !envIsPublicCloud, so create and multi-select are unconditional on onprem, while the search field and filter bar render unconditionally everywhere.useStatsigGateCreateOrgScopedKeysresolves to?? false, so the owner-type column stays hidden on onprem.There is no key rotation action
The row actions menu contains only Edit and Delete, and
EditApiKeyDrawer.tsxedits only the Name field. Nothing regenerates a secret in place.The page therefore documents rotation as a manual create, migrate, verify, delete workflow, and states plainly that both keys work until the old one is deleted.
Note
Per discussion in review, this page covers only the API key management changes that are confirmed and released or on a confirmed timeline. A couple of related items that came up during review are intentionally left out pending confirmation from Product/Eng, and can follow in a later PR once finalized.
Questions for review
API key creation has been disabled by your organization administratormatch what users see?isViewerBillingOnly, unrestricted in the onprem Organization Dashboard. Please confirm, since role behavior can change without anyone treating it as a docs-visible change.