Document connector recipient export-screening evidence
A control can exist on paper while its evidence remains scattered across the workflow.
Teams often need to preserve useful integrations while making eligibility decisions traceable.
“We can’t pause every connector, but I also can’t explain which approvals actually exist.”
Dalili Ochieng · Data Platform Owner
He manages approved integrations for a global analytics team and needs to keep downstream workflows running.
What pulls against what
- integration continuity vs. screening proof
- audit certainty vs. workflow speed
- legacy cleanup vs. forward control coverage
What is at stake
A defensible record can preserve customer integrations while avoiding an audit finding that grows with every new activation
Why Databricks
In cloud analytics environments, external connections can make compliance evidence as important as the technical control itself.
Written for
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.