Salesforce, Microsoft Teams, and SharePoint: One Set of Files
Your sales team works in Salesforce. Your colleagues and partners work in Teams. Keep them connected through the same SharePoint documents with sFiles.
Microsoft Teams stores channel files in SharePoint. sFiles connects Salesforce records to those SharePoint locations, so Salesforce users and Teams collaborators can work with the same documents instead of maintaining separate copies. File access and Teams channel membership remain separate configuration decisions.
How do Salesforce, Teams, and SharePoint work together?
Different applications do not have to mean different copies of the same document.
Consider a familiar handoff: a salesperson uploads a proposal in Salesforce, a project manager asks for it in Teams, and someone emails an attachment to an external partner. Before long, the team is comparing versions instead of moving the work forward.
The better starting point is a shared file location. Teams already uses SharePoint for channel documents, and sFiles can link that SharePoint content to the Salesforce record where your business manages the relationship or project.
Salesforce
The Account, Opportunity, or project record gives the documents their business context.
sFiles
Users browse, upload, and open linked SharePoint documents from the Salesforce record.
SharePoint
The underlying site, document library, and folder hold the channel's documents.
Microsoft Teams
Colleagues and approved partners discuss the work and collaborate on documents.
A shared-document architecture, not a message or membership synchronization flow.
The goal is one set of documents, with different ways to access it. When both interfaces point to the same SharePoint item, there is no separate Teams copy to keep aligned with a Salesforce copy. Saved changes are available when that item is reopened or its listing refreshed.
Where does a Teams channel store its files?
Start with the channel type. A standard channel uses a folder in the parent Team's SharePoint site. Private and shared channels have separate SharePoint sites, so a single Team can involve more than one site.
| Channel type | File location | Membership model |
|---|---|---|
| Standard | A channel folder in the parent Team's SharePoint library. | Team members, including admitted guests, can access standard channels. |
| Private | A separate SharePoint channel site. | A selected subset of the parent Team, including guests already in that Team. |
| Shared | A separate SharePoint channel site. | Selected participants. External participation uses Microsoft Entra B2B direct connect. |
Channel membership is summarized here. Individual file-sharing links and permissions also need review.
Files uploaded into one-to-one or group Teams chats are generally stored in the uploader's OneDrive for Business. A link to a document already in SharePoint leaves it in its existing location. This article focuses on channel documents in configured SharePoint locations, not every file exchanged through Teams.
For an existing channel, use Open in SharePoint from its files area to identify the destination. Link sFiles to that site, library, and folder rather than creating a similarly named folder somewhere else.
Three ways to connect the work without duplicating files
These are illustrative workflows, not customer case studies. Each assumes the required SharePoint locations and user permissions have been configured.
Let partners stay in Teams while your staff works in Salesforce
Imagine a membership organization that manages committees in Salesforce and already uses Teams channels to collaborate with external members. Staff need meeting materials and working documents beside the committee record, but members are comfortable working in Teams.
Instead of introducing another document process, link the Salesforce committee record to the channel's SharePoint location. Staff can upload materials through sFiles, while authorized members review or update those documents through Teams. A file uploaded by a member to that location is accessible from the linked Salesforce record.
Staff upload an agenda from the committee record. Members add supporting documents in the Teams channel. Staff reopen the record and work from the same collection.
The benefit: external collaborators keep their familiar workspace, and internal staff do not have to download, re-upload, and reconcile a second set of files.
External collaboration does not always mean a shared channel. Guests can participate in a Team; private-channel guests must also belong to that Team. Shared channels use a different external identity model and require cross-tenant configuration by both organizations.
Hand over the project, not another folder of attachments
Consider a services business where sales manages Opportunities in Salesforce and implementation works in Teams. When a deal closes, delivery needs the signed scope, requirements, and customer documentation.
Design the handoff around a shared SharePoint location. sFiles can associate project records with existing Teams-backed sites, and related-record configurations can expose a parent record's folder without copying its contents.
For example, the Salesforce project could retain a connection to the agreed project workspace while delivery works there through Teams. Enterprise Flow actions can create additional working folders or update SharePoint columns when your configured Salesforce process reaches the handoff stage.
An Opportunity closes. A configured Salesforce process prepares the document handoff. Delivery opens the shared project files in Teams, while the account owner retains access through the linked Salesforce record.
The benefit: the customer relationship continues across departments without a second document collection becoming the delivery team's unofficial source of truth.
Creating a new Team, creating a channel, or assigning its members is a separate provisioning step. Linking a folder does not perform those actions.
Bring legal and finance into the document, not into another copy
Picture a salesperson preparing a customer contract while legal and finance coordinate their reviews in Teams. Emailing each reviewer an attachment makes it harder to know which version the salesperson should send.
Keep the working contract in an appropriately restricted SharePoint location and connect it to the Opportunity through sFiles. Reviewers can open the document through Teams or Microsoft 365, while the salesperson opens the same saved document from Salesforce.
Sales uploads the draft through sFiles. Legal reviews the shared Word document. Finance checks the commercial terms. Sales opens the saved document from the Opportunity before completing the approval process.
The benefit: fewer attachment chains and less uncertainty about which document contains the latest saved changes.
Keep approval tracking explicit. A Teams conversation or a saved document change is not automatically a Salesforce approval. Your approval status, reviewer notifications, and final distribution should follow a separately configured business process.
What does sFiles handle in this architecture?
sFiles connects the document layer to Salesforce. Its documented site, library, and folder selection feature specifically supports linking Salesforce records to Teams-backed SharePoint locations.
Work from the record
Browse, upload, and open linked SharePoint files in the context of the Salesforce record.
Use the right workspace
Map records to different SharePoint sites and libraries instead of forcing every project into one destination.
Organize the process
Use supported Flow and Apex actions for document operations such as folder creation and metadata updates.
Manage collaboration access
Handle Teams membership and external identity requirements through the appropriate Microsoft 365 configuration.
Saving into a Teams-connected location does not, by itself, post a channel message or add someone to the channel. Document availability, notifications, and membership should be treated as separate requirements.
The documents can be shared. The permissions still need a plan.
Imagine an Opportunity visible to three salespeople, with its documents placed in a standard channel belonging to a 50-person Team. Restricting the Opportunity does not remove those other Team members' Microsoft-side access.
Salesforce record access and direct Teams or SharePoint access are separate paths. Under per-user authentication, sFiles uses the connected user's Microsoft permissions. Your Microsoft 365 access model still controls what someone can reach outside Salesforce.
Granting access to a SharePoint file is not the same as adding someone to a Teams channel. sFiles offers configurable file and folder permission actions. Private and shared channel-site membership, however, is controlled through Teams, not independently through SharePoint.
For external collaboration, define who can read, edit, invite others, and retain access when the engagement ends. Review direct sharing links as well as group membership; a separate permission grant may survive removal from a channel.
Design recommendation: keep internal commercial discussions and partner-facing deliverables in deliberately separated locations. Do not assume that hiding something in the Salesforce interface makes it private in Teams.
Start with one channel and one Salesforce record
A focused test can establish the architecture before you automate the wider process.
- Identify the channel location. Open its files area in SharePoint and confirm the site, library, and folder being used.
- Link a test record. Configure sFiles to use that existing location. Include the correct site and library overrides where required.
- Test both directions. Upload through sFiles and locate the file in Teams. Save a change through Teams, then reopen the same file from Salesforce.
- Test the access boundaries. Use an internal user, an external participant where relevant, and someone who should not have access.
- Add automation after the connection works. Define folder operations, metadata updates, notifications, and membership changes as distinct tasks.
This is a suggested validation sequence, not a claim that every workflow is preconfigured. Use the sFiles linking and Flow documentation alongside your Microsoft 365 policies.
The real opportunity is not making everyone adopt the same application. It is keeping the business connected to the same documents.
Frequently asked questions
Are Microsoft Teams files stored in SharePoint?
Files uploaded to Teams channels are stored in SharePoint. Files uploaded into one-to-one or group chats are generally stored in the uploader's OneDrive for Business. Sharing a link to an existing document does not move that document into a channel's SharePoint location.
Can Salesforce users access documents from a Teams channel?
Yes. With sFiles configured to use the channel's underlying SharePoint site, library, and folder, authorized Salesforce users can work with those documents from the relevant record. The connection must target the actual channel location, not just another folder with the same name.
Can external partners stay in Teams while employees use Salesforce?
Yes. In this workflow, external collaborators access the documents through their approved Teams access, while internal users access the same SharePoint location through sFiles. The external collaborators do not need to use Salesforce for that document workflow, but their Microsoft access and sharing requirements still apply.
Does sFiles synchronize Salesforce permissions with Teams membership?
Connecting a Salesforce record to SharePoint does not synchronize Teams membership. sFiles offers configurable file and folder permission actions, but those are not equivalent to adding or removing a person from a Team or channel. Channel-site membership must be managed through Teams.
Do we need sFiles Enterprise for this?
Enterprise is the fit when the solution requires multiple SharePoint sites or libraries, end-user site and folder selection, or the broader Flow and Apex automation toolset. A simpler, fixed-location document workflow may fit Standard. Confirm the required actions and configuration against the current feature comparison.
Does uploading through sFiles automatically post a Teams message?
Do not treat document availability as a Teams notification. Saving a file in a channel's SharePoint location makes it available through that location; posting a channel message or updating a Salesforce approval status needs a separately configured workflow.
Bring your Teams documents into the Salesforce workflow
Already collaborating in Teams? Bring one channel and one Salesforce use case to a demo. We will show you how sFiles can connect the documents without replacing the way your team works.