Open WebUI local accounts let an administrator give someone access to the self-hosted chat workspace without connecting an external identity provider. The local-account path fits small teams, lab systems, and onboarding checks where the account should appear in the admin user list before it can use the application.
The local-account flow creates users through the public sign-up form and administrator approval. The administrator can temporarily enable new sign-ups, let the person register with a temporary password, and then promote the pending account from Admin Panel → Users.
The User role grants standard workspace access, while Admin gives system-wide control. Use Pending as the approval state, keep administrator accounts separate from normal user testing, and add group or resource permissions only after the account can sign in.
Related: How to create an RBAC group in Open WebUI
Related: How to disable a user in Open WebUI
Leave sign-ups enabled only for the account request window on private instances. Anyone who can reach the sign-up page can request an account while this setting is on.

If Default User Role is set to User, the account may skip the pending state. Keep pending for approval-controlled onboarding.
Use Admin only for people who should manage global settings, users, providers, tools, and system configuration.

Disable Enable New Sign Ups again if registration was opened only for this account.
Related: How to disable signup in Open WebUI