Manage SharePoint Docs Without Leaving Salesforce
Modern B2B teams often juggle CRM records in Salesforce and documents in SharePoint. Switching between the two platforms wastes time and can lead to lost or outdated files. For example, Salesforce’s built-in storage is limited (only 10 GB plus 2 GB per user) while SharePoint Online offers roughly 1 TB per user. Offloading large attachments to SharePoint (and accessing them from Salesforce) dramatically cuts costs and storage headaches. Once Salesforce and SharePoint are connected, your reps can browse and manage SharePoint files right from Salesforce. In practice this means clicking a link or opening a document on a Salesforce record page to view, download, or upload files without ever leaving the CRM. In the connected system, “you can search, navigate, and even create new folders or upload new documents directly without having to go back and forth between Salesforce and SharePoint”. In short, everything is brought into one place: users can link, view, and organize SharePoint assets on Salesforce records, eliminating tedious tab-switching.
Centralized Document Access in Salesforce
With a robust connector in place, Salesforce pages become a one-stop window into SharePoint libraries. For example, a sales rep can click a custom SharePoint component on the Account or Opportunity record and immediately browse that customer’s SharePoint documents in an embedded view. Users can open or preview files (Word, PDF, Excel, etc.) right in Salesforce, thanks to an integrated document viewer. They can even upload new files: clicking “New File” on the component lets them choose files from their device and send them straight to a designated SharePoint folder. Behind the scenes the connector auto-syncs that upload back to Salesforce so the record’s Files related list shows the new document immediately. As one expert noted, this unified interface means you can “link, view, and even organize SharePoint assets right on Salesforce records”. In practice, your team never has to hunt for emails or switch apps to find the latest contract or specification. It’s all available on the relevant Salesforce record.
Key capabilities include:
– Seamless Browsing and Search: SharePoint document libraries appear in Salesforce via an embedded interface, so users can search or navigate SharePoint files from within any record. The connector may expose SharePoint in an iframe or Lightning component, making the libraries as accessible as Salesforce lists.
– One-Click Opening and Upload: Clicking a SharePoint file link on the Salesforce page opens a preview (or the file’s native app) without leaving CRM. Likewise, the Upload or Link button lets users send new files to SharePoint folders in one step. SharePoint folders can be created on demand from Salesforce, so users never need to leave the record to manage files.
– Live Document Viewing: Users can review or download files on-screen. While edits typically happen in SharePoint or Office Online, any changes made there are instantly reflected back in Salesforce. In practice, users see the updated version immediately “if edits are to be made, the file will have to be opened in SharePoint, but thanks to the direct link, any changes will also be available to see when opening the record from Salesforce”.
– Automatic File Routing: The connector can auto-assign new attachments. For example, if a rep attaches a PDF to a record, the system can push that file into the related SharePoint folder and then display the SharePoint link in Salesforce. This keeps Salesforce lean while using SharePoint for actual file storage, seamlessly synchronizing the file in both systems.
Automated Folder Creation & Metadata Mapping
dgt27’s solution excels at keeping documents organized. You can configure an automated workflow so that creating a new Salesforce record automatically creates a matching folder in SharePoint. That folder can be named with merge fields from the record (e.g. combining Account name and record ID) and then instantly linked to the record. For example, opening a new Opportunity might trigger a SharePoint subfolder named “Opportunity – [Opportunity Name]” which then appears on the Opportunity page. This ensures every record has its own document folder without manual effort.
Behind the scenes, this uses Salesforce Flows or Apex triggers: a Flow rule watches for new records and calls the SharePoint API or dgt27’s Apex action to make the folder. On creation it stores the folder ID on the Salesforce record, so the two stay connected. You can even define complex hierarchies: child subfolders (for product lines, cases, etc.) are created automatically under the main folder. As one review put it, “the possibility to automatically create folders is the true advantage of this automation…upon creation, the folder can be automatically linked to the record”.
Metadata mapping further enhances this. Custom Salesforce fields (like Project Code or Case Type) can populate columns in SharePoint, ensuring search and filters are consistent. For instance, a “Region” picklist on Account could auto-fill a SharePoint column, so all Europe-region documents are tagged accordingly. This bi-directional data flow means that document metadata is unified, and reporting becomes easier.
Sync and Version Control
A critical post-integration benefit is that changes sync in real time. When a file is updated in SharePoint, the connector pushes the change to Salesforce so users see the current version. Likewise, if a file is uploaded or renamed from Salesforce, it appears immediately in SharePoint. This two-way sync removes outdated attachments and confusion about “the latest file.” If a user forgets and downloads a document from Salesforce, they always get the up-to-date SharePoint copy.
SharePoint brings robust versioning to the table. Unlike Salesforce Files (which have minimal version history), SharePoint maintains an enterprise-grade version history and metadata search. Your teams can see prior versions, compare changes, or restore an older file right in SharePoint. Because dgt27’s expert will surface SharePoint files inside Salesforce, your users effectively gain that same version control view. For example, if a finance team uploads a new contract revision in SharePoint, the newest version will appear on the Salesforce opportunity; if needed, they could click through to the SharePoint version history to retrieve earlier drafts. This tight coupling ensures the “latest file confusion” goes away, as SharePoint’s history is leveraged for Salesforce users.
Permission Sync and Security
Security remains paramount. dgt27’s expert respects both systems’ permissions. A user only sees the SharePoint documents they’re allowed to access. In practice, Salesforce profile or role settings can control who sees the SharePoint component, and SharePoint’s own folder permissions (Owner, Editor, Viewer roles) ensure sensitive files stay locked down. In fact, “both Salesforce and SharePoint permissions are respected to ensure you can still maintain full control despite the connection established between the two”. For example, if a user lacks SharePoint rights to a folder, we will simply hide those docs in Salesforce. Conversely, if a document is shared via Salesforce, the connector can propagate a SharePoint folder share link to grant access. This synced security model means no extra administrative overhead – your existing SharePoint access groups and Salesforce sharing rules carry over seamlessly.
Industry Use Cases
This connected document workflow helps many sectors work smarter:
- Real Estate: Agents can attach property photos, inspection reports, and contract scans to Salesforce property or opportunity records. When a new property listing record is created, the connector auto-creates a SharePoint folder (e.g. named by MLS number). All images and documents then live in SharePoint but show up on the listing’s Salesforce page. The brokerage saves CRM storage and ensures the latest lease agreements or blueprints are a click away in Salesforce.
- Healthcare: Clinics and hospitals store sensitive patient forms (intake documents, lab results, insurance records) in SharePoint. A connector links those files to Salesforce Health Cloud or case records. When a clinician opens a patient’s record, they immediately see associated SharePoint docs without hitting a separate portal. Folder automation can group files by patient ID, and synced permissions enforce HIPAA, only approved care team members (both in Salesforce and in SharePoint groups) can view those files.
- Finance: Banks and insurance firms often generate large client reports and policies. Instead of clogging Salesforce storage, these files are pushed to SharePoint. From the CRM, a relationship manager sees all contract and statement files for a client account because each Salesforce Account record links to its SharePoint folder. SharePoint’s robust version history means auditors always find the latest approved document in Salesforce. Offloading to SharePoint also dramatically reduces file storage costs, as noted above.
- Manufacturing: Companies can automatically tie product manuals, CAD drawings, and compliance certificates to sales or work order records. For instance, when an Opportunity is created for a new machine sale, the connector may link a SharePoint folder of spec sheets and user guides. Engineers and sales reps then find those documents inside Salesforce when updating the order. This integration ensures everyone “will know for sure where the extra details about the product can be found and shared”.
By industry or function, the pattern is the same: relevant SharePoint documents become part of the Salesforce record page, saving time and aligning workflows across departments.
Key Features
The connector goes beyond simple linking. It provides real-time sync (bi-directional updates), automated folder creation, and metadata mapping as built-in features. Once configured, these tools require no manual effort:
- Real-time Sync: Any file added, updated, or deleted in Salesforce or SharePoint is immediately mirrored on the other side. This keeps Salesforce’s Files related lists and SharePoint libraries perfectly aligned at all times.
- Automated Folders via Flow: Admins set up Salesforce Flow or Process Builder rules to define how folders are created and named in SharePoint. For example, you might say “When a new Account is created, create a folder named AccountName_ID in Library X and link it.” The connector handles this logic automatically, using record fields (merge fields) to name folders and even support multi-layer folder structures if needed.
- Metadata & Search Mapping: Custom fields in Salesforce (like region, project code, or status) can populate corresponding SharePoint columns. This means if a document is updated in Salesforce (e.g. a status change on the record), the SharePoint metadata is updated too. Your teams get fast filtering and search in both systems based on the same fields.
- In-App File Previews: The integration often includes a preview component so users can click and view documents in Salesforce. (Under the hood it may use Microsoft Office Online or SharePoint’s preview for Word, Excel, PowerPoint, PDFs, etc.) Users can download or print from the preview, or when editing is needed click an “Edit” button that opens the file in SharePoint/Office Online.
- User-Friendly UI: Non-technical users get a clean interface (often a Lightning component) where they see a list of files and folders, with “New,” “Upload,” “Link,” and “Share” buttons. No Salesforce admin navigation is required beyond placing the component on the page. One click to attach a new file or link to an existing folder, everything happens inside the Salesforce layout.
These features let your teams focus on content and process, not on manual file management. There’s no need to schedule batch syncs or worry about version drift; dgt27’s platform keeps everything current in the background.
FAQ (Frequently Asked Questions)
Can users upload a document to SharePoint from within Salesforce?
Yes. The connector adds an “Upload” option on Salesforce record pages. Clicking it lets users select files from their computer and specify which SharePoint folder they should go to. Once uploaded, the file immediately appears in the record’s Files list and in the linked SharePoint library.
What happens when a document is edited?
Edits are typically made in SharePoint (or in Office Online). After a user opens the file (via the Salesforce interface) and makes changes, those changes are saved back to SharePoint. Because the systems are synced, anyone viewing the file from Salesforce next sees the updated version. SharePoint’s version history also records the change in case you need to revert.
Is syncing really instant?
Yes, updates occur in real time. For example, if a user uploads a file in Salesforce (which dgt27 automatically moves to SharePoint), the Salesforce interface immediately shows the new link. Similarly, a file added directly to the linked SharePoint folder shows up on the Salesforce record without delay.
How are permissions handled?
The connector enforces both sets of permissions. A user will only see files in Salesforce if they have the right SharePoint role (e.g. Viewer or above) for that folder. Likewise, Salesforce sharing controls can be used to hide the component itself from unauthorized users. This means no one gains access to a file through Salesforce unless they were already allowed in SharePoint.
Do I need any special Salesforce license?
No extra Salesforce licenses are required beyond what app or flows run on. The integration runs on standard platform features (Lightning Components, Flows, and SharePoint APIs). It works with Salesforce Enterprise or above. (On the SharePoint side, an Office 365 or SharePoint Online license is needed, but this is typically already in place for corporate users.)
Contact dgt27
Managing SharePoint documents inside Salesforce unlocks efficiency and collaboration for your teams. To learn how dgt27 can tailor this solution to your business, contact us today. Email info@dgt27.com or visit our Contact page to schedule a demo. Our consultants will help you map out a seamless document strategy that keeps files organized, secure, and directly accessible in Salesforce.


Leave Comment
Was this blog helpful?
Was this blog helpful?