English
Admin and users
These settings control whether the console can self-register, whether new admins start locked, whether users are auto-assigned, and how long to wait after a withdrawal is approved before paying out.
For partner environments, keep self-registration off and lock-after-register on.
Administrator registration
| Field | Value |
|---|---|
| Admin name | Administrator registration |
| Key | admin.register.enabled |
| Control | Switch |
| Format | On / off |
| Example | On in seed data; turn off for partner use |
What it does
When on, the Admin login page shows Register. Anyone who knows the URL can apply with an email.
When off, only existing admins can create accounts under Administrators → Admin accounts.
Impact
- On exposes the console to self-service signup. Keep it off in production and partner deployments.
- Even if on, whether the new account can sign in still depends on lock-after-register.
- Turning it off does not delete existing admins.
Lock Account After Admin Registration
| Field | Value |
|---|---|
| Admin name | Lock Account After Admin Registration |
| Key | admin.register.locked |
| Control | Switch |
| Format | On / off |
| Example | On |
What it does
Applies to self-registered admins only. When on, the new account is locked and cannot sign in until an existing admin unlocks it and assigns a role.
Accounts created by an admin in the list are not auto-locked by this setting (you can still lock them when creating).
Impact
- Registration on and this off: a stranger may enter the console immediately (depending on the default role). High risk.
- Recommended: registration off. If you must allow registration, this must stay on.
- Unlock locked accounts in the admin account list.
Auto Assign Manager For Unassigned Users
| Field | Value |
|---|---|
| Admin name | Auto Assign Manager For Unassigned Users |
| Key | manager.auto.assign.enabled |
| Control | Switch |
| Format | On / off |
| Example | Off |
What it does
When on, a scheduled job assigns platform users who have no owner to an eligible admin.
Eligible admins belong to a role with Distribute enabled. The job prefers the admin who currently owns the fewest users.
When off, assignment is only manual under Administrators → User assignment.
Impact
- Before turning it on, check which roles have Distribute. If super-admins have it, new users may land on them.
- Useful when you have a CS or review team. Leave it off if ownership is unclear.
- Users already assigned by hand are not reassigned.
User Withdraw Protection Duration
| Field | Value |
|---|---|
| Admin name | User Withdraw Protection Duration |
| Key | user.withdraw.protection.duration |
| Control | Slider |
| Format | 0 or a positive integer |
| Unit | Minutes |
| Example | 24 (24 minutes) |
What it does
After an admin approves a withdrawal, the order becomes Waiting withdraw. Payout is not sent yet. The system waits this many minutes. Only “waiting withdraw” on-chain orders older than that window enter automatic payout.
Use the window to stop stolen-account withdrawals, address changes, or a mistaken approval. Cancel or block the order before the wait ends.
How to fill it
Enter minutes. For a 2-hour wait, enter 120, not 2.
0 means the order can enter automatic payout as soon as the payout job sees it.
Impact
- Too short: no time to stop a bad payout.
- Too long: honest users wait, support tickets rise.
- This only delays automatic payout of already-approved “waiting withdraw” orders. It does not auto-approve “under review” orders.