Choose when customers are asked to sign and which parts of their account remain available while a required agreement is outstanding. Review the agreement’s own controls and the module’s Settings together.

Set the request on the agreement

Open PD Modules → Agreements → Agreements. Open Edit on the intended document, or prepare a new one. Confirm its audience before changing When are they asked.

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 offers the applicable document for signing without making it a login gate.

The Enforcement checkbox, Required — they cannot continue without accepting, determines whether the agreement is mandatory for its request flow. Turning it off makes the agreement optional. Do not confuse an optional agreement with an unpublished draft: the published document can still be offered and accepted.

Review the Settings master switches

Open Agreements → Settings and review Ask at checkout and Ask when they next sign in. These affect groups of agreements, so changing one can affect more than the document you just edited.

Under Days a customer may postpone a login agreement, zero means no postponement window. A positive value allows Remind me later for the configured period. This postponement is held for the customer’s current session; do not treat it as a scheduled, permanent exemption from the document.

Choose which pages remain available

Review Pages a customer may still open before signing. The options are Only support and billing (recommended), Nothing until signed, and Everything except placing new orders.

The default mode also permits access to existing service pages. Do not interpret its short label as an exact list of every permitted page. The module’s own signing and agreement pages, and account access such as signing out and password reset, remain reachable.

Review the intended customer journey before saving a stricter mode. Check a representative controlled account with an outstanding applicable request, including billing, support, existing services and ordering.

Verify a change or diagnose a missing prompt

Changes to an existing agreement’s timing and enforcement can take effect when saved, without publishing new wording. Confirm both the agreement controls and Settings after saving.

The client-area check can retain an earlier clear result briefly, and a session postponement can delay the prompt. Check those conditions before repeatedly changing or republishing a document.

If the prompt still differs from the intended result, retain the platform, document/version reference, audience, request timing, Settings choices and redacted error while your hosting team compares the actual request and permitted page. Do not repeatedly submit signatures to diagnose it.

Check request timing and access

Your hosting team should compare the agreement’s timing, required flag, audience, current acceptance and re-acceptance choice with the Settings master switches, permitted-page mode and actual page the customer tried to open. Review the briefly retained clear result and any session postponement before changing controls again. Preserve the platform-specific request timing described above. Do not tighten settings for every customer or submit a signature to diagnose one missing prompt.

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