Skip to main content
Re-acceptance lets a user who has already accepted sign again, for example when details shown in the agreement change or when your policy requires fresh consent. The prior acceptance stays binding, and each re-acceptance is recorded as a new event - old events and certificates are never modified.

​
Two ways to trigger it

  • Always require re-acceptance - a per-template toggle that re-prompts every user on every interaction. Configured in the Dashboard under Template settings.
  • On demand - your backend flags specific users and templates when you decide their consent is stale, via the Request clickwrap re-acceptance endpoint.

​
Detecting it in your integration

Read the reAcceptanceRequired flag on the consent status endpoint. When it’s true, GET /clickwrap re-displays the agreement and the user signs again against the current content. The status stays ACCEPTED throughout, so there is no compliance gap.

Request clickwrap re-acceptance

Flag specific users and templates for re-acceptance via the API.

Checking consent status

Read reAcceptanceRequired to detect when a re-display is pending.