From afcf572c43afba8ed6dd20c27e470b854d36081d Mon Sep 17 00:00:00 2001 From: Morgan Helton Date: Tue, 4 Aug 2026 16:31:53 -0500 Subject: [PATCH] docs(organizations): remove machine access tokens section The section documented an Auth0 client-credentials flow that required contacting Flox for a client ID and secret. Service accounts cover the same org-owned, non-interactive access and are created in FloxHub by organization owners. Point the Imageless Kubernetes token-expiry note at service accounts, which was the only inbound link to the removed section. Co-Authored-By: Claude Opus 5 (1M context) --- concepts/organizations.mdx | 18 ------------------ imageless-kubernetes/config.mdx | 2 +- 2 files changed, 1 insertion(+), 19 deletions(-) diff --git a/concepts/organizations.mdx b/concepts/organizations.mdx index aba59f0..4531e68 100644 --- a/concepts/organizations.mdx +++ b/concepts/organizations.mdx @@ -36,24 +36,6 @@ A [service account](/concepts/service-accounts) is an identity your automation s Only owners can create service accounts and issue their tokens. See [Service accounts](/concepts/service-accounts) for how to set one up and how to rotate its tokens. -## Machine Access Tokens - -In addition to _user-level_ access based on FloxHub accounts, FloxHub supports _programmatic_ access via `Auth0`-issued machine tokens, using the client credentials grant. These tokens are not tied to users—they authenticate as the organization itself and are intended for CI/CD or other non-interactive use cases. - -FloxHub supports this via the client credentials grant. To enable it, contact the Flox team to request a client ID and secret. Once provisioned, your workflows can fetch an access token using a `curl` command: - -```bash -curl --request POST \ - --url https://auth.flox.dev/oauth/token \ - --header 'content-type: application/x-www-form-urlencoded' \ - --data "client_id=YOUR_CLIENT_ID" \ - --data "client_secret=YOUR_CLIENT_SECRET" \ - --data "audience=https://hub.flox.dev/api" \ - --data "grant_type=client_credentials" -``` - -The token can be used to authenticate calls to FloxHub’s API or CLI tools in the context of your organization. - ## Environment Visibility and Management Organizations in FloxHub include a view of all environments and packages owned by the organization. diff --git a/imageless-kubernetes/config.mdx b/imageless-kubernetes/config.mdx index 203d448..ad7b7d9 100644 --- a/imageless-kubernetes/config.mdx +++ b/imageless-kubernetes/config.mdx @@ -24,7 +24,7 @@ flox auth token \ **Token expiry** - Tokens generated with `flox auth token` are associated with your user account and will expire 1 month from when they were issued. For a more robust alternative see [Machine Access Tokens for Organizations](/concepts/organizations#machine-access-tokens). + Tokens generated with `flox auth token` are associated with your user account and will expire 1 month from when they were issued. For a token that belongs to your organization rather than to you, and that you can issue with a longer lifetime, see [Service accounts](/concepts/service-accounts). **Flox CLI version**