Before creating an account
Sign in to EPAdmin with hosting:manage, complete the installed MFA policy and refresh authentication when requested. Check the agent, current licence and package availability first. Account creation is a durable host operation, not a form-only customer record.
Create the account
Open Account Management → Create Hosting Account. Enter the account display name, Customer login, a new privately retained Customer password, optional contact email and an active hosting package. Review any advanced per-account overrides and the resulting tools and limits before submission.
When the installed GET /v1/accounts/capabilities explicitly reports primary-domain support, the form also requires the primary domain. Use a complete lowercase domain without a scheme, port or path. This reserves ownership; it does not create a website, zone or mailbox. An older installation must not be given a fabricated capability or an unsupported new field.
The request uses POST /v1/accounts with name, login, password, contact_email, package_id, supported primary_domain and optional overrides. Record the returned operation ID. Wait for completion and inspect owned identity, filesystem and enforcement evidence before using the account.
Find and maintain accounts
The list supports a server search, status filter and cursor pagination. A new search clears the previous selection. Reopen the latest account detail before choosing Modify; a package change sends package_id, the current revision and any explicit overrides. Profiles use name, contact_email and revision. Profile contact is separate from a verified recovery address.
Reset Customer password requires matching new values of at least 14 characters. It revokes the Customer's existing sessions and API tokens while retaining enrolled MFA. It changes the Panel password; the Linux identity stays locked without a shell password. Never ask a Customer to send their current password.
Suspend, reactivate and terminate
Suspension/reactivation sends the reviewed account revision and returns a durable operation. Inspect the final service state; a submitted request is not proof that all access has changed. A bulk action returns individual results, so review every account instead of treating the batch as atomic.
Termination first loads an impact preview. Read its resource inventory, exact confirmation phrase, revision and recovery requirements. Submit only the current preview_token, confirmation_phrase and revision after acknowledgement. Missing full reconstruction evidence can block termination in this candidate; do not bypass the gate or remove metadata manually.
Verify and troubleshoot
Test a Customer login with the new credentials, confirm it sees only its own resources, and review the recorded operation events. For a stale revision, reload and review the changed account. For uncertain delivery, inspect the existing operation before another create. Customer ownership handover is not implemented. An Admin View session is separately audited, expiring and read-only; it is not a Customer password reset or write session.