Partner & Channel Control
Consentrix separates policy acceptance from operational restrictions. After a decision is recorded, your team may still need to control sharing partners and active communication channels.
What This Covers
| Concept | What it means | Scope |
|---|
| Partner | A third party that may receive customer data | Per decision and per linked partner |
| Partner Block | Whether a specific partner is blocked for that decision | Customer + decision + partner |
| Block Channel | Whether a communication channel is active or blocked | Customer + product + channel |
How They Connect
- Partners are linked to template versions before decisions are recorded.
- Partner blocks are updated on the specific customer decision.
- Block channels are managed separately per customer and product.
Working Rules
| Rule | Why it matters |
|---|
| Partner control is tied to the specific consent decision | Blocking one partner does not affect every other decision |
| Channel blocking is product-scoped | A customer can allow email for one product but block it for another |
| These controls are related to consent but not identical to the original decision | Avoid treating them as the same audit event |
Common Scenarios
| Scenario | What usually happens |
|---|
| Customer wants to stop sharing with one partner | Update the partner block state on the decision |
| Customer no longer wants SMS for one product | Update block channel for that product |
| Compliance asks which partner was allowed at decision time | Review the decision and its partner-block state |