Teams that keep authentication inside Open WebUI can manage local accounts without an identity provider. An administrator can create a user directly, so onboarding one person does not require opening public registration.

An existing administrator account and enabled local password sign-in are required. The admin-side Add User form creates the account immediately; it does not depend on a public sign-up request or a Pending approval.

User provides standard access subject to the instance's model and resource permissions. Admin grants system-wide control, so routine team accounts should use User.

Steps to create an Open WebUI user:

  1. Open the user menu in your administrator session.
  2. Select Admin Panel.

    The panel opens on Users, with the existing accounts listed under Overview.

  3. Click Add User.
  4. Set Role to User.

    Admin gives the account control over users and global settings; it is unnecessary for ordinary workspace access.

  5. Enter the person's display name in Name.
  6. Enter the person's sign-in address in Email.
  7. Enter a unique temporary password in Password.

    The initial password gives access to the account and should reach the recipient through a private credential channel. When password changes are enabled, the recipient can replace it under Settings → Account → Password → Change Password; creation does not force a password change at first sign-in.

  8. Click Save.
  9. Confirm the new email address appears with the User role in the users table.
  10. Open your Open WebUI address in a separate private browser window.

    The separate session leaves the administrator signed in while the new account is tested.

  11. Enter the new account's email address in Email.
  12. Enter its temporary password in Password.
  13. Click Sign in.
  14. Confirm the chat workspace greets the new user by name.

    The workspace confirms account access. Available models still depend on the instance's connections and permissions. A Pending activation screen means the account does not yet have the intended User role.

Share this guide