Skip to content

Managing users

The Users & Groups surface is your organization’s roster and group directory. Its Team roster section is where you review every account, change a user’s role, activate or deactivate access, and start account recovery when someone is locked out.

The Users & Groups surface listing organization members with name, email, role, and status columns, plus a row action menu.
Users & Access → Users & GroupsCitadel synthetic data on a non-production Arbitex demo instance. Never client data.
  1. Open Users & Access → Users & Groups in the admin console and use its Team roster section. The roster loads with name, email, role, and status for every account.

  2. Use the search box to filter by name or email. The table paginates on the client, so large orgs stay responsive.

  3. To change someone’s role, open the row’s action menu and pick a new role (for example, Member → Admin). The change takes effect immediately.

  4. To suspend access, toggle the account’s status to inactive. An inactive user cannot sign in or call the API, but their history and group memberships are preserved.

  5. If a user is locked out, choose Send recovery from the row menu to start the self-service account recovery flow. Arbitex emails them a recovery link.

The Users panel is backed by the admin users API (control plane). All calls require the admin role.

List the roster (offset-paginated; the backend caps limit at 100):

Terminal window
curl -X POST "https://admin.arbitex.ai/api/v1/admin/users?limit=100&offset=0" \
-H "Authorization: Bearer $ADMIN_TOKEN"
# → { "items": [ { "id": "...", "email": "...", "role": "member", "is_active": true } ], "total": 42 }

Change a user’s role:

Terminal window
curl -X POST "https://admin.arbitex.ai/api/v1/admin/users/$USER_ID/role" \
-H "Authorization: Bearer $ADMIN_TOKEN" \
-H "Content-Type: application/json" \
-d '{"role": "admin"}'

User management is available on every plan. The maximum number of active users is governed by your plan’s seat count; when you reach it, inviting or activating a user surfaces an upgrade prompt in the console.

On a Hybrid Outpost, the roster is served from the org’s control-plane database. In an air-gapped deployment, recovery emails are not sent automatically — the console shows the recovery link so an admin can deliver it through an approved internal channel.