The reseller panel: every account from one screen

The reseller view is the layer above your individual accounts. It manages all of them from one screen: creating, suspending, terminating, modifying in bulk, and reading the meters that tell you how much of your allocation is actually in use.

The two layers, plainly

• Account view: one site's contents. Files, databases, email, DNS, subdomains, certificates, cron.
• Reseller view: the accounts themselves. Who exists, what package they are on, which address they answer on, how much they consume.

WHM and Accounts gives a quick test for telling them apart: phrase the task out loud, and notice whether it names one site or reaches across several.

What lives up here

Account lifecycle first: create an account, list accounts, manage suspension, list the suspended ones, terminate, and modify several accounts at once. Then the things that describe accounts rather than change them: packages and package listings, bandwidth usage, disk quota usage, and a view of accounts that have gone over quota.

Alongside those sit the estate-wide versions of things you also see per account: addon and parked domains, subdomains, DNS zone editing, password modification, API tokens, certificate creation and installation, SSL host management, AutoSSL, assigned addresses, and transferring or restoring a cPanel account.

The meters are the part people ignore

Three numbers sit at the top of this view and they answer questions you would otherwise guess at:

1. Accounts used against allowed. Tells you whether your next site needs a plan change or just a click.
2. Disk used against allocated. Read it alongside file counts, because inodes run out before bytes do on a caching-heavy network. See cPanel in Practice.
3. Bandwidth used against allocated. A jump here with no traffic increase is usually a crawler or a backup job, not customers.

Checking these takes ten seconds and turns "are we near a limit" from a worry into a fact.

Bulk actions deserve more care up here

Modify multiple accounts is genuinely useful and genuinely dangerous, for the same reason: it does the thing to everything at once. The discipline is in WHM and Accounts and it is short: one account, then a few that differ from each other, then the rest in batches, with a look in between.

Terminate is the one with no undo. Suspend first, wait, then terminate. Suspension keeps everything including the address assignment; termination removes the account and returns the address to your pool.

Addresses live here too

Assigned addresses are a reseller-level concern because they are what makes your network look like separate properties from outside. Which account answers on which address is worth auditing periodically rather than trusting, since the map drifts quietly during migrations and rebuilds.

The audit itself is four steps and takes a few minutes: it is written out in WHM and Accounts. What the separation buys you, and what it does not, is in IP diversity and footprint.

Start here when something is unclear

When a site misbehaves and you do not yet know whether the cause is that site or the estate, the account list is the fastest first look. One account behaving differently from its siblings is a site problem. Every account behaving the same way is usually something you applied to all of them.