You can edit, suspend and remove cPanel accounts via Account Functions » List Accounts. By default the page shows a table with all your cPanel accounts. Among others, it shows the IP address, the disk space quota and usage and the hosting package. You can sort the table by any column and export the table to a CSV file.
Clicking the plus sign in the first column reveals various options, including the option to change the cPanel password.
Image: the List Accounts page.
You can either suspend or terminate a cPanel account. If you want to delete an account, we strongly recommend you first suspend it and to then wait one or two days before terminating it. This is particularly important when an account has moved elsewhere. By first suspending the account you can be fairly sure that the old account is definitely no longer needed. If it turns out that the package is still need, for instance because the DNS for the domain is hosted on the server, then you can simply unsuspend the account and resolve the issue. You don’t have that option when you terminate an account. Everything, including the DNS zone, is deleted.
Image: the “terminate account” interface.
You can quickly increase (or decrease) the disk space quota for an account via the Change Quota option. This is mainly useful if an account has suddenly run out of disk space. After you increase the quota everything should be up and running again, and you can then resolve the disk space overuse. It is worth noting that changing the quota doesn’t change the hosting package itself – it purely changes the account’s disk space quota.
Often, the best way to resolve a disk space issue is by changing the hosting plan. The Change Plan option let’s you do just that.
Another option is to change an account’s resources via Modify Account. Among others, you can change the bandwidth limit, number of databases and aliases. When you modify an account you usually get a “package conflict”. The new set of resources isn’t known, and you therefore need to decide how you want to proceed. The most sensible option is usually the first option: Create a new package with this name.
Image: resolving a package conflict.
By default, the new package name is the old package name with the username appended. For example, in the above image I added a subdomain to the exampleweb package. The original package name is example_Plan_1, and the suggested new name is therefore example_Plan_1_exampleweb.
If you like to keep things organised then you can change the name to something more descriptive. For instance, as I added a subdomain I can change the name to example_Plan_1_extra_subdomain. That way it is easy to tell how the custom package is different from other plans.
This article is part of a series about reseller hosting: