Confirm the exact username, affected domains and customer impact. Coordinate billing or abuse handling through the normal process. Suspension affects service availability and should not be treated as a substitute for a backup or a complete security cleanup.

1. Open Account Functions > Manage Account Suspension.
2. Select the intended account from the domain or username list. Review its current state before proceeding.
3. Enter a clear internal reason that will help an authorized colleague understand the action. Do not include passwords, confidential evidence or unnecessary personal data.
4. If you are a server administrator, consider whether the reseller should be prevented from reversing this suspension. Use that restriction only when justified by your operational process.
5. Select Suspend and wait for the report. Record the action and the conditions required for reinstatement.

Confirm the account is shown as suspended and check the customer-facing result. Suspension does not guarantee that every external service used by the application has stopped, so assess separate database, DNS or third-party dependencies when relevant.

If WHM refuses the action, verify account ownership and role permissions. If the wrong account was selected, restore it promptly through Manage Account Suspension and investigate any service impact. For an incident involving compromised content, retain evidence and arrange remediation before reinstating service rather than cycling suspension on and off.

• Unsuspending a cPanel account in WHM
• Requiring a cPanel user to change their password
• Changing an account bandwidth allowance in WHM
• Creating a cPanel account in WHM as a reseller

• Official cPanel & WHM documentation