# Integration lifecycle How supported Aiviance connections establish consent, scope data and handle synchronisation without exposing internal interfaces. Aiviance integrations connect a defined external source to a defined entity. A connection is not a general grant to every record in an account. ## Establish a connection Supported provider flows start inside the signed-in product. Where a provider uses OAuth or another consent flow, Aiviance initiates that flow, validates the returned state and completes the connection for the current user and entity. The providers and connection types available depend on region, workspace and product configuration. A provider present in the codebase or subprocessor register is not, by itself, a promise that every customer can connect it. ## Synchronise within the source boundary Each connection retains provider identity, owning entity and lifecycle state. Supported sync operations use that context to import the records or portfolios covered by the connection. Reconnect, refresh, manual sync and disconnect actions are available only where the corresponding provider adapter implements them. Imported information remains subject to product review and accounting controls. A provider response is not silently converted into an authorised or posted financial decision. ## Disconnect and investigate Disconnecting a source stops future access through that connection. Existing financial records follow their own retention and correction rules; disconnecting does not silently rewrite historical books. Operational webhooks, provider callbacks and internal registry routes are implementation interfaces, not public partner contracts. A partner should use only the authentication, events and schemas supplied in its documented integration agreement. For the end-user view, read [Connect financial data](/docs/product/connections). For the public-contract boundary, read [Aiviance developer platform boundary](/docs/developers/platform-boundary).