Open WebUI user roles determine whether an account can reach the chat workspace and shared resources. Moving a standard user back to Pending withdraws that access while retaining the account for review or later reactivation.
The role selector under Admin Panel → Users changes the account's system role. Pending restricts workspace access, while Sign out all devices separately revokes existing browser sessions and requires a new sign-in.
This method applies to locally managed accounts on a self-hosted instance. For SSO or SCIM managed users, the identity provider remains the source of truth for offboarding; a local role change does not replace its account lifecycle policy.
Steps to disable an Open WebUI user:
The starting point is an administrator session, with a separate browser session for testing the target account. The account holder can perform the sign-in check without sharing their password.
- Open the user menu in your administrator session.

- Select Admin Panel.
The panel opens directly on Users → Overview.
- Confirm the target account has the User role.
Changing an administrator's role can cause lockout. A separate known administrator must remain active. Returning the target account to User later restores workspace access, but revoked browser sessions still require a new sign-in.
- Click the target account's role badge to open Edit User.

- Set Role to Pending.

- Click Save to disable the user's workspace access.
The saved Pending role keeps the user record and history. It does not invalidate existing browser tokens; session revocation is a separate action.
- Reopen Edit User through the target account's Pending badge.

- Click Sign out all devices.
Confirmation ends the target user's browser sessions. API keys remain stored; Pending blocks their access to protected model and chat routes, but restoring User can make those keys usable again. Permanent key retirement requires deleting or replacing the key separately.
- Click Confirm to revoke the target user's sessions.

- Reload the target user's previously open browser tab.
The old session should return to Sign in rather than the workspace. The saved role and session revocation serve different purposes; signing out alone does not disable an account.
- Open your Open WebUI address in a separate private browser window.

- Enter the disabled account's email address in Email.

- Enter its password in Password.

- Click Sign in.

- Confirm the disabled account cannot enter the chat workspace.
With MFA disabled, Account Activation Pending appears after the password is accepted. With MFA enabled, the account stays on the sign-in page with Your account is awaiting administrator approval. and no session is issued. Both results reflect the Pending role rather than an incorrect password.
- Close Edit User in your retained administrator window.

- Confirm the administrator's Users table retains the target's Pending row beside your Admin account.
