EzePanel · resellers
Make delegated hosting ownership explicit.
Organize reseller identities, available packages and customer accounts while keeping server administration with the provider. Understand the controls behind the delegation before defining the offer.
Explore the capabilityOwnership stays connected.
A reseller relationship connects three responsibilities: the platform operator, the delegated customer manager and the hosting customer. The account owner and package scope need to stay clear at each handoff.
Define the reseller identity.
The administrator manages reseller profiles and the ownership of customer accounts. The reseller workspace then presents its customer-management scope rather than the complete administrator environment.
Technical details
A reseller identity is not root access. Shared services, host security, server updates and global infrastructure policy remain separate administrator responsibilities.
Swipe to inspect · tap the image for full context
Connect packages to the delegated offer.
Reseller package-access records identify which packages can be used in the relevant creation workflow. Packages connect account allowances and Feature Lists to reusable hosting configuration.
Technical details
A package existing on the server does not establish access for every reseller. Review the assigned scope and actual account creation result before presenting the offer to customers.
Know which boundaries are enforced.
Account ownership is checked in supported reseller workflows, including account/domain PHP operations. Customer users continue to act within their own hosting-account identity.
Technical details
Some aggregate reseller disk and bandwidth limits and profile capability flags are not uniformly enforced. Treat those as a current product limit, not an assumed hard allocation guarantee. The administrator guide details the individual controls.
Follow the account through its lifecycle.
Create within the available package scope, follow provisioning and confirm the resulting owner and website. Review access when staff or customer responsibility changes.
Technical details
Disabling a reseller login and changing customer-account ownership are different decisions. Preserve the customer service and administrative access required to investigate failures or complete a handover.
Separate software roles from commercial terms.
EzePanel provides the hosting workflow. The provider and reseller agree their own service scope, customer support and commercial arrangements. EzePanel software licensing is a separate relationship.
Technical details
This page does not create a reseller price, white-label entitlement or response-time commitment. Use verified controls to define the service and review approved licensing terms for software rights.
In daily operations
Make the handover clear.
Example: a provider assigns a customer portfolio to a reseller. It verifies ownership and available packages, then confirms which changes remain provider responsibilities instead of sharing a root administrator login.
Frequently asked questions
Questions about the workflow.
Is a reseller a server administrator?
The reseller role describes delegated customer scope. It does not grant unrestricted infrastructure or root authority.
Are every reseller quota and capability flag enforced?
No. Some aggregate quotas and flags are not uniformly enforced. Review the administrator reseller guide before relying on a particular boundary.
Does this page announce a reseller pricing programme?
No. It describes product roles and workflows. Hosting resale terms and EzePanel software licensing are separate commercial relationships.
Can customers promote themselves into reseller access?
Ordinary customer access does not authorize management of other hosting accounts. Reseller identity and ownership are administrator-managed.
Connected capabilities
Connect this workflow to your hosting operation.
Explore the platform or discuss the requirements of your server, team and customers.