Grouped Display #

When a customer has purchased a bundle, their Licenses section in the customer portal displays a grouped view rather than individual standalone rows.

1. The bundle appears as a group header. It shows:
   • The bundle product name (e.g., “Developer Pack”)
   • The parent license key
   • The subscription renewal date
   • A renewal action button
2. Child licenses are nested under the bundle header. Each child shows:
   • The child product name (e.g., “Pro Plugin”)
   • The child license key
   • Activation count vs. limit
   • Expiration date
   • “Managed by [Bundle Name]” label instead of an individual renewal action

Renewal Action Placement #

• The renewal action appears only on the bundle (parent) row.
• Child license rows display “Managed by [Bundle Name]” in place of a renewal button.
• Customers cannot renew individual child licenses separately. All renewals happen at the bundle level when the bundle subscription is renewed.

What “Managed by [Bundle Name]” Means #

The “Managed by” label tells the customer:

• This license is part of a bundle
• Its renewal is handled when the bundle subscription renews — no separate action is needed
• If they want to manage renewal settings, they do so at the bundle level (the parent row)

Activation Management #

Each child license has its own activation management. Customers can still activate and deactivate sites for each child license independently, the same as for any individual license.

Download Access #

Download access for each child product follows that child product’s own settings. If a child product requires an active support contract for downloads, that requirement applies normally.