Documentation
Connect the First Provider
Use the first provider connection to prove signal quality, review access posture, and establish the operating context for downstream decisions.
Use the first connection to prove trust, not breadth
The first connection should answer the basic questions early: what access is required, what context becomes visible, and what proof survives after action.
Starting small reduces integration risk and gives security and platform teams a real review surface.
- Confirm the access model before enabling broad coverage
- Validate that spend signals map to a real owner queue
- Check that approval and export records are retained correctly
What good first-connection evidence looks like
Buyers should be able to see one issue move from raw signal into an owner-routed decision path with context preserved.
That evidence matters more than a large connector count during the first review.
- Named owner attached
- Checks or policy context attached
- Outcome and savings proof recorded
Next reads
Related content
Proof Pack
Identity and Approval Controls
See how identity expectations, approval gates, and owner-routed execution fit together in the decision path.
Open proofDocumentation
Decision History and Export Records
Keep a durable record of what changed, who approved it, and what outcome was captured after action.
Open docs