Abstract: Techniques are described for managing, drafts of an electronic document (e.g., an electronic note, an electronic message, an electronic calendar invitation, and/or other types of electronic documents) between client devices. Such an electronic document can be composed using different clients, such that composing the document can be continued using different clients. A draft of an electronic document can be stored by clients and/or the message management service as a metadata. A message management service can be implemented as an intermediary computing system to manage a current version of a draft in local storage when a draft is composed using a client device. The message management service can manage version information of a draft that is exists, if any, on each of the client devices. The message management service can synchronize a draft of the message with client devices when a draft is composed using a client device.

Abstract: Techniques are described for managing, drafts of an electronic document (e.g., an electronic note, an electronic message, an electronic calendar invitation, and/or other types of electronic documents) between client devices. Such an electronic document can be composed using different clients, such that composing the document can be continued using different clients. A draft of an electronic document can be stored by clients and/or the message management service as a metadata. A message management service can be implemented as an intermediary computing system to manage a current version of a draft in local storage when a draft is composed using a client device. The message management service can manage version information of a draft that is exists, if any, on each of the client devices. The message management service can synchronize a draft of the message with client devices when a draft is composed using a client device.

Abstract: Techniques are described for managing drafts of an electronic document (e.g., an electronic note, an electronic message, an electronic calendar invitation, and/or other types of electronic documents) between client devices. Such an electronic document can be composed using different clients, such that composing the document can be continued using different clients. A draft of an electronic document can be stored by clients and/or the message management service as a metadata. A message management service can be implemented as an intermediary computing system to manage a current version of a draft in local storage when a draft is composed using a client device. The message management service can manage version information of a draft that is exists, if any, on each of the client devices. The message management service can synchronize a draft of the message with client devices when a draft is composed using a client device.

Abstract: Embodiments of the present invention improve the calendar invite experience by providing a unified interface for managing calendar invites, regardless of the originating calendar service/messaging provider. When a calendar invite is received, the relevant information (date, time, location, etc.) is parsed from the invite and presented to the user through a calendar invite user interface. The calendar invite user interface can include selectable icons or links allowing a user to accept/decline an invite. Invites are often sent in ICS files or as accept/decline links. Based on the user action, the appropriate message can be returned so that the calendars of the invitees and the organizer can be properly updated.

Abstract: Techniques are described for an access management system to manage access to a service (e.g., a message management service). A client can receive a message including an electronic image from a messaging service. The electronic image can include access information for obtaining access to a message management service. Input is received that indicates interaction with the electronic image in an interface. The client can send, to the access management system, the electronic image to request access to the message management service based on the access information. Authorization is received from the access management system indicating that the account can access the message management service. The client displays an interface to provide access to the message management service. The access to the message management service can be based on the authorization.

Abstract: Techniques are described for managing drafts of an electronic document (e.g., an electronic note, an electronic message, an electronic calendar invitation, and/or other types of electronic documents) between client devices. Such an electronic document can be composed using different clients, such that composing the document can be continued using different clients. A draft of an electronic document can be stored by clients and/or the message management service as a metadata. A message management service can be implemented as an intermediary computing system to manage a current version of a draft in local storage when a draft is composed using a client device. The message management service can manage version information of a draft that is exists, if any, on each of the client devices. The message management service can synchronize a draft of the message with client devices when a draft is composed using a client device.

Abstract: Techniques are described for managing drafts of an electronic document (e.g., an electronic note, an electronic message, an electronic calendar invitation, and/or other types of electronic documents) between client devices. Such an electronic document can be composed using different clients, such that composing the document can be continued using different clients. A draft of an electronic document can be stored by clients and/or the message management service as a metadata. A message management service can be implemented as an intermediary computing system to manage a current version of a draft in local storage when a draft is composed using a client device. The message management service can manage version information of a draft that is exists, if any, on each of the client devices. The message management service can synchronize a draft of the message with client devices when a draft is composed using a client device.

Abstract: Techniques are described for managing drafts of an electronic document (e.g., an electronic note, an electronic message, an electronic calendar invitation, and/or other types of electronic documents) between client devices. Such an electronic document can be composed using different clients, such that composing the document can be continued using different clients. A draft of an electronic document can be stored by clients and/or the message management service as a metadata. A message management service can be implemented as an intermediary computing system to manage a current version of a draft in local storage when a draft is composed using a client device. The message management service can manage version information of a draft that is exists, if any, on each of the client devices. The message management service can synchronize a draft of the message with client devices when a draft is composed using a client device.

Abstract: Techniques are described for an access management system to manage access to a service (e.g., a message management service). A client can receive a message including an electronic image from a messaging service. The electronic image can include access information for obtaining access to a message management service. Input is received that indicates interaction with the electronic image in an interface. The client can send, to the access management system, the electronic image to request access to the message management service based on the access information. Authorization is received from the access management system indicating that the account can access the message management service. The client displays an interface to provide access to the message management service. The access to the message management service can be based on the authorization.

Abstract: Embodiments of the present invention improve the calendar invite experience by providing a unified interface for managing calendar invites, regardless of the originating calendar service/messaging provider. When a calendar invite is received, the relevant information (date, time, location, etc.) is parsed from the invite and presented to the user through a calendar invite user interface. The calendar invite user interface can include selectable icons or links allowing a user to accept/decline an invite. Invites are often sent in ICS files or as accept/decline links. Based on the user action, the appropriate message can be returned so that the calendars of the invitees and the organizer can be properly updated.