Consent BB feature bucket
This is the very first entrypoint for features that may or may not end up in the specification. The initial reason for the list is a tendering process in which suppliers may ask questions or advertise additional features that are not in the specification.
The feature bucket is the table below where we note and describe a feature, its origin and may escalate it as a Jira issue to discuss its implementation in the specification.
Feature | Description | Origin | Jira issue |
|---|---|---|---|
Automatic expiry | Consent Agreements can specify a maximum duration. Consent Records can have an expiry date. The system can notify of expiry through Pub Sub. | @Benjamin Balder Bach (I’m typing this in as an example) |
|
|
|
|
|