Abstract: Aspects of the present disclosure relate to systems and methods for determining one or more relevant activities to surface for a user of one or more files hosted by a collaborative application. In one aspect, a set of collaborative activities that are applied by one or more users to one or more files hosted by the collaborative application may be captured. The set of collaborative activities may be analyzed in relation to the user of the one or more files hosted by the collaborative application. At least some activities in the set of collaborative activities may be identified as belonging to one or more relevance categories. A prioritization may be assigned to the at least some activities that belong to the one or more relevance categories.

Abstract: A computing device for organizing a collaborative workspace for a user implements providing, using a display of the computing device, an interactive user interface associated with the collaborative workspace in which the user may work on a shared task in a coordinated fashion with other users; identifying, based on one or more factors, one or more activities specific to the user from within the collaborative workspace; assigning the identified one or more activities to a catch-up list associated with the user; displaying, within the interactive user interface, the catch-up list; detecting that at least one of the one or more activities has been addressed from within the collaborative workspace or the catch-up list; and updating, based on the detection, the collaborative workspace and the catch-up list.

Abstract: Aspects of the present disclosure relate to systems and methods for determining one or more relevant activities to surface for a user of one or more files hosted by a collaborative application. In one aspect, a set of collaborative activities that are applied by one or more users to one or more files hosted by the collaborative application may be captured. The set of collaborative activities may be analyzed in relation to the user of the one or more files hosted by the collaborative application. At least some activities in the set of collaborative activities may be identified as belonging to one or more relevance categories. A prioritization may be assigned to the at least some activities that belong to the one or more relevance categories.

Abstract: Aspects of the present disclosure relate to a unified activity service. In one aspect, different files stored on different storage platforms may be rendered on different user interfaces. Multiple activities associated with each of the different files may be obtained from the activity service. In another aspect, activity metadata corresponding to the multiple activities may be stored in the activity service. Activities associated with the different files may include content changes in a file (e.g., edits and deletions), sharing a file, renaming a file, comments within a file, messaging, and conversations related to a file. The different storage platforms may be independent of the activity service.

Abstract: Systems, methods, and software are disclosed herein for indicating that a change made to content in a collaborative document is updating on a cached version displayed to a user. A cached version of a collaborative document is displayed in a user interface to an application. A source of the collaborative document external to the cached version of the collaborative document is then queried for changes that have occurred to content within the collaborative document since the cached version of the collaborative document was generated. If a change has occurred to the content within the collaborative document, an indication is displayed in the user interface that the cached version of the collaborative document is being updated based on the change.

Abstract: Aspects of the present disclosure relate to a unified activity service. In one aspect, different files stored on different storage platforms may be rendered on different user interfaces. Multiple activities associated with each of the different files may be obtained from the activity service. In another aspect, activity metadata corresponding to the multiple activities may be stored in the activity service. Activities associated with the different files may include content changes in a file (e.g., edits and deletions), sharing a file, renaming a file, comments within a file, messaging, and conversations related to a file. The different storage platforms may be independent of the activity service.

Abstract: Aspects of the present disclosure relate to an activity notification system. In one aspect, one or more entities associated with a user of a file may be identified. A priority level may be assigned to each of the one or more entities based on a type of activity of one or more activities associated with the file. The priority level may include at least a highest priority level and a lowest priority level. A notification indicating an occurrence of at least one activity from the one or more activities associated with the file may be sent to the entity of the one or more identified entities assigned the highest priority level. It may be determined which activities of one or more activities received at a notification service meet a notification value threshold. At least one notification from the activities determined to meet the notification value threshold may be generated.

Abstract: Aspects of the present disclosure relate to a unified activity service. In one aspect, different files stored on different storage platforms may be rendered on different user interfaces. Multiple activities associated with each of the different files may be obtained from the activity service. In another aspect, activity metadata corresponding to the multiple activities may be stored in the activity service. Activities associated with the different files may include content changes in a file (e.g., edits and deletions), sharing a file, renaming a file, comments within a file, messaging, and conversations related to a file. The different storage platforms may be independent of the activity service.

Abstract: Aspects of the present disclosure relate to an activity notification system. In one aspect, one or more entities associated with a user of a file may be identified. A priority level may be assigned to each of the one or more entities based on a type of activity of one or more activities associated with the file. The priority level may include at least a highest priority level and a lowest priority level. A notification indicating an occurrence of at least one activity from the one or more activities associated with the file may be sent to the entity of the one or more identified entities assigned the highest priority level. It may be determined which activities of one or more activities received at a notification service meet a notification value threshold. At least one notification from the activities determined to meet the notification value threshold may be generated.

Abstract: Aspects of the present disclosure relate to a unified activity service. In one aspect, a first file stored on a first storage platform may be rendered on a first user interface. One or more activities associated with the first file may be obtained from the activity service. A second file stored on a second storage platform may be rendered on a second user interface. One or more activities associated with the second file may be obtained from the activity service. In another aspect, activity metadata corresponding to at least one activity associated with a first file stored on a first storage platform and activity metadata corresponding to at least one activity associated with a second file stored on a second storage platform may be received at and stored in the activity service.