Adding a User

Creating a user creates a full hosting account: the panel login, the Linux system user and the plan-governed limits all come from this one form. The same form, pre-filled, is also the user edit page.

Account Information

• Username: lowercase letters, digits and underscores, up to 32 characters, with a live character counter and progress bar. The Linux system username is derived from it server-side and shown in the success message.
• Email: required, format-checked.
• Password: required on create (optional when editing; leave empty to keep the current one). Strength is scored by the server as you type: a colored bar with a 0-100 score and label, plus a live requirements checklist (minimum length, lowercase, uppercase, digit, special character) driven by the panel's password policy. There is no generate button here; the password is typed in and confirmed.
• Full Name: optional.

User Settings

• Role: which roles you can grant depends on three things at once: your own role (ROOT can create ADMIN and RESELLER; ADMIN can create RESELLER; everyone with the permission can create USER), your license (roles outside the license show as locked and open an upgrade dialog instead of being selected), and your permission keys. A RESELLER does not see the selector at all: an info notice explains resellers create USER accounts only.
• IP Addresses: at least one server IP must be assigned, from a multi-select of available addresses. The list is scoped: a RESELLER only sees IPs that belong to them.

Service Plan

A required plan selection, preloaded with the server's default plan. Picking a plan unfolds a summary so you know what you are handing out: the numeric limits (domains, disk, bandwidth, databases, email accounts, subdomains, FTP accounts, cron jobs, with "Unlimited" where the plan says so) and the access flags (SSH with its level, FTP, MySQL, cron, SSL, backup) as check or cross marks.

For ADMIN and RESELLER a Remaining Resources box shows their own leftover quota (users, CPU, memory, disk), and if the selected plan would not fit into it the form lists the conflicts and disables the create button; the server enforces the same limits regardless.

What happens on create

Submit validates the form, creates the account and returns you to the user list with a toast that includes the generated system username. There is no separate credentials screen: the password is the one you just typed, so store it before leaving the page if the customer needs it.

Editing users

The edit page (/users/edit/ID) is this same form with the values loaded; the username cannot be changed (edits to that field are not applied) and the password only changes if you type a new one. For ROOT, editing adds the Permissions tab with per-user page and feature overrides, described on the User Management page.