Skip to content

User Management ​

Updated: 10/15/26, 5:44:21 PM

User management maintains the system's login accounts. Menu path: System Management → Permissions → User Management.

This page manages accounts of the "operations" client; merchant accounts have two entries — operations-side managed administration in Merchant Workbench → Merchant Users, and the accounts themselves can also be queried and handled (ban, password reset, etc.) on this page from the "Merchant Panel" tab.

Page Structure ​

The list is topped by client tabs (Operations / Merchant Panel, generated dynamically from client master data), defaulting to Operations. Both tabs offer identical capabilities; this page uses the operations side as the example.

  • Query conditions: name, account, status (normal / locked / banned), email
  • List columns: name, account, email, client, status, password expiry time, initial-password flag, creation time

Accounts with an orange "initial password" flag have not yet changed the admin-set/generated password and are forced to change it at first login.

Creating a User ​

Action: "New" in the toolbar. Form fields:

FieldRequiredDescription
NameYes3-15 characters
AccountYes6-20 characters; letters, digits, _, - only; duplicate check in real time as you type
Password / confirm passwordNoLeave empty to auto-generate a random initial password per the password policy; if filled in, both entries must match

After a successful save, the dialog switches to a result state showing the account and initial password in plain text (one-click copy) — the initial password is displayed only this once; forward it to the user immediately.

Role Assignment ​

Action: row "More → Assign role". It is currently single-role: the dialog lists assignable roles as single-select cards; select and save to take effect.

The role determines which menus the account can see and which actions it can perform after login; see Permissions and Menu Management for creating and adjusting roles and assigning menus and permission codes.

Edit and Details ​

  • Edit: only the name can be changed; the account is immutable and email is read-only (changes require the user's own verification flow in the Profile). If a user's email is dead and cannot be self-unbound, the admin can clear it with "Force unbind email" on the edit page (a managed-administration channel — use with care);
  • View: the details drawer includes roles, last login time and IP, login count, password expiry time, whether the password is initial, etc.;
  • Third-party bindings (More → Third-party bindings): view the user's bound third-party platform accounts; admins can only unbind, never bind on behalf.

Batch Operations ​

Select multiple rows and run from the toolbar's "Batch operations": batch ban / batch unlock / batch password reset (disabled with no selection). Batch password-reset results come as a table that can be "Copy all" for distribution.

Built-in super admin cannot be touched

The built-in super admin (administrator) cannot be edited, assigned roles, or banned; its identity column shows a gold "built-in super admin" tag. Day-to-day operator accounts should get their own role assignments instead of sharing the super admin.

Password Reset ​

Action: row "More → Reset password", or select multiple rows for a batch reset.

  • Reset does not accept a specified new password: the system generates one randomly per the password policy, and the result page shows the plain text once (a table for batches, with "Copy all").
  • After a successful reset, all of the user's login sessions are immediately forced offline; they must log in again with the new password.
  • The reset password counts as an initial password; the user is asked to change it at next login.

Account Status and Lockout ​

There are two "locks" in the system; when troubleshooting login issues, first tell them apart:

MechanismHow it triggersWhere to viewHow to release
Account status (normal / locked / banned)Set manually by an admin"Status" column of the user listRow "More → Unlock" restores normal
Login failure lockoutLocks automatically for a while after consecutive wrong passwords reach the threshold (threshold and duration switches in the configuration guide)System Management → System Monitoring → Locked Users (with failure count and remaining lock time)Auto-unlocks at expiry, or unlock manually on the Locked Users page (which also resets the failure count)

The "Unlock" action clears both locks; "Ban" is an explicit login denial that requires manual restoration.

Merchant users and merchant status

When a merchant-panel account cannot log in, beyond the account's own locks it may be that the merchant is disabled (when the merchant's status is disabled in its profile, none of the merchant's accounts can log in; see Merchant Management).