Skip to main content

Packages

Manage and configure user packages, defining the privileges, features, and limits for each package to ensure users receive the appropriate level of service based on their subscription.

Overview​

Packages define what resources and features users have access to. Each user is assigned a package that determines their sending limits, contact quotas, and available features.


Viewing Packages​

Navigate to Users → Packages to view all configured packages.

Page Features​

ElementDescription
Add New +Create a new package
Show entriesControl page size
SearchFind specific packages

Table Columns​

ColumnDescription
IDUnique package identifier
Package NameName of the service tier
User RoleAssociated permission profile
Created onPackage creation date
ActionsRow action menu

Row Actions​

Click the ⋯ menu on any row to access:

ActionDescription
EditModify package settings
DeleteRemove the package

Creating a Package​

Navigate to Users → Packages and click Add New +.

The package creation form is a 2-step wizard.

Step 1: Package Details​

Configure package attributes and limits.

Package name *​

Enter a descriptive name for the package.

Examples:

  • "Starter Plan"
  • "Professional"
  • "Enterprise"

User role *​

Select the role that defines permissions for users in this package.

Create Roles First

User roles must be created before packages. Navigate to Users → User Roles to create roles.


Sending Limits​

Configure email sending quotas. Enter -1 for unlimited.

FieldDescription
Hourly speedMaximum emails per hour
Daily limitMaximum emails per day
Monthly quotaMaximum emails per month

Resource Limits​

Configure limits for contacts and resources. Enter -1 for unlimited.

FieldDescription
Maximum contactsTotal contacts across all lists
Maximum sending domainsNumber of sending domains allowed
Maximum sending nodesNumber of SMTP connections allowed
Maximum segmentsNumber of segments allowed
Maximum triggersNumber of automation triggers allowed
Trigger actions monthly limitTotal trigger actions per month
Maximum evergreen campaignsNumber of evergreen campaigns allowed

Automation Limits​

Configure limits for automation workflows. Enter -1 for unlimited.

FieldDescription
Reset Automation LimitAutomation reset limit
Monthly Actions LimitTotal automation actions per month
Maximum Actions in a single AutomationActions allowed per automation workflow

Commercial ESP Features​

Commercial ESP Only

The following features are only available with a Commercial ESP license.

Limit suppressed domains​

Enable to set a limit on how many domains users can suppress.

Stop running campaigns when the bounce rate reaches​

Enable to automatically stop campaigns when bounce rate exceeds a threshold.

Enable credits​

Enable credit-based billing for this package.

Allow overuse​

Permit users to send beyond their limits using credits.

Click Continue to proceed to Step 2.


Step 2: Additional Settings​

Configure additional package settings.


Additional Headers​

Add custom email headers that will be embedded in emails sent by users on this package.

note

No special characters or spaces are supported except hyphens (-).

Click Add New to add a header with name and value fields.


Assign Pre-built Assets​

Pre-assign system resources to users on this package. Enable a toggle to show a selection list.

AssetDescription
Sending NodesSelect specific sending nodes available to this package
Bounce addressesSelect bounce addresses available to this package
Sending domainsSelect sending domains available to this package

Miscellaneous​

Allow using sender information from sending nodes dynamically​

When enabled, users can use sender details configured on sending nodes.

Allow using sender information from contact lists dynamically​

When enabled, users can use sender details configured on contact lists.

Allow using custom sender information​

When enabled, users can specify custom sender information when creating campaigns.

Maximum threads​

Enable to set a maximum number of concurrent sending threads for users on this package.

Show the Initial setup Guide​

Enable to display the initial setup wizard to new users on this package.


Sending Domain Restrictions​

Require users to configure authentication before sending:

SettingDescription
Require DKIM authenticationUsers must set up DKIM for sending domains
Require tracking domain authenticationUsers must configure a custom tracking domain
Require bounce domain authenticationUsers must configure a custom bounce domain

Saving the Package​

Click Submit to create or update the package.

Click Back to return to Step 1.


Editing a Package​

  1. Click the ⋯ menu on a package row
  2. Select Edit
  3. Modify settings as needed
  4. Click Submit
Existing Users

Changes to package settings may affect users currently assigned to this package.


Deleting a Package​

  1. Click the ⋯ menu on a package row
  2. Select Delete
  3. Confirm deletion
Users Affected

You cannot delete a package that has users assigned to it. Reassign users to a different package first.


Example Packages​

Starter Package​

For new or low-volume users:

SettingValue
Hourly Speed500
Daily Limit5,000
Monthly Quota50,000
Maximum Contacts10,000
Maximum Segments10
Maximum Triggers3

Professional Package​

For regular business users:

SettingValue
Hourly Speed2,000
Daily Limit25,000
Monthly Quota250,000
Maximum Contacts100,000
Maximum Segments50
Maximum Triggers10

Enterprise Package​

For high-volume users:

SettingValue
Hourly Speed-1 (Unlimited)
Daily Limit-1 (Unlimited)
Monthly Quota-1 (Unlimited)
Maximum Contacts-1 (Unlimited)
Maximum Segments-1 (Unlimited)
Maximum Triggers-1 (Unlimited)

Best Practices​

Package Design​

  • Clear naming - Use descriptive package names
  • Logical progression - Create upgrade paths between packages
  • Appropriate limits - Match limits to user needs and server capacity
  • Feature differentiation - Distinguish packages by features, not just limits

Limit Setting​

  • Start conservative - Begin with lower limits and increase as needed
  • Monitor usage - Watch for users consistently hitting limits
  • Buffer capacity - Don't set limits at server maximum
  • Document limits - Communicate limits clearly to users

Maintenance​

  • Regular review - Audit packages periodically
  • Usage analysis - Identify underused or overused packages
  • Adjust as needed - Update limits based on actual usage
  • Retire unused - Remove packages with no users

Troubleshooting​

Cannot Delete Package​

Possible causes:

  • Users assigned to package

Solutions:

  • Reassign users to different package
  • Move or delete users first

Users Not Getting New Limits​

Possible causes:

  • Cache not cleared
  • User has custom limits set

Solutions:

  • Clear system cache
  • Check user's custom limit settings
  • Have user log out and back in

Package Limits Not Applying​

Possible causes:

  • Custom limits set on user override package
  • Wrong package assigned

Solutions:

  • Check user's custom limit settings (inherit toggles)
  • Verify package assignment

Next Steps​