Skip to main content

Create the first account

The first human account claims the instance and becomes its owner. From the webapp, choose Create account, or use the CLI during setup:
After the instance is claimed, public signup is disabled by default. Setup guides you through adding provider keys and creating your first organization. You can pause and resume later.

Invite a person

In the webapp, open the organization and go to Settings → Members → Invite by email. Enter the person’s email, choose an organization role, and optionally choose a workspace and workspace role. Create the invitation, copy its link, and send it through a trusted channel. airmux does not send the email for you. The CLI also creates invitations and prints the link once:
Use the workspace ID from airmux workspaces list. Reissuing invalidates the previous link. The CLI does not send email. The invitation is bound to that email address. The recipient opens the link, then creates an account or signs in with the matching email. From the same Members page, you can review, reissue, or revoke pending invitations. To create an account for automation, create a service account from organization settings or run airmux service-accounts create. Service accounts are machine identities and can’t sign in to the webapp.

Assign roles

Roles grant access at different scopes: Change roles in the webapp:
  • Instance roles: Instance → Users → select a user
  • Organization roles: Organization → Settings → Members
  • Workspace roles: Workspace → Settings → Members
You can also manage existing memberships with the CLI. airmux users list provides account IDs; select the organization and workspace context first:
Remove a workspace membership with airmux workspaces members remove "$USER_ID" --workspace production. Remove an organization membership with airmux organizations members remove "$USER_ID". Removing membership also revokes that person’s inference keys and sessions in the affected scope.

Disable public signup

Set AIRMUX_PUBLIC_SIGNUP=false for the control plane. Docker Compose defaults this setting to false; set it explicitly in .env if it was previously enabled, then recreate the services:
Then apply it to the deployment:
For other deployment types, set the same environment variable on the control-plane process. See the configuration reference. Disabling public signup does not revoke existing accounts or invitations.