Skip to Content
Browse documentation

Suspend or Unsuspend Resellers in WAP

Review reseller-wide suspension and restoration, required reasons and owned-account impact before applying lifecycle operations.

Open Hosting → Resellers → Suspend or Unsuspend. This targets the reseller and its owned account chain, unlike the individual User Accounts suspension workflow.

Requirements and impact review

Use administrator WAP access over HTTPS with JavaScript enabled. Demo sessions cannot apply changes. Review direct customers, nested resellers and the reason each account is currently suspended before operating on the chain.

The table lists User, Domain, Subaccounts, Hosting Plan, Contact Email, Status and Action. The displayed direct count is not a full impact manifest for a nested hierarchy.

Suspend fields and steps

Select Suspend Reseller for an active row. Review Reseller Account, Owned Accounts and the chain-wide warning. Enter required Reason for suspension, then confirm Suspend Reseller or cancel.

The server validates reseller existence and a nonempty reason. Keep the reason operational and free of secrets; it is included in audit metadata. The action invokes the reseller-mode suspension command rather than merely switching off reseller-panel login.

Unsuspend

Select Unsuspend Reseller, review the reseller/owned-account restoration warning and confirm or cancel. There is no reason field for restoration.

Restoration affects owned accounts

The operation is intended to restore the reseller's account chain. Review customers suspended for independent reasons before using it. It does not repair quota, policy or security issues, and automatic policies can suspend accounts again.

Verify outcomes

The view records reseller audit events and reports success/failure feedback. The current helper does not provide a trustworthy per-account command-completion report; a banner alone does not establish that every descendant reached the intended state. Reload inventory, inspect relevant logs and verify affected services/accounts individually.

Missing reseller, missing reason, demo restriction and unable-to-suspend/unsuspend errors need review before resubmission. Failures or partial results require state inspection, not an immediate duplicate request.

To reverse an unintended restriction, review the cause and use restoration only when appropriate. To reverse unintended restoration, review each account's intended state; do not assume one chain-wide action restores every prior independent suspension condition. There is no snapshot/undo control.

Do’s and don’ts

  • Do assess nested ownership and customer impact.
  • Do distinguish notification/audit feedback from verified per-account state.
  • Do not assume this is only a reseller-login toggle.
  • Do not use termination for a temporary restriction.

Previous: Reseller Shared IPv6. Next: Terminate Reseller.