Design · Create · Ops & Automation
Partner data-sharing rules mapped to tiers and risk
A complete, partner-tier-by-population data-sharing rule spec: for each tier and population the chosen match condition and exact fields to expose, with PII handling and hard-excluded accounts spelled out, so sharing is configured consistently.
You receive: A structured rule-set (one row per tier x population) with match_condition, data_to_share, pii_rule, and exclusions, plus a coverage check that every combination is specified from the allowed vocabulary.
Part of Distribution, Win Market
What you receive
The shape of your delivered file. Your result is generated for your inputs.
Your deliverable is a structured document carrying these fields:
- Data to share
- Exclusions
- Match condition
- Pii rule
- Population
- Rules
- Tier
Some fields carry set values, drawn from:
contact_person, contact_email
customers, prospects, churned
json, csv
mask, hash, consent_required, exclude
never, overlapping, always
none, account_name, account_domain, tier_or_segment, usage_summary, contact_person, all_fields
strategic, integration, reseller
tier, population, match_condition, data_to_share
Opens soon
STUD opens runs for everyone soon, on every play at once.
Scope of the check
What's verified: Settles deterministically that the rule set is COMPLETE (every tier x population covered exactly once) and WELL-FORMED (match_condition and data_to_share drawn from the allowed vocabulary, person-level shares carry a PII rule, never-rows share nothing, hard-excluded accounts are excluded, no duplicate/conflicting rule); it explicitly does NOT settle that the posture is legally sufficient or that the chosen conditions are the right business call (legal sufficiency and strategy are judgment, flagged for counsel and never given a green check).
Get early access to STUD the day it goes live.