Per-tenant consent-log gate
Last updated 2026-06-14
Definition
The consent-log gate checks a per-tenant consent record before any message leaves. If a tenant has not granted consent to be contacted on a channel, Quri holds the send rather than risking an unwanted message. It is a delivery guard built into Relay 0.3.0, so compliance is enforced at the point of sending, not bolted on later.
How to do this in Quri
- Record each tenant’s consent for the channels you intend to use.
- Quri checks that consent record before every send on those channels.
- When consent is missing, the send is held instead of going out.
- Grant or update consent to let messages through, all kept in the consent log.
Frequently asked
- What does the consent-log gate actually block?
- Any send to a tenant that has not granted consent for that channel. Quri checks the consent record first and holds the message, so a contact only happens when it is allowed.
- How does this relate to opt-out?
- Opt-out is one person turning off messages they do not want. The consent gate is the tenant-level check that consent exists before sending at all — both have to clear for a message to go.