Integration Platforms
Part of Workflow documentation and ownership
Assigning an owner to orphaned integrations
Stabilise an ownerless integration, identify the teams that depend on it and complete an explicit operational handover.
Treat an integration with no recognised owner as an unresolved operating responsibility. Give its alerts and exceptions an interim response route, establish what it does and who depends on it, then ask a team with the authority and capacity to accept ongoing ownership. Record that acceptance: changing a tag alone does not complete the handover.
Stabilise the unknown integration
Identify the deployed workflow, its connections, source, destination and any available run or change records. Do not disable it merely because its builder left or its description is stale. A quiet integration may run on a schedule or a rare event. Mark ownership unconfirmed, assign interim triage and provide an escalation route while its purpose is investigated.
The interim team needs a way to receive incidents, preserve evidence and reach relevant system owners. Interim triage does not grant authority to change business records or accept permanent responsibility. If a credential belongs to a departed employee, involve the identity and system owners in a continuity decision rather than sharing that person's access.
Find the team that can own the outcome
Trace a representative item from source to destination. Ask the source owner why work is sent, the destination owner what confirms completion and the business team what would be missed if the integration stopped. Configuration and run history may reveal technical contacts, but they do not establish who should make business decisions.
Role / Responsibility to assign
- Business decision owner
- Defines eligible work and resolves business exceptions
- Operating owner
- Investigates, changes and recovers the integration
- Endpoint or access owner
- Maintains the connected system, account or API permission
One team may hold several roles. If two teams share the route, agree who owns the integration as a whole and where each endpoint hand-off begins. A shared mailbox is a contact route; it still needs a team accountable for decisions.
Roles and Responsibilities in Integration Ownership
- Business decision owner
- Defines eligible work and resolves business exceptions.
- Operating owner
- Investigates, changes, and recovers the integration.
- Endpoint or access owner
- Maintains the connected system, account, or API permission.
Make handover an acceptance decision
Give the proposed operating owner an evidence pack: purpose, version, dependency map, connection identities, alert route, unresolved items, recent changes and operating runbook. Mark missing information as missing. Confirm that the receiving team can inspect the relevant systems, obtain permissions, respond to failures and request decisions from the business owner.
Record the receiving team's acceptance, effective date, fallback contact and inherited open work. Update the workflow register and platform metadata. Check alert delivery and access through a safe exercise where possible, recording results only after the exercise. If no team can accept ownership, keep the interim response route and escalate the decision to the accountable service or business lead.
Handover Acceptance Checklist for Integration Ownership
- Evidence pack providedPurpose, version, dependency map, connection identities, alert route, unresolved items, recent changes, operating runbook.
- Receiving team can inspect systemsConfirmed ability to access relevant systems and obtain permissions.
- Team can respond to failuresAgreed process for incident response and recovery.
- Decision authority confirmedReceiving team can request decisions from business owner.
- Acceptance recordedEffective date, fallback contact, inherited open work documented.
Decide what happens next
The investigation may show that the integration should remain, change or be considered for retirement. If it stays in service, review its documentation and access when either endpoint changes. If retirement is proposed, identify consumers and unfinished work before stopping new starts. Missing ownership is a reason to investigate; it is not evidence that nobody uses the output.
