Skip to Content
Browse documentation

Suspend or Unsuspend Accounts in WAP

Temporarily restrict or restore Eenos account access with single and bulk suspension workflows, required reasons and reseller dependency checks.

Open Hosting → User Accounts → Suspend or Unsuspend to temporarily restrict hosting-account access or restore access to suspended accounts. Unlike termination, this is not an account-deletion workflow.

Requirements and preparation

Use an authenticated WAP administrator session over HTTPS with JavaScript enabled. Demo sessions cannot apply these actions. Confirm the username, domain, owner, current status and reason for the intended restriction or restoration.

Suspension is intended to disable account hosting access until unsuspended. It is not a substitute for investigating compromised processes, preserving incident evidence or verifying every protocol is blocked. Inspect actual affected services when access restriction matters.

Check the cause before restoring access

Unsuspension does not fix the original quota, policy or security problem. Verify that restoration is appropriate and review automated suspension policies in Tweak Settings, which may apply again if the underlying condition remains.

Table and controls

The table shows checkboxes, User, Domain, Status and Action, initially with 25 rows sorted by User. Search, pagination and page-length controls help locate accounts. Active rows offer suspension; suspended rows offer unsuspension.

The header checkbox selects accounts on the current page. Individual selections persist across table redraws and pagination, so a filtered or different page can hide already-selected usernames. Review the final Selected accounts list before any bulk confirmation.

Suspend one account

  1. Locate an active account and select Suspend Account.
  2. Review Hosting Account and Domain.
  3. Enter a nonempty Reason for suspension.
  4. Select Suspend Account, or cancel before submission.
  5. Check the response, reload and verify the account's suspended state and intended access restriction.

The reason is required by both the workflow and server form. Use a concise operational explanation without secrets or unnecessary customer information. The view records the reason in the account-suspension audit metadata.

For a reseller, validation requires its recorded subaccounts to be suspended first. Including both reseller and customers in a single bulk selection is not a guarantee that this prerequisite will be satisfied in the required order.

Unsuspend one account

  1. Locate the suspended account and select Unsuspend Account.
  2. Confirm Hosting Account, Domain and the restore-access notice.
  3. Select Unsuspend Account, or cancel to stop.
  4. Check the result and verify actual customer-service access separately.

This dialog has no reason or new-password field. It does not rotate credentials or automatically unsuspend every reseller subaccount.

Bulk Suspend

  1. Select the intended accounts and inspect any accumulated off-page selections.
  2. Select Bulk Suspend.
  3. Review Selected accounts in Suspend Multiple Accounts.
  4. Enter the required Reason for suspension. This one reason applies to the submitted group.
  5. Select Suspend Accounts, or cancel.
  6. Verify each account individually after processing.

No selection produces Select at least one user for suspending. Accounts must exist and reseller dependency checks still apply. Do not assume a mixed-state selection will automatically perform exactly the intended subset; choose accounts appropriate to the action and check outcomes.

Bulk Unsuspend

Select the intended suspended accounts, choose Bulk Unsuspend, review Unsuspend Multiple Accounts and its Selected accounts, then select Unsuspend or cancel. There is no bulk unsuspension reason field.

No selection produces Select at least one user to unsuspend. Review why every selected account was suspended before restoring the group; a shared selection does not establish that all have the same operational cause.

Processing and results

The view invokes existing suspend/unsuspend helpers and records account audit events. Bulk responses describe processing as started in the server background. Treat such messages as submission feedback, not a per-account completion guarantee. Verify the account status, relevant operation logs and actual service behavior before retrying or reporting completion.

There is no live progress dashboard or cancel-running-job control on this page. Audit metadata records the submitted account group; it is not an independent test that every customer service has reached the intended state.

Errors and recovery

SituationWhat to do
Missing reasonEnter a nonempty reason when suspending.
User not found / invalid accountReload and confirm the target still exists.
Reseller dependency errorReview and process the reseller's customer dependencies first.
Multiple accounts suspend/unsuspend failedInspect validation feedback and each target's current state before retrying.
Unable to suspend/unsuspendInvestigate actual account state and server-side operation errors; do not assume no partial effects.
Demo server, this operation is unavailableChanges are blocked in this session.

If a suspension was unintended, review the cause and use Unsuspend for that account, then verify access. If restoration was unintended, review and suspend again with the correct reason. Neither operation repairs separate configuration errors or recovers deleted data.

Do’s and don’ts

  • Do verify identity, reason and current state before confirming.
  • Do use focused selections and inspect every username in a bulk dialog.
  • Do review reseller dependencies and check customer-service results afterwards.
  • Do not treat Active/Suspended as a complete application-health or incident-containment test.
  • Do not assume unsuspension fixes the original condition or restores all child accounts.
  • Do not use termination when temporary suspension meets the intended need.

Previous: Terminate Account. Next: Change Account IPv4.