Specification · 03
Consent and permissions
Rules for recording consent and applying changes across the systems that use it.
When this is useful
A preference change may reach one system before another. The systems need agreed rules for which state to use and what to do while an update is pending.
My contribution
I map how consent is represented and propagated, working from the purposes and requirements agreed with the responsible teams.
A purpose-specific revocation is current while two cached copies still show an old grant; the proposed send gate blocks every send and cancels the queued job.
What it covers
- Purposes and recorded consent states
- Systems that supply or read each state
- Revocation updates and delays
- Suppression rules and differences between systems
- Uses that need further review or a decision
The output
A specification of consent states, permitted uses, update paths and unresolved decisions.
For an enquiry, describe the question and the systems involved.
contact@fiftystork.com ↗