Consent policies define what a customer is asked to agree to, how that content changes over time, and how each response is recorded.
What This Covers
How They Connect
- A product owns the consent requirement.
- A template groups one consent item over time.
- A version stores the exact content the customer saw.
- A decision records the customer's response to that version.
Working Rules
| Rule | Why it matters |
|---|
| Create a new version, not a new template, when wording changes | Preserves history |
| Record decisions against the exact version shown to the customer | Keeps the audit trail defensible |
| Set product scope correctly from the start | Reporting and downstream controls depend on it |
Common Scenarios
| Scenario | What usually happens |
|---|
| Legal text changed | Add a new template version |
| New business service needs consent | Create a new template under the right product |
| Customer agreed or withdrew | Record a new consent decision |
| Compliance asks what version was accepted | Review the decision and linked version |