Prepare an agreement as a working draft, review its audience and signing controls, then publish the wording you intend customers to see. PD Agreements keeps published text as numbered versions rather than overwriting earlier accepted wording.

Prepare the first draft

Open PD Modules → Agreements → Agreements. Have the module installed and available to your administrator or staff group, then select New agreement.

1. Enter a customer-facing Name.
2. Choose Type of document. This is a label for organising agreements; it does not determine who must sign or how the request behaves.
3. Enter The agreement text using Markdown. Use headings, paragraphs, lists and ordinary links. Pasted HTML is displayed as text.
4. Review Who must accept this and the product, group or client selections. A selection in any target field makes the agreement targeted, so check the audience before saving.
5. Review When are they asked, How they sign, Reading and Enforcement.
6. Use Save draft while preparing a new agreement. A new unpublished draft is not presented to customers for signing.

Understand the request timing

At checkout requests acceptance during the order when Ask at checkout is enabled. On next login uses the next client-area visit when Ask when they next sign in is enabled. On demand only makes the document available for signing without using it to block ordinary account access.

Use an account you control for a planned check of the intended audience. Do not create a real paid order solely to inspect the signing screen.

Publish the wording

Review the complete text and controls, then click Publish version 1 and confirm Publish agreement. Check the returned message, live version and Version history. The published text is the version customers accept; each acceptance refers to that version.

Change an existing agreement

Open Edit and prepare revised wording. Save changes keeps the last published wording, but audience, timing, method and enforcement are saved on the agreement itself and can affect behaviour immediately. It is not a preview-only save for those controls.

When the wording is ready, add an optional What changed in this version note. Select Everyone who signed an earlier version must accept this one only if you intend to request acceptance again. Click Publish new version and check the result.

Unchanged wording keeps the current version even if you press Publish: it does not create a new version or apply a new re-acceptance decision. If an outcome is unclear, inspect Version history and the current controls before repeating the action. Your hosting team should retain the original document/version reference, action time and redacted result while comparing the saved state.

Check the saved version and controls

Your hosting team should compare the intended agreement, returned operation result, current controls and Version history before saving or publishing again. Unchanged wording keeps the current version; saved audience, timing and enforcement can change even when no new wording version appears. Compare what changed with what customers actually see. Do not publish replacement wording merely to diagnose an uncertain earlier action.

See the PD Agreements WHMCS guide for related tasks, or explore PD Agreements.