Connections
Reconnect or disconnect a provider
Restore authorization for the same account, or deliberately stop collection while retaining history.
Before you start
Who this is for: Administrators with the required connection action permission.
- Identify the exact connection and dependent tests or data workflows.
- Agree on the effect of stopping collection before disconnecting.
Follow these steps
Choose the intended action
Open the connection and inspect its identity, lifecycle, and recent issues. Use Reconnect to restore supported authorization for the existing binding. Use Disconnect when the intended result is to stop collection. Discard draft applies to a never-connected draft and has different deletion behavior.
Reconnect where offered
Choose Reconnect when it is available and follow the provider’s authorization instructions. Confirm that you are signing in to the same external account. Recovery options vary by provider. If there is no Reconnect button, ask the connection administrator to check the setup instructions and the connection’s latest issue before changing credentials.
Disconnect deliberately
Choose Disconnect, read the confirmation, and enter a Reason. The dialog explains that stored credentials are revoked, syncing stops, and collected history and the audit trail are kept. Confirm only after reviewing the effect on dependent work.
Verify the result
After reconnection, inspect the binding and a subsequent completed run. After disconnection, verify the disconnected state and retained history. If discarding a draft, review the explicit warning that the never-connected draft is permanently deleted before confirming that separate action.
What you should see
Authorization is restored through the supported path, or collection is stopped with a recorded reason and retained connection history.
If something doesn’t look right
Reconnect returns no supported handoff
Read the error and contact the connection administrator or support. Do not paste credentials into an unrelated form.
The provider account has changed
A different bound subject requires a new connection; do not use reconnect to replace the identity.
Tests become stale after disconnect
Coordinate the intended replacement source or inactive scope. Stopping collection does not create fresh test results.
Still need a little help?
Ask the assistant about these steps, or tell our team where you got stuck.
Contact support