Help

Reconnect or disconnect Salesforce

Reconnect signs in again and keeps your settings. Disconnect revokes Ovante's access in Salesforce. Reconnecting to the same Salesforce org keeps every link; a different org starts over.

ProOwner
On this page

Reconnect when Salesforce stops accepting Ovante's sign-in, or to connect as a different Salesforce user. Disconnect when you want Ovante to stop for good: it ends Ovante's access inside Salesforce, not only Ovante's copy. Both work the same on the ChabadOne page.

Reconnect

  1. 1
    Open Settings → Integrations, and click Open on the Salesforce card.
  2. 2
    Click Reconnect on the health line, or open the menu on the top row and click Reconnect Salesforce.
  3. 3
    Sign in to Salesforce and approve the connection.
  4. 4
    You're back on the Salesforce page, and the health line says Syncing.

Your matching, field mapping and switches stay as they were. Reconnecting needs Pro.

Same Salesforce org or a different one

You sign in toWhat Ovante keeps
The same Salesforce orgEvery link between people and records, the parent Campaign, and the fact that past events were brought in
A different Salesforce orgYour settings only. The links mean nothing in the other org, so Ovante drops them and matches people again, and Bring in past events is available again.

Ovante also revokes the old sign-in in Salesforce once the new one is stored.

What happened while it was off

While a connection waits for a reconnect, Ovante holds new activity instead of dropping it. Once you reconnect, it sends what it held from recent days. Anything older stays in History, where you can Replay it.

Disconnect

  1. 1
    Open the menu on the top row and click Disconnect.
  2. 2
    Click Disconnect to confirm.

Ovante revokes its access in Salesforce, deletes its stored sign-in, the links and the delivery history, and stops sending. Everything already in Salesforce stays there.

Connecting again later

Ovante finds what it wrote before instead of duplicating it: people through your matching rules, and Campaigns by their name and the event id in their description.

What happens next

When
You reconnect to the same Salesforce org
Then
Ovante keeps every person it had linked, the event Campaigns and the fact that past events were brought in. Connecting a different org starts clean.
When
You disconnect Salesforce or ChabadOne
Then
Nothing more is sent, and Ovante revokes its access in Salesforce, not only its own copy. Records already in your CRM stay there.
When
A connection is waiting to be reconnected, or a webhook was turned off after failing
Then
Ovante keeps a record of what happens meanwhile. Reconnecting, or turning the webhook back on, sends the recent held deliveries.
Every rule in How Ovante decides

Good to know

  • When Salesforce stops accepting the sign-in, Ovante emails the owner, and the health line says Not syncing with Reconnect. A weekly email reminds the owner of any connection still waiting.
  • There's no pause. Disconnect is the way to stop.