Johan Sandoval
a5c0a5210e
Articles get their own address (shareable, back/forward work); the list is searchable by title and text, shows the article count, and is grouped into Applications and Troubleshooting & Guides via a hidden category line set from the editor. PDF export lays out at page width with page breaks, a title block and page numbers; Print uses the browser's vector print. Inline code is a pill that glows blue on hover, blockquotes no longer squeeze, and GitHub-style [!NOTE] alerts render. [[Badge]] syntax inside code spans is left alone.
25 lines
1.0 KiB
Markdown
25 lines
1.0 KiB
Markdown
<!-- category: Applications -->
|
|
[[Blue:Licensed]]
|
|
|
|
# Salesforce
|
|
|
|
Salesforce itself is web based. Desktop components are only needed by some Sales and Support users.
|
|
|
|
| Component | Who needs it |
|
|
|---|---|
|
|
| Salesforce for Outlook / Outlook integration | Sales reps who log email to Salesforce |
|
|
| Salesforce Data Loader | Sales Ops / admins doing bulk imports |
|
|
|
|
## Install
|
|
1. Install the components that were on the old device (check *Missing Software* on the **All Devices** page).
|
|
2. Installer share: [[Copy:\\fileserver\software\Salesforce\]]
|
|
3. **Data Loader** needs a Java runtime. The installer bundles one; accept the defaults.
|
|
|
|
## Outlook Integration
|
|
The modern integration is an Outlook add-in deployed from the Microsoft 365 admin center. After migration:
|
|
1. Open Outlook and look for the **Salesforce** button on the ribbon.
|
|
2. If it's missing, wait for add-in sync (up to 24 hours) or ask the M365 admins to confirm the assignment.
|
|
|
|
## Single Sign-On
|
|
Users sign in with **Use Custom Domain** > `company` > SSO. They shouldn't need a separate password.
|