Skip to content

docs(organizations): remove machine access tokens section #59

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
devusb merged 1 commit into from
Aug 4, 2026
Merged

docs(organizations): remove machine access tokens section #59

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 0 additions & 18 deletions concepts/organizations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion imageless-kubernetes/config.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ flox auth token \
<Note>
**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).
</Note>
<Note>
**Flox CLI version**
Expand Down