How to target PD Agreements at products, groups or clients in Blesta
Choose the audience for an agreement when only particular products, groups or customers should receive it. PD Agreements combines target matches with OR: a match in any selected group is enough.
Open the audience controls
Open PD Modules → Agreements → Agreements. Choose New agreement or Edit on the intended row. In the editor, find Who must accept this.
For a general agreement, choose Everyone and leave all target fields empty. For a restricted audience, choose Only the products, groups or clients I choose, then populate the intended fields.
Choose the targets deliberately
- Use Products for particular services the customer buys or already owns.
- Use Product groups to cover products belonging to a group, including products added to it later.
- Use Client groups for the selected customer groups.
- Use Individual clients for named customer accounts.
Selecting anything in those four fields makes the agreement targeted automatically. To return to Everyone, clear the previous selections as well as changing the audience choice. A targeted agreement with nothing selected is rejected when saving or publishing; it is not a useful way to pause requests.
Check the combined audience
For example, choosing a product and an individual client covers customers matching the product or that client. It does not limit the product to that one client. If your intended audience depends on an intersection, do not assume adding more targets narrows it.
Review When are they asked too. At checkout does not block the Blesta order form. It requests acceptance on a later client-area visit after the customer has the relevant product, with the applicable request settings enabled. On next login requests acceptance on a client-area visit; it is not limited to a fresh sign-in. A product-based request on an account visit depends on the products that customer already has; it is different from evaluating the cart during checkout.
Save and verify
Review the agreement’s current status before saving. For a new draft, save the draft and publish when its wording and controls are ready. For an already published agreement, Save changes updates the audience immediately while preserving the current published wording.
Check the audience summary in Agreements and reopen Edit to confirm the selected targets. Then use suitable accounts you control to check one intended match and one non-match without placing unnecessary real orders.
Earlier accepted wording is not changed by retargeting, and adding someone to the audience does not itself mean an existing valid acceptance is discarded. Review the current version’s re-acceptance decision when diagnosing a missing request.
If the result is unexpected, check the published state, actual ownership or group membership, request timing and master switches. Your hosting team should retain the target types, document/version reference and redacted result while checking the actual match; keep customer identities and private document text out of shared screenshots.
Check the intended audience
Your hosting team should compare the saved target selections with the intended customer’s actual products and group membership, published state, request timing and existing valid acceptance. Targets combine with OR; adding another target does not create an intersection. Reopen Edit to check saved selections before broadening the audience or repeatedly republishing.
See the PD Agreements Blesta guide for related tasks, or explore PD Agreements.
