Reseller guide

Create hosting accounts and support the customers assigned to your reseller account.

Where to find it: Documentation > Hosting Manager > Reseller guide.

Available to: Anyone reading the public documentation. The related SHM action still follows the role stated on its page.

What this page does

Use this guide to create and support owned accounts, select provider-approved packages and features, manage account DNS and SSL, inspect logs and audit history, and work inside the reseller's assigned capacity.

Before you start

Confirm the reseller package, ownership, available account packages, feature profiles, and remaining resources before account creation. A reseller cannot fix a global service by stepping outside their scope; root must handle server-wide service, firewall, license, update, and configuration work.

Reseller boundary

Capacity and packages

The reseller package caps what the reseller may distribute. An account package describes the customer's limits, but it cannot grant capacity or a feature the provider did not delegate to the reseller.

Supporting an account

Open the owned account from List Accounts and verify the selected username and domain before acting. Account pages then use the same ownership, package, feature, and service checks that protect a direct customer login.

How to use it

1. Review reseller capacity and approved policies.
2. Create the account with an appropriate package and feature profile.
3. Verify DNS, SSL, website, mail, database, and backup readiness.
4. Sign in or view the account context to confirm the customer menu.
5. Escalate global service or infrastructure work to root with exact evidence.

Current reseller workspace and API

The server menu provides Dashboard, Account Default, Account Packages, Feature Profiles, Create Account, List Accounts, Addon to Account, DNS Manager, AutoSSL, ModSecurity, Logs, and Audit. Work remains limited to owned accounts and delegated policy; root-wide services and global settings are not reseller operations.

Integrations can use the explicit /v1/resellers/{reseller}/... namespace for accounts, packages, profiles, defaults, DNS/DNSSEC/Cloudflare, AutoSSL, logs, audit, progress, and addon conversion. The reseller identifier must match the authenticated reseller unless root is making the request. Do not add owner or role fields to try to change that boundary.

Result and next check

The reseller can operate owned customer accounts consistently while server-wide authority remains with the provider. Capacity, ownership, and feature decisions remain visible and enforceable in SHM.