Reseller identity, account ownership and limits
Delegate hosting work.
Keep ownership explicit.
Create reseller identities, configure their profiles and organize the hosting accounts they manage. Understand which checks are implemented before treating every displayed limit as an enforced commercial entitlement.
Reseller hosting access and EzePanel commercial subscriptions are separate.
Swipe to inspect · tap the image for full context
- Reseller identity
- Access profile
- Account ownership
- Customer workflow
Three responsibilities
A reseller is not a server-root administrator.
Root administrator
Technical details
Creates and modifies reseller identities, changes profile controls and assigns existing hosting accounts. The current reseller-management pages require root access and CSRF protection for writes.
Reseller
Uses a separate reseller workspace for customer-account work. Account and domain ownership helpers scope supported workflows. This is distinct from unrestricted server administration.
Hosting customer
Uses the User Panel for an individual hosting account. Neither this account nor the reseller identity is the same thing as a subscription customer in the commercial EzePanel portal.
Onboard deliberately
Create the identity, then review the grant.
Create the reseller
Enter username, email, password, company, account-count limit, disk and bandwidth values, and the overselling selection. Username validation accepts 3–64 safe characters beginning with a letter; passwords require at least ten characters.
Review the initial profile
The compact creation path starts the reseller active with its standard management capabilities enabled. Open Modify to review status, permissions and limits before handing over access.
Organize hosting accounts
Assign an existing unassigned account or let the reseller create an account through an eligible package. Review the resulting ownership and provisioning state.
Check the customer workflow
Confirm the intended account appears in the reseller workspace and inspect its actual operation. A profile save or ownership label is not proof that every delegated permission and quota behaves as intended.
Modify Reseller field map
Know what the profile records.
- Login and identity
- Email, optional replacement password, company and branding name. Leaving the password blank preserves it. A branding-name field alone does not establish a complete white-label product.
- Status
- Active, Suspended or Disabled. The profile updates the reseller administrator’s active flag; this is not the same operation as suspending every hosted website.
- Limits
- Maximum accounts, disk, bandwidth, email, database, FTP and domain values, plus an overselling flag. Zero is displayed as unlimited for some fields; it does not mean unlimited physical server capacity.
- Capabilities
- Account creation, DNS, SSL, email and database access switches. Stored switches must be distinguished from actual enforcement; the current limitations are explained below.
- Owned accounts
- Account identity, domain, status and quota values, with Assign and Unassign actions. The listing also shows reseller counts and last-login information. The current screen does not offer a reseller-delete action.
Customer account creation
Provisioning starts after the checks.
The reseller creation route checks active status, permission to create accounts and a positive maximum-account limit. It also validates the customer identity, unique primary domain, eligible active package and installed PHP runtime before queuing provisioning.
Queued account work
The account begins in provisioning state, its primary domain begins pending and a background account-provision job is recorded. A successful submission is not yet a healthy Linux account, working website or issued certificate.
Package versus reseller allocation
The selected package supplies customer-account quotas and features. Those account limits are distinct from aggregate reseller allocation fields. Do not infer enforcement of the entire reseller budget from one account’s package values.
Current enforcement boundary
Stored policy is not always an enforced limit.
- Account creation checks
- The current reseller account-creation path checks active status, the creation capability and the configured account-count ceiling. Concurrent requests still require operational oversight.
- Aggregate allocation limits
- Aggregate disk, bandwidth and other allocation fields are stored in the profile. Treat them as planning values rather than hard admission limits; monitor aggregate usage separately.
- Capability switches need verification
- DNS and SSL workflows check account ownership. Their profile switches should not be relied on as independent access restrictions. Review the effective reseller access before delegation.
- Unassign is not universal revocation
- Some ownership helpers consider more than one ownership relationship. Removing the reseller assignment alone is not proof that all remaining access relationships have been removed. Review the effective ownership before treating a transfer as complete.
Changes and failure handling
Recheck after a partial failure.
Profile and login updates run sequentially. If a later validation or notification fails, earlier changes may already exist. Reopen the profile and inspect the actual saved state before repeating an operation. Password replacement calls the panel’s administrator-session revocation service; it is not a reset of customer hosting-account passwords.
Does suspending a reseller suspend its websites?
The current profile update changes reseller access state, not every account’s hosting status. Treat account suspension as a separate workflow.
Are all displayed limits commercially enforced?
No such blanket claim is supported. Account-creation checks exist, while aggregate allocations and some capability switches need further enforcement verification.
Does Unassign remove every access relationship?
Not necessarily. Verify effective ownership across the related fields before treating unassignment as access revocation.
Does this provide reseller billing?
This workspace manages hosting delegation and account ownership. Automated reseller charging, invoicing and subscriptions require a separate commercial system.