Abstract: The secure management of attachments is described. In one example, files are identified for attachment to a message through a secure content application extension. Rather than directly attaching the files to the message, a resource locator or link to the files is generated, and the resource locator is inserted into the message. The message is then forwarded for distribution to client devices based on an addressee list for the message. The distribution of and access to the files is managed separately by a management service. The management service can notify the client devices to retrieve the files based on a file access schedule. At each of the client devices, users can access the files through a secure content file application extension using the resource locator during the file access schedule. Thus, the files are distributed through secure content file applications and not as direct attachments to messages.

Abstract: The secure management of attachments is described. In one example, files are identified for attachment to a message through a secure content application extension. Rather than directly attaching the files to the message, a resource locator or link to the files is generated, and the resource locator is inserted into the message. The message is then forwarded for distribution to client devices based on an addressee list for the message. The distribution of and access to the files is managed separately by a management service. The management service can notify the client devices to retrieve the files based on a file access schedule. At each of the client devices, users can access the files through a secure content file application extension using the resource locator during the file access schedule. Thus, the files are distributed through secure content file applications and not as direct attachments to messages.

Abstract: The secure management of attachments is described. In one example, a message is received by a device management computing environment from a client computing device. The message can include an addressee list, a resource locator to a file, and a schedule associated with an event, for example. The message is intended for distribution to a number of other client devices along with the file according to the addressee list. However, the file is not directly attached to the message. Instead, the distribution of and access to the file is managed separately and securely by the device management computing environment. The device management computing environment can cause the file to be accessible through the client devices using the resource locator based on the schedule associated with the event. Further, after the event, the device management computing environment can cause the file to be inaccessible and/or removed from the client devices.

Abstract: The secure management of attachments is described. In one example, a message is received by a device management computing environment from a client computing device. The message can include an addressee list, a resource locator to a file, and a schedule associated with an event, for example. The message is intended for distribution to a number of other client devices along with the file according to the addressee list. However, the file is not directly attached to the message. Instead, the distribution of and access to the file is managed separately and securely by the device management computing environment. The device management computing environment can cause the file to be accessible through the client devices using the resource locator based on the schedule associated with the event. Further, after the event, the device management computing environment can cause the file to be inaccessible and/or removed from the client devices.

Abstract: The secure management of attachments is described. In one example, files are identified for attachment to a message through a secure content application extension. Rather than directly attaching the files to the message, a resource locator or link to the files is generated, and the resource locator is inserted into the message. The message is then forwarded for distribution to client devices based on an addressee list for the message. The distribution of and access to the files is managed separately by a management service. The management service can notify the client devices to retrieve the files based on a file access schedule. At each of the client devices, users can access the files through a secure content file application extension using the resource locator during the file access schedule. Thus, the files are distributed through secure content file applications and not as direct attachments to messages.