Cross-Platform File Sharing
Files shared in Slack appear in Teams and files from Teams reach Google Chat. SyncRivo relays attachments on all five platforms; bytes pass through memory only.
The file sharing problem in multi-platform teams
When engineering shares a Figma export in Slack and the design review discussion happens in Teams, the file never crosses the bridge — colleagues in Teams have to ask for it to be re-shared, breaking the conversation flow. SyncRivo solves this by routing file attachments and their metadata bidirectionally, so shared content follows the message wherever it goes.
How cross-platform file routing works
- 1
File event detection
SyncRivo detects messages with file attachments from each platform in real time via native platform events.
- 2
Download in memory
SyncRivo downloads the file from the source platform API. File bytes pass through memory only and are never written to SyncRivo storage.
- 3
Upload to the destination
The file is uploaded to each bridged destination conversation, alongside the sender's name.
- 4
Platform-appropriate rendering
Where the destination supports it the file appears as a native attachment; in some cases (such as Teams group chats with the bot) it appears as a header message with a link.
How Cross-Platform File Sharing works in SyncRivo
Event ingestion
File attachments arrive through the same event pipeline that powers message routing: Slack Events API, Microsoft Bot Framework and Graph for Teams, Google Chat app events, Zoom webhook events and Webex webhooks. Each event is signature-verified before the attachment is fetched from the source platform.
No file storage and no content scanning
File bytes pass through memory only and are never stored by SyncRivo. SyncRivo does not scan files with a DLP service; use your platforms' own DLP controls, and switch attachment relay off per connection where files should not cross a bridge.
Delivery
SyncRivo uploads the file to each destination platform using that platform's API. On Slack and Zoom, each file is posted as its own message. On Webex, a header message is followed by the file. Files posted to Google Chat keep the app's authorship rather than the original sender's.
Platform-specific behavior
Here is how Cross-Platform File Sharing behaves across each messaging platform we support. Preview fidelity and attribution vary because each platform uses a different file model.
| Platform | Behavior | Known limitation |
|---|---|---|
| Slack | Files downloaded from Slack and uploaded to Slack through the Slack API; one message per file. | File messages stay authored by the SyncRivo app rather than the original sender. |
| Microsoft Teams | Files downloaded from Teams through Microsoft Graph; posted as native file cards in delegated or mirrored chats. | Group chats that use the bot get a header message with a link instead of a native file card. |
| Google Chat | Attachments downloaded from and uploaded to Google Chat through the Chat API. | Uploaded files are authored by the app, not the original sender. |
| Zoom Team Chat | Files downloaded from and uploaded to Zoom Team Chat; one message per file. | Messages are posted from the app, not as the original sender. |
| Cisco Webex | Files downloaded from and uploaded to Webex; a header message is followed by the file message. | File messages keep the app's authorship. |
Frequently asked questions
- Can users in Teams view files shared from Slack?
- Yes. When a Slack user shares a file in a bridged channel, SyncRivo downloads it from Slack and uploads it to the bridged Teams conversation, so Teams users can open it without a Slack account. Depending on the Teams conversation type, the file appears as a native file card or as a header message with a link.
- Does SyncRivo store or copy file contents?
- SyncRivo does not store file contents. To relay a file, it downloads the file from the source platform and uploads it to the destination platform; the bytes pass through memory only. The copy on the destination platform is then governed by that platform's own storage and access controls.
- What file types are supported for cross-platform sharing?
- SyncRivo supports all file types that the source platform allows: documents (PDF, DOCX, XLSX), images (PNG, JPG, GIF), code snippets, archives (ZIP), and video files. The destination platform renders the file attachment using its native file preview where supported, or falls back to a link with file metadata.
- What happens to file permissions across platforms?
- Because the file is uploaded to the destination conversation, members of that bridged conversation can see it under the destination platform's permissions. Permissions set on the original file in the source platform do not carry over. Admins can switch attachment relay off per connection if files should not cross a bridge.
Related integration guides
Three-Platform Bridges
Connect three enterprise messaging platforms simultaneously with SyncRivo's cross-platform bridges.