Agreements

An agreement is a legal text somebody must accept before something happens — terms and conditions before an order, an end-user licence before a download, a newsletter opt-in at checkout. The text itself is not stored here: it lives on a page your site already publishes, and the agreement adds the three things a page cannot carry — a version, the places it is asked, and whether refusing is allowed.

A consent is the record that a named person accepted a named version at a named moment. It is written once and never edited: what somebody agreed to in March cannot be improved in June. This screen only reads consents — there is deliberately no way to change or delete one.

The list

The top card holds your firm's agreements: label, machine name, current version, the contexts where each one is asked (checkout, download, registration), whether it is required, how many consents it has collected, and whether it is active. New agreement opens the editor; clicking a consent count filters the ledger below to that agreement.

The editor

• Label — what the person sees next to the checkbox.
• Machine name — how code and exports name it; unique within your firm.
• Document path — the published page carrying the text (/terms-and-conditions). The checkbox links there.
• Version — moving it asks everybody again. Recorded consents keep the version they were given for, so history stays true.
• Asked — tick the contexts where this agreement appears.
• Required — refusing stops what the visitor was doing. Unticked makes it an opt-in, and an opt-in always defaults to OFF: silence is not consent.
• Scroll required — the confirm button waits until the reader has reached the bottom of the text (the download dialog).

An agreement with recorded consents refuses deletion — deactivate it instead, and it stops being asked while its history stays intact.

A consent counts per version: a customer who accepted version 1.3 is not asked again until you publish 1.4. At the checkout this shows in two places — the tick box is simply absent, and the review step reads "accepted earlier" for that agreement rather than leaving a blank that would look like a blocked order.

The consents ledger

The bottom card lists the newest consents — who (an account, or the e-mail an order carried), which agreement and version, in which context, and what was happening (an order number, a release). Filter by agreement or by e-mail; Export CSV downloads every row the filter matches, which is the answer to "show me everyone who accepted the terms".