Build a subscription package

What this achieves

A package is a plan that customers can be put on: a set of capabilities, a price, and a set of limits. Building one here is what makes it available to assign.

Required role: Humavera platform staff.

Steps

Go to Platform → Subscription Packages.
Select New package.
Under Identity, enter the Name, the Slug, and a Description, and set the Status.
Under Capabilities, select what the package includes. The composer confirms the set is valid before you can save.
Under Pricing, set Included seats (base covers), the base and overage prices, and the Currency.
Under Limits, set the credit allowance and the structural quotas.
Select Create.

Identity

Option	Description
Name	What the package is called wherever it is shown.
Slug	Its short identifier.
Description	One line describing who the package is for.
Status	Active, Hidden, or Deprecated.
Display order	Where it sits in a list of packages.
Tier rank	Its position in the ladder, which decides whether a move onto it counts as an upgrade or a downgrade.
Default for new tenants	Whether a newly created workspace lands on this package. Only one package is the default.

Tier rank is the field that carries a consequence. A move to a higher rank is an immediate upgrade a customer can make themselves; a move to a lower rank is a downgrade that goes to review instead. Rank the package deliberately rather than leaving it where it fell.

Capabilities

The capability set is dependency-validated. If you pick something whose prerequisite is missing, the composer says which capability requires which, and offers Auto-add dependencies to add the missing ones. A package with an invalid set cannot be saved.

Example: a package sold on advanced reporting cannot be saved without whatever that reporting is built on. The composer names the gap rather than letting a customer be sold a set that will not work.

Recommend with AI drafts a starting set from a target size, industry, country, and free-text needs. It is a draft: the panel says so, it applies into the composer, and you edit before saving.

Pricing and limits

Option	Description
Included seats (base covers)	How many employees the base price covers.
Base price — monthly ($) / Base price — annual ($)	The base price for each billing frequency.
Overage / extra employee — monthly ($) / Overage / extra employee — annual ($)	What each employee beyond the included seats costs.
Currency	The currency recorded against the package.
Custom pricing	Marks the package as priced by agreement rather than published.
Monthly AI credits	The credit allowance a workspace on this package receives each cycle.
API rate limit / hour	The request ceiling for programmatic access.
Max legal entities / Max payroll countries	Structural quotas. Leave blank for unlimited; the minimum is one. To withhold something entirely, remove the capability rather than setting a quota of zero.
Default field template	The employee-record template a new workspace on this package starts with.

Example: a package with fifty included seats and an overage rate charges the base price up to fifty employees, and the overage rate for each one after that.

The employee cap is enforced only on the free tier, where the included seats are the cap. Paid packages are uncapped and bill the extra as overage instead of blocking the workspace.

The last section of the form holds the billing provider’s product and price identifiers, which link the package to the account it is charged through.

Changing a package that customers are already on

This is the part that is easy to get wrong.

Option	Description
Clone	Copies the package so a new version can be built. This is how a package changes shape without disturbing anyone.
Status Hidden or Deprecated	Removes it from new sign-ups and from the assign dialog. Workspaces already on it are unaffected.
Delete	Blocked while any workspace is on the package, and blocked on the default package. The dialog offers to hide it instead.

Example: HC Corp is on a package whose price is changing. Clone the package, price the copy, and move new customers onto it. HC Corp keeps what they were sold until their own terms are renegotiated.

What happens next

An active package appears wherever a plan is assigned or compared, including on the customer’s own plan-comparison screen. Putting a workspace on it is a separate action taken on that workspace’s record.