Every setting explained
What each control on the Salesforce card does, what it changes in your org, and the one HubSpot option Salesforce doesn't have yet.
All of these live on the Salesforce card in Settings → Integrations. Only workspace admins can change them; everyone else sees them greyed out.
Changes save immediately — there is no "Save" button.
1. Contact sync — the master switch
The green (or amber) band at the top of the card. It has exactly two states.
| State | What it means |
|---|---|
| Paused | Sillage writes nothing to Salesforce on its own. |
| Active | Sillage pushes contacts according to the settings below. |
A freshly connected org always starts Paused. So does an existing connection the first time it sees this new settings panel. That is on purpose: connecting Salesforce gives Sillage permission to write, it does not give it instructions. You give the instructions below, then press Launch sync.
Pausing later stops future writes. It does not roll anything back — Contacts and fields already written to Salesforce stay exactly as they are.
One thing keeps working while paused: the Salesforce button on a lead in your Sillage leads table. That is you clicking, deliberately, on one lead (or a selection of them) — so Sillage does it. The pause switch only governs what Sillage does automatically.
2. Contact Push — when a Contact gets pushed
Two triggers exist in Sillage. This choice decides which ones are live.
On new intent only
A lead is pushed to Salesforce when a buying signal is detected on it. No signal, no push. This is the default and the conservative choice: Salesforce only ever receives people who did something worth reacting to.
Whether a lead who is not yet in Salesforce gets created is decided by Contact Creation Mode below — not here.
Choose this when: your CRM is the source of truth for "real" contacts and you don't want it filling up with people nobody has engaged.
Full mapped roster
Every contact matching your persona is pushed as soon as the account mapping for their company completes — signal or no signal. Intent data then arrives on those records automatically as signals get detected.
Two behaviours worth knowing:
- Newcomers only. Each mapping cycle pushes the people it has never pushed before. It does not re-push your whole roster every time. Contacts already in Salesforce keep getting their intent data updated through the signal path.
- It forces creation on. A roster push exists to put people in Salesforce who aren't there yet, so Sillage locks Contact Creation Mode to Create and update while this option is selected. You will see a note saying so, and the creation options become read-only.
Choose this when: you want your reps to see the whole buying committee of a target account in Salesforce from day one, and use intent to prioritise inside it.
Full mapped roster writes considerably more contacts than intent-only. On a large target account list this can be thousands of records.
Only create contacts with an email
This toggle appears only when Full mapped roster is selected. It is on by default, and should usually stay on.
Salesforce deduplicates contacts by email address. A contact pushed without one cannot be matched against what already exists, so you risk a duplicate of a person your org already has. With this on, Sillage skips contacts whose email it hasn't found yet — and picks them up on a later mapping cycle, once the email is available.
Turn it off only if you knowingly want LinkedIn-only records in Salesforce and accept the duplicate risk.
3. Contact Creation Mode — whether a missing person can be created
Update existing contacts only
Sillage only writes to Contacts that already exist in your org. It will enrich them with intent data, signals and status — but it never creates anyone.
There is one exception, and it is intentional: if someone on your team manually acts on a lead in Sillage — changes its status, edits it, pushes it from the leads table or the Chrome extension — that lead is created in Salesforce even under this mode. A human asked for it explicitly.
Create and update contacts
Sillage creates Contacts that don't exist yet, and updates the ones that do.
The one combination that silently does nothing: On new intent only + Update existing contacts only. A brand-new prospect who just showed a buying signal is not in Salesforce, so there is nothing to update — the signal is dropped and no record appears. Sillage shows a warning under the section when you select this pair. It is a valid setup if your CRM only tracks known contacts, but know that this is what it does.
4. Sync options
Create missing companies & associate
Off by default.
When Sillage pushes a contact whose company has no matching Account in your org, it creates the Account and associates the Contact to it. Existing Accounts are always matched and updated regardless of this setting — it only governs creating missing ones.
With it off, a contact whose company doesn't match an Account is still created — Salesforce Contacts don't require an Account — it's just left unassociated. Nothing is silently dropped either way; this setting only decides whether the Account gets created.
Leave it off if Account records in your org are created by another process (an import, a data provider, another integration) and you don't want a second source writing them.
Never touch customer contacts — HubSpot only
This switch is not on the Salesforce card. HubSpot's integration has a "Never touch customer contacts" option (lifecycle stage = Customer) that shields closed accounts from automated writes. Salesforce has no equivalent yet — every matched Contact is updated the same way, whether or not its Account is marked as a customer. The switch is deliberately left off the card rather than shown and ignored, so nothing here promises a protection that isn't running. If this matters to you today, ask your Sillage contact about timeline before launching the sync.
Quick reference
| Setting | Default | Safest for a first launch |
|---|---|---|
| Contact sync | Paused | Launch once the rest is set |
| Contact Push | On new intent only | On new intent only |
| Only create contacts with an email | On | On |
| Contact Creation Mode | Update existing only | Create and update |
| Create missing companies & associate | Off | Off |
These defaults apply to connections made since each option shipped. If your workspace connected Salesforce earlier, some toggles may sit in a different position — what the card shows is always the truth, so check it before your first launch rather than trusting the column above.