Packages, feature profiles, and limits
Packages define what a hosting plan can consume; feature profiles define which account tools it can use. Together they turn a product description into repeatable, enforceable SHM policy.
Where to find it: Documentation > Hosting Manager > Packages, feature profiles, and limits.
Available to: Anyone reading the public documentation. The related SHM action still follows the role stated on its page.
What this page does
Use account packages for customer quotas and runtime limits, reseller packages for delegated capacity, and feature profiles for module availability. Keep recurring commercial plans here and reserve one-off account overrides for genuine exceptions.
Before you start
Plan the feature profile before attaching it to a package. Removing a tool or lowering a limit can interrupt an existing customer workflow, while editing a package definition should not be confused with deliberately applying that package to every existing account.
Policy parts
| Policy | Controls | Typical result |
|---|---|---|
| Account Package | Disk, domains, mailboxes and hourly mail, databases, FTP, CPU, memory, processes, inodes, I/O, IOPS, shell, IP policy, and feature profile. | A reusable customer plan. |
| Feature Profile | The account modules allowed by the plan. | Matching navigation and backend enforcement. |
| Reseller Package | Delegated accounts, resources, IPs, packages, features, and reseller privileges. | A bounded reseller business. |
| Account override | A selected account value that differs from its normal plan. | An explicit exception that support must remember. |
Unlimited values
Where SHM accepts -1 as unlimited, use it only when the hosting offer and server capacity genuinely allow it. “Unlimited” is a billing word until the server becomes full; the kernel remains stubbornly literal.
Existing accounts
Creating or editing reusable policy does not by itself prove that an existing account received it. Open the account, apply or select the intended package through the supported account workflow, then verify limits, shell mode, feature profile, and navigation in that account context.
How to use it
- Create or review the required feature profile.
- Create the account or reseller package with realistic limits.
- Attach the correct feature profile.
- Assign the package during provisioning or through the account's package action.
- Sign in or open the account context and verify limits plus every enabled module.
Result and next check
New and deliberately updated accounts receive consistent quotas, resource policy, shell behavior, and feature access. Resellers can distribute only the capacity and tools delegated by their provider.
Theme color