WHM or cPanel: which login you need for which job

WHM manages accounts. cPanel manages one account's contents. Almost every wasted half hour on a hosting network starts with someone hunting for a WHM feature inside cPanel, or the reverse, so the fastest thing you can learn is which door to walk through.

The split in one line each

• WHM: creates accounts, assigns addresses, sets the limits an account lives inside, suspends, terminates, and shows you everything you own at once.
• cPanel: files, databases, email, subdomains, certificates and cron for one account.

If the task involves the word "which site" or "all of them", it is a WHM task. If it involves one site's contents, it is cPanel.

Jobs that live in WHM

1. Creating a new account for a new site.
2. Deciding which dedicated address an account answers on.
3. Setting the resource ceiling a group of sites runs inside.
4. Seeing every account, its address, its disk use and its status on one screen.
5. Suspending an account without deleting anything.
6. Issuing an access token so a script can work without your password.

Jobs that live in cPanel

1. Uploading files, editing them, restoring one from a backup.
2. Creating a database or a database user.
3. Adding a subdomain or an alias.
4. Issuing or installing a certificate for that site.
5. Scheduling that site's own cron jobs.
6. Reading that site's error log.

The rule that saves the most time

Never make a network wide change from inside a single cPanel. It works, and it is why the mistake persists: you fix one site, forget the other twenty-nine, and six months later nobody can explain why one account behaves differently. Changes that should apply everywhere belong in WHM, where they apply everywhere by construction.

The reverse mistake is rarer but more expensive. Operations in WHM affect accounts wholesale, so a careless click there is not one site being wrong, it is many. Slow down proportionally to how many accounts the screen is showing.

Getting into a single account from WHM

You do not need the individual cPanel password. WHM can open any account it owns, which means you should not be storing thirty cPanel passwords anywhere. One WHM login plus discipline beats a password list every time, and it removes the single worst habit on a hosting network, which is reusing one password across accounts so they are easier to remember.

What this means for how you plan the network

Because limits, addresses and grouping are all WHM level decisions, they are decisions you make once and live with. Which sites share an account determines which sites share a resource ceiling, a PHP version and a filesystem. That is worth thinking about before the first account exists rather than after thirty do. The reasoning is in Network Planning, and the resource side in Platform and Limits.

Address assignment is also a WHM level decision, and it is the one that decides how your sites look from outside. Each account here can answer on its own dedicated, non-consecutive address with private nameservers, but only if you assign it that way when the account is created.

The official interface documentation is at docs.cpanel.net.