What Ovante reads in your CRM
Ovante reads your Salesforce or ChabadOne records only by id, by the Ovante id it wrote, or in a bounded match on one person's email or phone. It never lists, counts or exports them.
ProOwner
Ovante acts as the Salesforce user who connected, so it could see whatever that user can see. Salesforce has no narrower data permission to ask for. These tables are everything the connectors actually read and write; the same list is under What Ovante touches on each integration's page and in the connect dialog.
Salesforce
| Ovante writes | Why |
|---|---|
| The fields you mapped, on the Contact or Lead | Keep the person current |
| Campaigns under the "Ovante Events" parent, and their members | Attendance |
| Tasks for gifts and purchases | Giving and buying history |
| An Account, found or created by company name | Only when company is mapped |
| Ovante reads | Why |
|---|---|
| Contacts or Leads whose email or phone matches one registration, under your matching rules: their id, name, email and phone, a few at a time | Find the person to update |
| One record by id, when your duplicate rule pointed at it | Name it in History |
| The linked record's mapped fields, when the rule is only fill empty fields | Keep what you already have |
| Field names for the Contact, Lead and Campaign objects | The mapping picker |
| Accounts by exact name | Find before creating |
| Campaigns by name, members by Campaign and person, Tasks by person, subject and day | Never write the same thing twice |
ChabadOne
| Ovante writes | Why |
|---|---|
| A Web contact (name, email, mobile, Lead Source Web) and a Form Submission | A new person for your team to review |
| An Event campaign and its members | Attendance |
| An Income Charge and Payment, with their line items | Purchases and donations |
| Ovante reads | Why |
|---|---|
| Record types in ChabadOne's package | Create records of the right type |
| The linked contact, by id | Follow a merge to the surviving contact |
| Member statuses on Ovante's own Campaign | Add Confirmed and Declined if they're missing |
| Campaigns with the event's name | Find Ovante's Campaign again after a reconnect |
| Income by the Ovante id written on it | Never book twice, and handle refunds |
| Line items of Ovante's own Charge and Payment | Finish a booking a failed write left half done |
| The active payment types on Income (settings, no records) | Book money you collected yourself as Cash or Check |
| The members of one of Ovante's own event Campaigns: contact ids and descriptions only | Find a person again after a reconnect, when no Income names them |
Never
- A list, search or export of your contacts.
- A count of your contacts. Test connection checks access and counts only the people Ovante has linked.
- A field Ovante didn't write or you didn't map.
To limit it in Salesforce itself
- Connect as a user with less access, such as a staff user who can create contacts and campaigns but can't see giving history.
- Or create a dedicated integration user with a permission set that allows only the objects and fields above.
When you disconnect
Ovante revokes its access in Salesforce and deletes its stored sign-in, its links and its delivery history. Everything already in your CRM stays.
Was this helpful?
Related
Connect SalesforceSign in to Salesforce from Settings, Integrations. Ovante then acts as that Salesforce user, with exactly that user's access.Connect ChabadOneSign in to the Salesforce org that runs ChabadOne. Attendance, ticket purchases and donations start landing in ChabadOne's own records, with all three switches on.Reconnect or disconnect SalesforceReconnect 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.How ChabadOne sync worksEvery new person arrives as a ChabadOne Web contact for your team to review. Attendance becomes Event campaign members, and money becomes Income booked as a Charge and a Payment.