Synchronization of notification actions across multiple enrolled devices

1. A system for managing notifications for a plurality of client devices from a management server, the client devices including first and second client devices of a user and the management server comprising:

a computing device comprising a processor and a memory; and

program instructions stored in the memory that, when executed by the processor, cause the computing device to carry out a method including the steps of:

receiving from the first client device metadata associated with a notification posted on the first client device, wherein the first client device has a client application installed therein to communicate with an application server and a management agent installed therein to communicate with the management server, and the notification is issued by the application server and communicated to the first client device via the client application;

receiving from the first client device an indication of an action performed with respect to the notification;

determining whether to propagate a new notification state to the second client device based at least in part on a type of the action and a current notification state associated with the second client device; and

providing to the second client device a command to change the current notification state to the new notification state.

2. The system of claim 1 , wherein determining whether to propagate the new notification state is further based at least in part on an activity status of the second client device.

3. The system of claim 1 , wherein the program instructions that cause the computing device to provide to the second client device the command to change the current notification state to the new notification state further cause the computing device to place the command in a command queue associated with the second client device.

4. The system of claim 1 , wherein the first client device and the second client device are associated with a user account and enrolled with the management service.

5. The system of claim 1 , wherein the metadata associated with the notification comprises at least one of a notification identifier, a notification type, notification content, and an action performable with respect to the notification.

6. The system of claim 1 , wherein the action comprises at least one of a dismissal action, a reply action, and a snooze action.

7. The system of claim 1 , wherein the new notification state comprises at least one of a dismissal of the notification and a snoozing of the notification.

8. A method of managing notifications for a plurality of client devices from a management server, the client devices including first and second client devices of a user, comprising:

receiving, by the management server, from the first client device metadata associated with a notification posted on the first client device, wherein the first client device has a client application installed therein to communicate with an application server and a management agent installed therein to communicate with the management server, and the notification is issued by the application server and communicated to the first client device via the client application;

receiving, by the management server, from the first client device an indication of an action performed with respect to the notification;

determining, by the management server, whether to propagate a new notification state to the second client device based at least in part on a type of the action and a current notification state associated with the second client device; and

providing, by the management server, to the second client device a command to change the current notification state to the new notification state.

9. The method of claim 8 , wherein determining whether to propagate the new notification state is further based at least in part on an activity status of the second client device.

10. The method of claim 8 , wherein providing to the second client device the command to change the current notification state to the new notification state further comprises placing the command in a command queue associated with the second client device.

11. The method of claim 8 , wherein the first client device and the second client device are associated with a user account and enrolled with the management service.

12. The method of claim 8 , wherein the metadata associated with the notification comprises at least one of a notification identifier, a notification type, notification content, and an action performable with respect to the notification.

13. The method of claim 8 , wherein the action comprises at least one of a dismissal action, a reply action, and a snooze action.

14. The method of claim 8 , wherein the new notification state comprises at least one of a dismissal of the notification and a snoozing of the notification.

15. A non-transitory computer-readable medium comprising machine-readable instructions, wherein when executed by a processor of at least one computing device of a management server from which notifications are managed for first and second client devices of a user, the machine-readable instructions cause the at least one computing device to carry out a method including the steps of:

receive-receiving from the first client device metadata associated with a notification posted on the first client device, wherein the first client device has a client application installed therein to communicate with an application server and a management agent installed therein to communicate with the management server, and the notification is issued by the application server and communicated to the first client device via the client application;

receiving from the first client device an indication of an action performed with respect to the notification;

determining whether to propagate a new notification state to the second client device based at least in part on a type of the action and a current notification state associated with the second client device; and

providing to the second client device a command to change the current notification state to the new notification state.

16. The non-transitory computer-readable medium of claim 15 , wherein determining whether to propagate the new notification state is further based at least in part on an activity status of the second client device.

17. The non-transitory computer-readable medium of claim 15 , wherein the machine-readable instructions that cause the at least one computing device to provide to the second client device the command to change the current notification state to the new notification state further cause the computing device to place the command in a command queue associated with the second client device.

18. The non-transitory computer-readable medium of claim 15 , wherein the first client device and the second client device are associated with a user account and enrolled with the management service.

19. The non-transitory computer-readable medium of claim 15 , wherein the metadata associated with the notification comprises at least one of a notification identifier, a notification type, notification content, and an action performable with respect to the notification.

20. The non-transitory computer-readable medium of claim 15 , wherein:

the action comprises at least one of a dismissal action, a reply action, and a snooze action; and

the new notification state comprises at least one of a dismissal of the notification and a snoozing of the notification.