Skip to content

Packages and feature lists

Set resource limits, inode limits, and customer-visible capabilities.

1Overview

Packages define account quotas such as disk, bandwidth, databases, websites, email accounts, applications, and inodes. Feature lists control which user-panel sections are available.

Packages and feature lists in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.
Hosting Packages page with resource limits, feature list settings, assigned accounts, and package actions.

Packages and feature lists in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.

2Before you begin

Administrator actions can affect multiple customer accounts and server services.

3Step-by-step workflow

Open Packages, create or edit a package, set a non-negative limit for each resource, choose enabled features, then apply the package to the intended accounts. Review existing usage before reducing a quota.

  1. Open Packages and choose Packages, Feature Lists, or Assign Accounts for the task you need.
  2. Use Create package for a new plan or Edit on the existing package you want to change.
  3. Give the package a clear name and review each displayed limit, including disk, bandwidth, domains, databases, email, applications, and inodes.
  4. Check the field guidance for unlimited values; do not assume that a blank value and zero mean the same thing.
  5. Select the feature list that controls which tools the customer can use.
  6. Save the package, then use Assign or Assign Accounts to choose its customers.
  7. For an edited package, review the assigned-account count and use Apply to accounts when that action is offered.
  8. Open an affected user view and check both its visible menu and resource limits.

4Practical example

Example: duplicate Basic before creating a larger plan, increase the required quotas, and assign only the intended customers. Changing a shared package can affect several accounts, so review the assignment list first.

5Verify the result

Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.

  1. Check that quotas remain above current usage.
  2. Confirm feature changes appear in the user-panel navigation after the next refresh.

6Common problems and what to check

New limits are not visible: check that the account is assigned to the saved package and that the changes were applied.

A menu item is missing: inspect the feature list as well as the package quotas.

A lower quota is rejected: compare the proposed limit with current usage before reducing it.

7Security, impact, and rollback

Changing a package affects every assigned account after it is applied. Disabling a feature hides its user-panel tools but does not automatically delete existing data.

Related guides

WebsitesFind each hosted domain, its owner, document root, status, and website-level tools.Hosting passwordsReset a customer hosting password from a verified administrator workflow.See all guides in Administrator panel

Still need a hand?

Get help with your plan, website, or hosting through your client area.

Open client area