Packages are service tiers that define what resources and features your users get — every user is assigned a package that determines their sending limits, contact quotas, and available capabilities. You manage them under Users → Packages, and creating one is a 2-step wizard.
Step 1 sets the package name, the user role that defines permissions, and the limits (enter -1 for unlimited):
Sending limits — hourly speed, daily limit, monthly quota
Resource limits — maximum contacts, sending domains, sending nodes, segments, triggers, trigger actions per month, evergreen campaigns
Automation limits — monthly actions and maximum actions per automation
Commercial ESP options — suppressed-domain limits, auto-stopping campaigns at a bounce-rate threshold, credit-based billing, and overuse allowance
Step 2 covers additional headers embedded in users' emails, pre-assigning specific sending nodes, bounce addresses, and sending domains to the package, sender-information options (from sending nodes, contact lists, or custom), maximum sending threads, the initial setup guide toggle, and authentication requirements (force DKIM, custom tracking domain, or custom bounce domain).
Worth knowing: user roles must be created before packages; you can't delete a package while users are assigned to it — reassign them first; editing a package affects all users currently on it; and if a user isn't getting new limits, check whether custom per-user overrides (inherit toggles turned off) are taking precedence over the package values.
