Hi Everyone,
I'm a Salesforce Administrator currently learning about SharePoint and Salesforce integration for document management, and I'd love to learn from your experience.
I'm interested in understanding how organizations use SharePoint with Salesforce to manage documents, folders, security, and document access efficiently. I'm also curious about best practices for folder structures, metadata synchronization, version control, and providing a smooth user experience.
As I'm still exploring this area, I would greatly appreciate any insights, recommendations, or lessons learned from real-world implementations.
Looking forward to hearing your ideas and experiences. Thank you!
#Trailhead Challenges #Salesforce Developer #Salesforce Admin #Salesforce #Sales Cloud #Trailhead
@Roopa Sharma, This is a good area to learn early. Many orgs end up with documents in both systems, and the friction shows up exactly where you listed. Here is how each one tends to play out once a setup is live.
- Where the documents live -
- SharePoint as the home, with Salesforce records pointing to it. The usual choice when the company already runs on Microsoft 365.
- Salesforce Files, when volumes are small and only CRM users need the documents. The Files related list is flat, with no folders per record.
- Ways to connect the two
- Files Connect (native): lets users browse, search and attach SharePoint files from Salesforce, but it does not create a folder per record.
- Power Automate: a good fit if your team already builds on the Microsoft side. The trade-off is that the logic lives outside Salesforce, on a premium connector.
- AppExchange apps: compare them on four things. Does Flow create a folder when a record is created? Do uploads from the record go straight to SharePoint? Do SharePoint's own permissions still apply? Can you trial it in a sandbox first?
- Your questions, in practice -
- Folder structure: mirror your data model (Account, then Opportunities, then each opportunity), with the same subfolders on every record. Add the record ID to folder names so a rename never breaks a link.
- Metadata: tag files with SharePoint columns such as document type, status and record ID, instead of relying on folder names.
- Version control: let SharePoint's version history handle it, and avoid saving copies back into Salesforce.
- Security: SharePoint decides who can open a file. Salesforce sharing does not carry over to SharePoint on its own, so plan who updates access when an account changes owner.
- User experience: users should reach a record's folder from the record page, without searching SharePoint.
If you go the AppExchange route, CloudFiles is one app that works this way with SharePoint. With its flow actions, each record gets a folder when it's created, and files are tagged as they arrive. Users open that folder from the record page, and SharePoint's permissions decide what each person can see. https://appexchange.salesforce.com/appxListingDetail?listingId=a0N4V00000Gh9uFUAR
Disclosure: I work at CloudFiles.
- Where the documents live -
