Managing message attachments
Disclosed are systems, methods, and non-transitory computer-readable storage media for managing email attachments in an online content management system. In some implementations, a messaging client can receive input attaching a content item to an electronic message in a message thread. In response to the input, the messaging client can store the content item in a file system managed by an online content management system, generate a link to the content item, and insert the link in the electronic message. The content item can be shared with the recipients of the electronic message such that the content item can be synchronized across recipient devices by the online content management system. The messaging client on each recipient device and/or the sender's device can present representations of the attachments associated with the message thread in a centralized location on a GUI of the messaging client.
1. A method, comprising:
identifying, by a computing system, a first message generated at the computing system, wherein the first message comprises an attachment and the first message is to be transmitted from the computing system to a second computing system;
responsive to identifying the first message, generating, by the computing system, a thread identifier corresponding to the first message, wherein the thread identifier identifies a thread of related messages, the thread of related messages comprising at least the first message and a second message;
responsive to generating the thread identifier, generating, by the computing system, a shared folder dedicated to the thread identifier, the shared folder accessible to the computing system and the second computing system and configured to store attachments associated with the thread of related messages;
determining, by the computing system, that the computing system or the second computing system forwarded the first message or the second message to a third computing system; and
based on the determining,
causing, by the computing system, a content management system to add the third computing system as an authorized device to the shared folder, and
causing, by the computing system, the shared folder to be synchronized with a managed file system of the third computing system.
2. The method of claim 1 , further comprising:
determining, by the computing system, that the first message is related to the second message.
3. The method of claim 1 , further comprising:
receiving, by the computing system, a further message sent from the computing system to the second computing system;
identifying, by the computing system, that the further message includes a second attachment; and
based on the identifying, saving, by the computing system, the second attachment in the shared folder.
4. The method of claim 3 , wherein saving, by the computing system, the second attachment in the shared folder comprises:
determining a context of the second attachment based on content contained therein; and
based on the context, determining that the shared folder is relevant to the second attachment.
5. The method of claim 3 , wherein saving, by the computing system, the second attachment in the shared folder comprises:
determining that specified recipients in the further message comprises all users in a group of users associated with the shared folder.
6. The method of claim 3 , further comprising:
responsive to the saving, synchronizing, by the computing system, the shared folder with managed file systems of the computing system and the second computing system.
7. The method of claim 1 , further comprising:
receiving, by the computing system, a request to add a fourth computing system as an authorized device to the shared folder; and
responsive to the request, causing, by the computing system, the content management system to:
add the fourth computing system as an authorized device to the shared folder, and
causing the shared folder to be synchronized with a further managed file system of the fourth computing system.
8. The method of claim 1 , wherein generating, by the computing system, the shared folder dedicated to the thread identifier comprises:
invoking an application programming interface (API) of the content management system to cause the content management system to generate the shared folder for the thread identifier.
9. The method of claim 8 , wherein causing, by the computing system, the content management system to add the third computing system as an authorized device to the shared folder comprises:
invoking the API of the content management system to cause the content management system to add the third computing system as an authorized device to the shared folder.
10. A non-transitory computer readable medium comprising one or more sequences of instructions, which, when executed by one or more processors, causes a computing system to perform operations comprising:
identifying, by the computing system, a first message generated at the computing system, wherein the first message comprises an attachment and the first message is to be transmitted from the computing system to a second computing system;
responsive to identifying the first message, generating, by the computing system, a thread identifier corresponding to the first message, wherein the thread identifier identifies a thread of related messages, the thread of related messages comprising at least the first message and a second message;
responsive to generating the thread identifier, generating, by the computing system, a shared folder dedicated to the thread identifier, the shared folder accessible to the computing system and the second computing system and configured to store attachments associated with the thread of related messages;
determining, by the computing system, that a third computing system user has interacted with the first message or the second message; and
based on the determining,
causing, by the computing system, a content management system to add the third computing system as an authorized device to the shared folder, and
causing, by the computing system, the shared folder to be synchronized with a managed file system of the third computing system.
11. The non-transitory computer readable medium of claim 10 , further comprising:
determining, by the computing system, that the first message is related to the second message.
12. The non-transitory computer readable medium of claim 10 , further comprising:
receiving, by the computing system, a further message sent from the computing system to the second computing system;
identifying, by the computing system, that the further message includes a second attachment; and
based on the identifying, saving, by the computing system, the second attachment in the shared folder.
13. The non-transitory computer readable medium of claim 12 , wherein saving, by the computing system, the second attachment in the shared folder comprises:
determining a context of the second attachment based on content contained therein; and
based on the context, determining that the shared folder is relevant to the second attachment.
14. The non-transitory computer readable medium of claim 12 , wherein saving, by the computing system, the second attachment in the shared folder comprises:
determining that specified recipients in the further message comprises all users in a group of users associated with the shared folder.
15. The non-transitory computer readable medium of claim 12 , further comprising:
responsive to the saving, synchronizing, by the computing system, the shared folder with managed file systems of the computing system and the second computing system.
16. The non-transitory computer readable medium of claim 10 , further comprising:
receiving, by the computing system, a request to add a fourth computing system as an authorized device to the shared folder; and
responsive to the request, causing, by the computing system, the content management system to:
add the fourth computing system as an authorized device to the shared folder, and
causing the shared folder to be synchronized with a further managed file system of the fourth computing system.
17. The non-transitory computer readable medium of claim 10 , wherein generating, by the computing system, the shared folder dedicated to the thread identifier comprises:
invoking an application programming interface (API) of the content management system to cause the content management system to generate the shared folder for the thread identifier.
18. The non-transitory computer readable medium of claim 17 , wherein causing, by the computing system, the content management system to add the third computing system as an authorized device to the shared folder comprises:
invoking the API of the content management system to cause the content management system to add the third computing system as an authorized device to the shared folder.
19. A system, comprising:
one or more processors; and
a memory having programming instructions stored thereon, which, when executed by the one or more processors, causes the system to perform operations comprising:
identifying a first message generated at the system, wherein the first message is to be transmitted from the system to a second computing system;
responsive to identifying the first message, generating a thread identifier corresponding to the first message, wherein the thread identifier identifies a thread of related messages, the thread of related messages comprising at least the first message and a second message;
responsive to generating the thread identifier, generating a shared folder dedicated to the thread identifier, the shared folder accessible to the system and the second computing system and configured to store attachments associated with the thread of related messages;
determining that the system or the second computing system forwarded the first message or the second message to a third computing system; and
based on the determining,
causing a content management system to add the third computing as an authorized device to the shared folder, and
causing the shared folder to be synchronized with a managed file system of the third computing system.