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: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 invitation is bound to that email address. The recipient opens the link, then creates an account or signs in with the
matching email. Invitations continue to work while public signup is disabled. 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 do not 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
airmux users list provides account IDs; select the organization
and workspace context first:
airmux workspaces members remove "$USER_ID" --workspace production. Remove an
organization membership with airmux orgs members remove "$USER_ID". Removing membership also revokes that person’s
inference keys and sessions in the affected scope.
Disable public signup
SetAIRMUX_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: