Learn how Mio's File Sync feature enables secure cross-platform sharing of collaborative files, handles SSO, and streams direct file copies like GIFs and screenshots.
Hi everyone, welcome to Mio Academy. I'm Jacob, and in this module, we will be exploring Mio's File Sync feature. This lesson will focus on how cross-platform users can share collaborative files, such as those on Google Drive, SharePoint, and OneDrive using Mio's File Sync.
File sharing and collaboration are crucial for any organization, and Mio's File Sync ensures that users across different platforms can seamlessly share and access cloud-based files.
Mio utilizes two types of flows to facilitate secure and efficient file sharing. These are Service Provider-led SSO and Identity Provider-led SSO.
Now let’s dive into some commonly asked questions about File Sync.
Mio uses secure authentication methods, such as SAML-based SSO, to ensure that files are accessed only by authorized users. All data is encrypted during transmission to maintain confidentiality.
Yes, Mio supports file sharing from various cloud storage services, as long as they support secure authentication methods. This flexibility ensures that your team can collaborate effectively, regardless of their preferred storage platform.
Mio respects the file permissions set by the original platform. This means that if a file is shared with view-only permissions on Google Drive, those permissions will be maintained when accessed through Teams, and vice versa.
Thank you for watching this lesson on Mio's File Sync feature. If you have any further questions, please visit our help center at help.m.io.
Stay tuned for more lessons here at Mio Academy, where we help you become an expert on all things Mio. See you next time!
Hi everyone, welcome to Mio Academy. I'm Jacob, and in this module, we will be exploring Mio's File Sync feature.
Mio uses two types of flows to enable secure and efficient file sharing: Service Provider-led SSO and Identity Provider-led SSO.
In this video, we’ll dive into the mechanics of Service Provider-led SSO and take a look at this flow from the end user perspective. .
Greg shares a Google Drive link in Google Chat. Tessa receives the link in Microsoft Teams.
When Tessa clicks on the link, she is taken to a Google sign-in interface. She uses her Microsoft Teams username, and is redirected to a Microsoft Teams sign-in page. Entering her Teams password, Tessa is then granted access to the Google Drive file.
As a reminder, the Google Interop account that Mio has created for Tessa uses the same email address as Tessa’s Microsoft login. This email has been added to a group inside of the Google Admin Console, which is redirected to Microsoft SSO for authentication.
Tessa shares a SharePoint file in Microsoft Teams. Greg receives the link in Google Chat.
When Greg clicks on the link, he is taken to a Microsoft sign-in interface. He enters his Google username, and is redirected to a Google sign-in page. He types his Google password and is granted access the SharePoint file.
This works because Greg’s Microsoft Guest Account, created by Mio, uses the same email address as Greg’s Google login. Additionally, this email address has been added to a security group within Microsoft Entra ID, which redirects the user to Google SSO for authentication.
Thank you for watching this lesson on File Sync with the Service Provider-led SSO flow.
If you have any further questions, please visit our help center at help.m.io.
Stay tuned for more lessons here at Mio Academy, where we help you become an expert on all things Mio. See you next time!
Hi everyone, welcome back to Mio Academy. I'm Jacob, and in this lesson, we'll discuss how Mio shares copies of files, such as GIFs, screenshots, and other attachments that users upload directly.
File sharing goes beyond just collaborative links, such as those on Google Drive or SharePoint.
Users often need to share direct copies of files like images, GIFs, and other attachments. Mio ensures that these files are handled efficiently and securely across platforms by streaming the copy of the file to the other platform.
When a user uploads a file in a chat, Mio ensures it can be accessed across different platforms without any loss of quality or functionality by streaming the file directly to the other platform.
Mio uses a combination of OAuth technology and HTML streaming to send cross-platform files. Mio recalls the message metadata to stream the file via HTML, where the recipient must then perform an authorization to verify that they are an intended recipient.
Let’s take a look at the end user perspective.
Greg Taylor, a Google user, sends a GIF in Google Chat. It is received natively by Tessa Park, a Microsoft Teams user.
Tessa then sends a screenshot in Microsoft Teams, and it is received natively by Greg on Google Chat.
Mio ensures that all files, whether they are GIFs, screenshots, or other attachments, are transmitted securely between platforms. This includes maintaining the integrity of the files so that there is no loss in quality during the transfer.
Mio does not persistently store user messages or files. Message metadata is retained by Mio for future reconciliation across platforms. However the underlying messages and files are not permanently retained. This means that files are only accessible by the intended recipients and are not stored on Mio's servers.
Mio provides a proxy service for all files uploaded. When a file is either uploaded or requested by a connected platform or user, Mio will connect and authenticate to the source platform and request the file. As the file is streamed, an outbound connection is made to the target platform or authenticated user, and the file is proxied to the recipient.
Occasionally, a real time stream between the platforms is not possible. In this scenario, the file is requested and temporarily cached on the Mio server before the outbound connection is made. This two-part transmission is still achieved through a single transaction, ensuring that the file is not retained by Mio outside the transfer session.
The main limitation that users should be aware of is that Mio will always stream an uploaded file as a link when it is sent from a Google primary user to a Microsoft primary user in a direct message or group chat. This is due to the Microsoft platform limitation that Microsoft guest accounts, which represent Google primary users in this scenario, are not able to send files in direct messages or group chats. However, all Google Drive or SharePoint links can still be shared and delivered regardless of the originating platform.
Mio adheres to strict data privacy and security standards. All file transfers are encrypted, and Mio does not have access to the content of the files.
If for some reason you are unable to configure your environments to take advantage of these solutions, there are the existing options offered by Microsoft and Google, such as visitor sharing and external sharing. You can learn more in the help articles linked.
Thank you for watching this lesson on how Mio handles copies of files.
If you have any further questions, please visit our help center at help.m.io.
Stay tuned for more lessons here at Mio Academy, where we help you become an expert on all things Mio. See you next time!
Hi everyone, welcome back to Mio Academy. I'm Jacob, and in this lesson, we'll discuss how Mio shares copies of files, such as GIFs, screenshots, and other attachments that users upload directly.
File sharing goes beyond just collaborative links, such as those on Google Drive or SharePoint.
Users often need to share direct copies of files like images, GIFs, and other attachments. Mio ensures that these files are handled efficiently and securely across platforms by streaming the copy of the file to the other platform.
When a user uploads a file in a chat, Mio ensures it can be accessed across different platforms without any loss of quality or functionality by streaming the file directly to the other platform.
Mio uses a combination of OAuth technology and HTML streaming to send cross-platform files. Mio recalls the message metadata to stream the file via HTML, where the recipient must then perform an authorization to verify that they are an intended recipient.
Let’s take a look at the end user perspective.
Greg Taylor, a Google user, sends a GIF in Google Chat. It is received natively by Tessa Park, a Microsoft Teams user.
Tessa then sends a screenshot in Microsoft Teams, and it is received natively by Greg on Google Chat.
Mio ensures that all files, whether they are GIFs, screenshots, or other attachments, are transmitted securely between platforms. This includes maintaining the integrity of the files so that there is no loss in quality during the transfer.
Mio does not persistently store user messages or files. Message metadata is retained by Mio for future reconciliation across platforms. However the underlying messages and files are not permanently retained. This means that files are only accessible by the intended recipients and are not stored on Mio's servers.
Mio provides a proxy service for all files uploaded. When a file is either uploaded or requested by a connected platform or user, Mio will connect and authenticate to the source platform and request the file. As the file is streamed, an outbound connection is made to the target platform or authenticated user, and the file is proxied to the recipient.
Occasionally, a real time stream between the platforms is not possible. In this scenario, the file is requested and temporarily cached on the Mio server before the outbound connection is made. This two-part transmission is still achieved through a single transaction, ensuring that the file is not retained by Mio outside the transfer session.
The main limitation that users should be aware of is that Mio will always stream an uploaded file as a link when it is sent from a Google primary user to a Microsoft primary user in a direct message or group chat. This is due to the Microsoft platform limitation that Microsoft guest accounts, which represent Google primary users in this scenario, are not able to send files in direct messages or group chats. However, all Google Drive or SharePoint links can still be shared and delivered regardless of the originating platform.
Mio adheres to strict data privacy and security standards. All file transfers are encrypted, and Mio does not have access to the content of the files.
If for some reason you are unable to configure your environments to take advantage of these solutions, there are the existing options offered by Microsoft and Google, such as visitor sharing and external sharing. You can learn more in the help articles linked.
Thank you for watching this lesson on how Mio handles copies of files.
If you have any further questions, please visit our help center at help.m.io.
Stay tuned for more lessons here at Mio Academy, where we help you become an expert on all things Mio. See you next time!
.svg){kind=icon}
