Public registration lets visitors request local accounts on an Open WebUI instance. Disabling signup closes that route when access should be limited to existing users and accounts created by an administrator.

The first administrator account normally closes signup automatically. An established instance may have registration enabled again, and its saved setting can take precedence over a later ENABLE_SIGNUP environment-variable change.

Existing local accounts retain password sign-in when Login Form stays enabled. Closing local signup does not remove users, prevent administrator-created accounts, or change the separate OAuth and LDAP provisioning controls.

Keep your working administrator session open until the access checks pass. Disabling Login Form removes local password sign-in, so it must stay enabled. If a signup or sign-in check fails, use the retained session to restore the previous Authentication settings.

Steps to disable signup in Open WebUI:

  1. Open the user menu in your administrator session.
  2. Select Settings.
  3. Select Authentication under Admin.
  4. Disable New Sign Ups.
  5. Click Save.

    The saved change takes effect immediately.

  6. Open your Open WebUI address in a separate private browser window.

    The local form shows Sign in without a Sign up option. Configured SSO or LDAP buttons may still appear.

  7. Check the public configuration endpoint for enable_signup set to false.
    $ curl --silent --show-error "https://openwebui.example.com/api/config" | jq '.features.enable_signup'
    false

    The JSON filter requires jq.

  8. Test the signup endpoint with an unused disposable email address.

    An unexpected successful response can create an account. A disposable address and a unique test password limit the consequences if signup is still enabled.

    $ curl --include --silent --show-error --request POST "https://openwebui.example.com/api/v1/auths/signup" \
      --header "Content-Type: application/json" \
      --data @- <<'JSON'
    {"name":"Blocked Registration","email":"blocked.registration@example.com","password":"<password>"}
    JSON
    HTTP/1.1 403 Forbidden
    ##### snipped #####
    content-type: application/json
    ##### snipped #####
    
    {"detail":"You do not have permission to access this resource. Please contact your administrator for assistance."}

    HTTP 403 with this message means registration was rejected before a new account was created. The HTTP protocol version may differ behind a proxy.

  9. Enter an existing user's email address in Email in the private window.
  10. Enter the account's password in Password.
  11. Click Sign in.
  12. Confirm the existing user's name appears above the chat composer.

    The existing account can still reach the workspace while new local registrations are blocked. The instance's connections and permissions determine which models are available.

Share this guide