Recording consent
What CommonLynk records when a person agrees to their data being held, and what it deliberately does not.
Consent is captured on the individual’s own record, in the Status and Consent section of the registration form.
What is recorded
Two things: a tick box carrying a fixed statement, and a date. The statement reads that the person consents to the collection and storage of their personal data for service delivery, follow up and reporting, in accordance with the organisation’s data protection policy.
Where the person has consented, their record shows a Consent given marker in the header and a Consent row on the Identity card giving the date.
Making consent compulsory
Consent behaves like any other field on the Registration Form Fields screen. If your policy is that nobody may be registered without recorded consent, mark the consent tick required there and the form will refuse to save without it.
What is not recorded
- Consent is held for individuals only. Households and establishments have no consent field.
- There is one consent statement rather than a choice of purposes, so you cannot record consent for one use and not another.
- There is no history of consent being given and later withdrawn. The tick and the date show the current position, and editing them replaces what was there.
- Consent is not part of the bulk export or the import template, so it can only be set on the form. It is included in the portable copy produced for a data access request.