Skip to content

Organizations and users

A superadmin administers the whole instance. The first one is created from the MLSUITE_SUPERADMIN_* settings when the API starts (see configuration); others are promoted on the Users page.

A superadmin:

  • acts as Owner in every organization, without being a member, and sees every organization in the switcher;
  • sees the Administration group: Organizations, Users, Moderation, API traffic and Infra;
  • has invitations accepted on the spot.

Other accounts that open these pages get “Not found”.

Organizations lists every organization with its counts of models, schemas, plugins, inferences and members. Search by name, slug or description; sort by latest updated, latest created or name. Each organization’s menu offers Edit name, Edit slug, Edit description, Transfer owner and Delete; deletion succeeds only for an empty organization.

New organization creates one:

Field Rule
Name Required, up to 150 characters.
Slug Filled from the name until edited; up to 120 characters, unique.
Owner Any account; defaults to you.
Description Optional, up to 600 characters.

The new organization gets the built-in roles.

Users lists every account with its system role (User or Superadmin), whether it is enabled, and when it was created. Search by name or email, filter by role, and sort by name, newest or oldest.

New user creates an account with an email, full name, password (10 to 128 characters) and role. It is enabled at once and gets a personal organization.

Each user’s menu offers:

Action Effect
Change password Set a new password. This is how users who forgot theirs get back in.
Change role Make the account a User or a Superadmin.
Disable user / Enable user A disabled account cannot sign in. Applies at once.
Delete Remove the account, if nothing else refers to it. Accounts that created models, runs or other records cannot be deleted; disable them instead.

The last enabled superadmin cannot be demoted, disabled or deleted.