Module guide

Data Operations

Governed connector operations, sync runs, issue triage, onboarding decisions, and readiness review for external data flows.

2026-07-20Data operations/intelligence

Runtime availability

Available in the customer workspace for authorized operational users. It exposes customer-visible connector state and readiness rather than protected runtime internals.

Who uses this module

managersadministrators

What users can do

Review connector state, sync runs, issue queues, and readiness blockers.
Moderate onboarding decisions and reconciliation issues.
Track whether an external data flow is live, pending, or limited to proof fixtures.

Access and approval limits

Connector state is organization-scoped even when enterprise administrators supervise multiple countries.
Operational state labels describe readiness and blockers without exposing secret or vendor-only configuration.
Onboarding decisions and reconciliation overrides stay in governed queues.

Key workflows

These workflows describe how the visible customer workspace is intended to be used.

Review a connector blocker

Use the queue views to identify whether a blocker comes from readiness, sync, reconciliation, or onboarding state.

1Open Data Operations for the active organization.
2Select the connector, run, or issue card that needs review.
3Use the visible blocker labels to route the next action to the correct lane.

Core concepts

Connector readiness

Readiness indicates whether an integration can be trusted for customer workflow use inside the selected organization.

Reference

Covered screen

`/intelligence`

Troubleshooting

A connector is stuck in proof-only or pending state.

Review visible readiness blockers, latest run status, and onboarding decisions.
Check whether the organization scope is the expected one.

Escalate with the connector name, organization, and visible blocker labels.

Connected modules

These areas usually carry the next action, source record, or downstream evidence.