Patent Description:
It is with respect to these and other considerations that the following disclosure is made.

<CIT> discloses a technique for facilitating online collaboration among users of client machines allows multiple users to work together and concurrently on a set of documents. In response to a request from a user, a server opens a document in a software application running on the server and virtualizes the software application to the client machines. Multiple users can then operate the software application from the respective client machines to edit the document via remote control. The server multiplexes pointer input from the client machines to provide pointer input to the software application from one user at a time. Multiplexing of pointer input takes place seamlessly and automatically in response to user activity with respect to the virtualized software application.

<CIT> discloses a device including plug-in software components that are integrated with document processing software suites. The plug-in software components provide a set of integrated interfaces for collaborative document processing in conjunction with multiple remote file, data, and application service providers. The set of interfaces enable coauthoring a document, document merging, discovering and displaying context-sensitive metadata on a software dashboard based on permissions associated with the metadata and/or a client computing device, caching, symmetric distributed document merge with the multiple service providers, and integrated search and insertion of multimedia data in documents, among others. The documents include formatted text documents, spreadsheet documents, and slide presentation documents.

The invention is defined by a computer-implemented method for managing operation of a collaboration platform according to claim <NUM> and a system according to claim <NUM>.

The techniques disclosed herein enable a system to update user-specific instances of an application for individual users of a group in response to a data file for the application being associated with a collaboration object that corresponds to the entire group within a different application. Generally described, the user-specific instances of the application present each individual user with their own custom user experience that provides access to specific data files based on object permissions for the application. In some examples, the application may be a notetaking application through which an individual user can access and edit files that the object permissions indicate that she is permitted to access. The files may include content that the individual user has created herself and retains exclusive access to and/or content that has been created by another user and shared with the individual user via the collaboration object. An application extension may be executable by the different application (e.g., a web-conferencing application) to extend content editing functionalities of the application into the collaboration object. For example, the application extension may enable a web-conferencing application to implement content editing functions of a stand-alone notetaking application within a virtual meeting (e.g., an exemplary form of collaboration object). In response to a data file of the application being accessed in association with the collaboration object through the application extension, each of the user-specific instances of the application may be automatically updated to provide direct access to the data file. In this way, each of the users within the user group associated with the collaboration object is enabled to access the data file via both of the collaboration object (that is accessible by the entire user group) and their own user-specific instance of the application.

The collaboration object is a communication session (e.g., a virtual meeting or web-based conference), for example that is facilitated between the entire group of users by a web-based collaboration platform that transmits bi-directional user streams between a plurality of client devices. For example, individual ones of the client devices may continuously capture audio and video "AV" data (e.g., of a user) via various input devices such as cameras and microphones. The captured A/V data may be continuously streamed to a server device(s). Upon receiving the AV data streams, the server device(s) transmit to each individual client device the streams of A/V data that is received from each other client device. Thus, each individual client device is enabled to render live audio and/or video of the participants who are utilizing the other client devices. In this example, the web-based collaboration platform may execute an application extension of the application in association with the communication session. In this way, functionalities that are provided within each user-specific instance of the application may be extended into the communication session. Exemplary applications which may be extended into a communication session include, but are not limited to, the notetaking application described above, a form generation application, a whiteboard application, and so on. For purposes of the present example, presume that the web-based collaboration platform exposes content editing functionalities of the notetaking application into the communication session via the application extension for the notetaking application. Then, in response to a data file being generated or modified during the virtual meeting via the application extension of the notetaking application, user-specific instances of the notetaking application that correspond to the group of users attending the virtual meeting may be automatically updated to provide each individual user of the group with access to the data file by way of their own user-specific instance of the notetaking application.

In an exemplary implementation, a system determines a group definition that associates multiple user accounts with a collaboration object corresponding to a first application. Collaboration objects are communication sessions, examples of which include, but are not limited to, virtual meetings, web-based calls, channels, chats, and email threads, and/or various other communication modalities that support collaborative editing of a data object. The group definition may correspond to an invitee list for a communication session, participants of a communication session and/or web-based call, members of a channel or chat, senders and/or recipients of an email thread, and so on. Accordingly, in various embodiments, the first application may be a web-conferencing application that is implemented by a web-based collaboration platform that facilitates the collaboration object. For example, a web-based collaboration platform may facilitate a virtual meeting or call by transmitting bi-directional user streams between a plurality of client devices.

The system receives an instruction to associate a data file corresponding to a second application with the collaboration object corresponding to the first application. The instruction corresponds to a user generating a new data file, e.g. that corresponds to a notetaking application, during a communication session that is being facilitated by the web-conferencing application via an application extension for the notetaking application. As described in detail below, the application extension may extend content editing functionalities of the second application into the collaboration object corresponding to the first application. In this way, one or more of the multiple user accounts associated with the collaboration object by the group definition are provided with the content editing functionalities of the second application directly through the collaboration object being facilitated by the first application. For example, under circumstances where the collaboration object is a virtual meeting being facilitated by a web-conferencing application and the application extension corresponds to the notetaking application, notetaking functionalities provided by the notetaking application are exposed with respect to data file directly within the virtual meeting.

Responsive to the instruction to associate the data file corresponding to the second application with the collaboration object corresponding to the first application, the system may automatically (e.g., without manual user input) configure object permissions data to grant the multiple user accounts (defined by the group definition of the collaboration object) with access to the data file. Additionally, the system may also update application configuration parameters for the second application in association with each of the multiple user accounts. Generally described, the application configuration parameters may control aspects of a user experience presented by the user-specific instances of the second application. For example, the application configuration parameters may dictate a listing of data files that are presented by each of the user-specific instances of the second application that uniquely correspond to the individual users defined by the group definition.

The application configuration parameters that are updated based on the object permissions data may be transmitted to user-specific instances of the second application for each of the multiple user accounts defined by the group definition for the collaboration object. Upon receipt, the application configuration parameters cause each user-specific instance of the second application to render a user interface element that is configured to provision access to the content of the data file that has been associated with the collaboration object based on the instruction received via the first application. Thus, the techniques described herein enable each of the users within the user group for the collaboration object to access the data file via both of the collaboration object (that is accessible by the entire user group) and their own user-specific instance of the application. In this way, users are seamlessly enabled to access content that was edited via the application extension being executed by the first application in association with the collaboration object directly via their own user-specific stand-alone instance of the second application.

Features and technical benefits other than those explicitly described above will be apparent from a reading of the following Detailed Description and a review of the associated drawings. This Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. The term "techniques," for instance, may refer to system(s), method(s), computer-readable instructions, module(s), algorithms, hardware logic, and/or operation(s) as permitted by the context described above and throughout the document.

The following Detailed Description discloses techniques for updating user-specific instances of an application that correspond to individual users of a group based on a data file for the application becoming accessible via a collaboration object that corresponds to the entire group within a different application. The user-specific instances of the application present each individual user with their own custom user experience that is configured to provide access to specific content based on object permissions for the application. As a specific example, the application may be a notetaking application (e.g., MICROSOFT ONENOTE, MICROSOFT WHITEBOARD) through which an individual user can view and/or edit files that the object permissions indicate she is permitted to access. An application extension may be executable, by the different application, in association with the collaboration object to extend content editing functionalities of the application into the collaboration object. Responsive to specific content being associated with the collaboration object via the application extension, each of the user-specific instances of the application may be automatically updated to provide direct access to the specific content. In this way, each of the users within the user group associated with the collaboration object is enabled to access the data file via both of the collaboration object (that is accessible by the entire user group) and their own user-specific instance of the application. The techniques disclosed herein are applicable to a variety of systems and approaches involving synchronizing content access permissions and presentation of specific pieces of content across disparate applications. Aspects of the disclosed techniques are described in the specific context of automatically configuring a user group's user-specific instances of a second application to include a pointer to a data file as a response to that data file being associated with a collaboration object that is accessible to the user group via a first application. The collaboration object is communication session (e.g., a prescheduled virtual meeting, an impromptu virtual call, etc.) and some aspects are described in relation to a specific example of content of the data file being collaboratively edited during the communication session by way of an application extension, of a notetaking application, that is executed by a web-conferencing application that is facilitating the communication session. While the presently disclosed techniques are not necessarily limited to these specific contexts or examples (unless claimed with such limiting recitations), an appreciation of various aspects of the disclosed techniques is readily gained through a discussion of these specific contents and examples. However, other arrangements such as a group of users' user-specific instances of a word processing application being updated to provide direct access to a word processing file in response to that word processing file being shared with the group of users via a chat, channel, and/or email thread shall be considered variations of the described and claimed techniques (unless clearly claimed to exclude such variations).

Various examples, scenarios, and aspects of the disclosed techniques are described below with reference to <FIG>.

<FIG> is a system diagram illustrating an example environment <NUM> in which a data file <NUM> being accessed in association with a collaboration object <NUM> of a first application <NUM>(<NUM>) causes user-specific instances <NUM> of a second application <NUM>(<NUM>) for a group of users associated with the collaboration object <NUM> to include a file pointer <NUM> to the data file <NUM>. As illustrated, the example environment <NUM> includes a collaboration platform <NUM> that is in communication with a plurality of user devices <NUM>. The collaboration platform <NUM> may include one or more servers that implement aspects of the first application <NUM>(<NUM>) and the second application <NUM>(<NUM>) in association with multiple user accounts. For purposes of the present discussion, presume that the collaboration platform <NUM> implements aspects of each of the first application <NUM>(<NUM>) and the second application <NUM>(<NUM>) in association with a first user account through an Nth user account. Further presume that the first user account corresponds to a first user device <NUM>(<NUM>), the second user account corresponds to a second user device <NUM>(<NUM>), and so on. For example, the first user device <NUM>(<NUM>) may be operating based on login credentials for the first user account, the second user device <NUM>(<NUM>) may be operating based on login credentials for the second user account, and so on.

As illustrated, each of the user devices <NUM> support corresponding first application instances <NUM> and second application instances <NUM>, each of which are user-specific in the sense that the instances <NUM> and <NUM> operate in accordance with whichever user account is actively logged into the respective user device <NUM>. Thus, the first user device <NUM>(<NUM>) is supporting a first instance <NUM>(<NUM>) of the first application <NUM>(<NUM>) that corresponds to login credentials for the first user account, the second user device <NUM>(<NUM>) is supporting a second instance <NUM>(<NUM>) of the first application <NUM>(<NUM>) that corresponds to login credentials for the second user account, and so on. Furthermore, the first user device <NUM>(<NUM>) is supporting a first instance <NUM>(<NUM>) of the second application <NUM>(<NUM>) that corresponds to login credentials for the first user account, the second user device <NUM>(<NUM>) is supporting a second instance <NUM>(<NUM>) of the second application <NUM>(<NUM>) that corresponds to login credentials for the second user account, and so on. The user-specific instances <NUM> of the second application <NUM>(<NUM>) present a custom user experience that uniquely corresponds to the user account that is logged into that user-specific instance <NUM>. In some embodiments, each custom user experience is configured to provide direct and seamless access to specific data files based on object permissions associated with the second application <NUM>(<NUM>). For example, the first instance <NUM>(<NUM>) (of the second application <NUM>(<NUM>)) that is operating on the first user device <NUM>(<NUM>) may present a listing of data files that user account data <NUM> indicates the first user account is permitted to access.

In the example environment <NUM>, the collaboration platform <NUM> executes the first application <NUM>(<NUM>) to implement first functionalities <NUM>(<NUM>) in association with a collaboration object <NUM>. The collaboration object <NUM> is a communication session (e.g., a virtual meeting or web-based conference) that corresponds to a group definition <NUM>. The group definition <NUM> may define a plurality of user accounts in association with the collaboration object <NUM>. For example, the group definition <NUM> may correspond to a group of users that are invited to a pre-scheduled virtual meeting, a group of users that attend an impromptu virtual call, a group of users that have accepted an invitation to a pre-scheduled virtual meeting, a group of users that belong to a channel or chat, etc. For exemplary purposes, presume that the group definition <NUM> excludes the third user account and includes each of the first user account, the second user account, and the Nth user account. The collaboration platform <NUM> may maintain or otherwise have access to directory data <NUM> that defines attributes (e.g., usernames, passwords, departments, job titles, etc.) for the first through Nth user account.

As illustrated, the collaboration platform <NUM> receives an instruction <NUM> to associate a data file <NUM> with the collaboration object <NUM>. The data file <NUM> may correspond to the second application <NUM>(<NUM>). For example, the data file <NUM> may be a note page that viewable and editable via second functionalities <NUM>(<NUM>) that are provided by the second application <NUM>(<NUM>). In some embodiments, the instruction <NUM> causes the first application <NUM>(<NUM>) to expose the second functionalities <NUM>(<NUM>) with respect to content of the data file <NUM> by executing an application extension <NUM> of the second application <NUM>(<NUM>) in association with the collaboration object <NUM>. In this way, the application extension <NUM> enables the group of users associated with the collaboration object <NUM> to implement the second functionalities <NUM>(<NUM>) of the second application <NUM>(<NUM>) while collaboratively viewing the content of the data file <NUM> within the context of the collaboration object <NUM>.

To illustrate this point, suppose that the collaboration object <NUM> is a virtual meeting that is being facilitated between the first user account, the second user account, and the Nth user account. In this context, the collaboration platform <NUM> may receive user streams from each of the first user device <NUM>(<NUM>), the second user device <NUM>(<NUM>), and the Nth user device <NUM>(N). Thus, each of these user devices <NUM> may continuously capture audio and video "AV" data (e.g., of a user) via various input devices such as cameras and microphones. Each of these user devices <NUM> may also continuously stream the captured A/V data to the collaboration platform <NUM>. Upon receiving the AV data streams, the collaboration platform <NUM> transmits to each individual user device the streams of A/V data that is received from each other user device. Thus, each individual user device is enabled to render live audio and/or video of the participants who are utilizing the other user devices.

In some embodiments, the instruction <NUM> may be generated based on a user input that selects an icon that corresponds to the second application <NUM>(<NUM>) that is exposed by the user-specific instances <NUM> of the first application <NUM>(<NUM>). The instruction <NUM> may cause the first application <NUM>(<NUM>) to execute the application extension <NUM> within the context of the collaboration object <NUM>. For example, in the context of the collaboration object <NUM> being a virtual meeting and the second application <NUM>(<NUM>) being a notetaking application, the execution of the application extension <NUM> by the first application <NUM>(<NUM>) may expose notetaking functionalities of the notetaking application directly within the virtual meeting. In this way, each of the users that are participating in the virtual meeting are enabled to collaboratively edit content of the data file <NUM> within the context of the virtual meeting using notetaking functionalities that are extended into the virtual meeting via the application extension <NUM>. The file pointer <NUM> that is illustrated within the collaboration object <NUM> may point to the data file <NUM> (e.g., identify a unique path to the data file <NUM> in a file system maintained by the collaboration platform <NUM>). Generally described, the file system is configured to facilitate and/or perform operations in association with stored files (e.g., open a file, delete a file, write to a file, read from a file, replace a file, copy a file, move a file, search for a file, create a file, etc.). There are a variety of different file systems, some of which can be designed to be used for specific applications or specific operating systems executing on a host system. A file system is typically configured as a hierarchical structure that includes nodes representing directories and/or files. Moreover, a file system comprises logic that enables navigation through the nodes to locate a file (e.g., a document, an executable, a spreadsheet, an image, a video, etc.) and to perform an operation in association with the file. In some instances, a file system may maintain object permissions data <NUM> as described below.

Based on the instruction <NUM>, the first application <NUM>(<NUM>) may generate update data <NUM> that is configured to update the user account data <NUM> to indicate that each user defined by the group definition <NUM> for the collaboration object <NUM> is permitted to access the data file <NUM>. For illustrative purposes, object permissions data <NUM> that corresponds to the data file <NUM> is shown with check-marks indicating that account permissions for each of the first user account, the second user account, and the Nth user account permit access to the data file <NUM>. For purposes of the present discussion, presume that at least some of these user accounts were not permitted to access the data file <NUM> prior to the instruction <NUM> being generated to associate the data file <NUM> with the collaboration object <NUM>.

The collaboration platform <NUM> may then provide aspects of the update data <NUM> to the second application <NUM>(<NUM>) which may update application configuration parameters <NUM> to reflect the object permissions data <NUM> as updated based on the instruction <NUM>. The application configuration parameters <NUM> may control aspects of a user experience presented by the user-specific instances <NUM> of the second application <NUM>(<NUM>) at each of the user devices <NUM>. For example, the application configuration parameters <NUM> for each user account may dictate a listing of data files that are presented by each of the user-specific instances <NUM> of the second application <NUM>(<NUM>).

As illustrated, the collaboration platform <NUM> transmits instances of the application configuration parameters to each instance <NUM> of the second application <NUM>(<NUM>) that corresponds to the users identified in the group definition <NUM> for the collaboration object <NUM>. It will be appreciated that the transmitted instances of the application configuration parameters may be transmitted as a result of the instruction <NUM> causing the object permission data <NUM> to be updated to indicate that user accounts defined by the group definition <NUM> are permitted to access the data file <NUM>. Here, first application configuration parameters <NUM>(<NUM>) are sent to the first user device <NUM>(<NUM>), second application configuration parameters <NUM>(<NUM>) are sent to the second user device <NUM>(<NUM>), and Nth application configuration parameters <NUM>(N) are sent to the first user device <NUM>(N). Notably, due to the third user account being omitted from the group definition, application configuration parameters are not generated for and transmitted to the third user device <NUM>(<NUM>). In some embodiments, the application configuration parameters <NUM> transmitted to each user device <NUM> associated with the group definition <NUM> cause the respective instances <NUM> of the second application <NUM>(<NUM>) to include the file pointer <NUM> that points to the data file <NUM>. In this way, the transmitted instances of the application configuration parameters may cause each user-specific instance <NUM> of the second application <NUM>(<NUM>) to render a user interface element that is configured to provision access to the content of the data file <NUM> that has been associated with the collaboration object <NUM> based on the instruction <NUM> received via the first application <NUM>(<NUM>). Thus, the techniques described herein enable each of the users within the user group for the collaboration object <NUM> to access the data file <NUM> via both of the collaboration object <NUM> (that is accessible by the entire user group) and their own user-specific instance <NUM> of the second application <NUM>(<NUM>). In this way, users are seamlessly enabled to access content that was edited via the application extension being executed by the first application in association with the collaboration object directly via their own user-specific stand-alone instance <NUM> of the second application <NUM>(<NUM>) operating on their user device <NUM>. I data file <NUM> is generated as a result of the instruction <NUM> being received via the first application <NUM>(<NUM>). For example, during a virtual call the participants may decide to collaboratively generate content using the second functionalities of the second application <NUM>(<NUM>). Thus, one of the participants may select an icon or user interface element that extends the second application <NUM>(<NUM>) into the virtual call. Selection of the icon may result in the instruction <NUM> being sent to the first application <NUM>(<NUM>) and may trigger the first application <NUM>(<NUM>) to being executing the application extension <NUM> (e.g., a plug-in) in association with the virtual call. This may result in a function tray of the second application <NUM>(<NUM>) being displayed to all of the participants in the context of the virtual call. Selection of the icon may also cause the collaboration platform <NUM> to generate the data file <NUM> in storage that is accessible by each of the first application <NUM>(<NUM>) and the second application <NUM>(<NUM>). Selection of the icon may also cause the collaboration platform <NUM> to provide the file pointer to the first application <NUM>(<NUM>). In some embodiments, the file pointer <NUM> points to a single data file <NUM> that is shared by and accessible to all of the user accounts included in the group definition <NUM>. For example, the instruction <NUM> may trigger generation of a single notetaking file or whiteboard file and each instance <NUM> of the second application for user accounts in the group definition <NUM> point to the same file. In this way, all of the users within the group may see all of the others users' inputs to the single data file. Additionally, or alternatively, the instruction <NUM> may cause the collaboration platform <NUM> to a plurality of user-specific instances of the data file in association with the plurality of user accounts included within the group definition. Then, the application configuration parameters <NUM> may cause individual instances <NUM> of the second application to provision individual user accounts, of the plurality of user accounts, with access to individual user-specific instances of the data file initially shared via the instruction <NUM>. In this way, each user may start off with the same content but may mark it up as she sees fit to generate her own content in accordance with her own preferences.

Turning now to <FIG>, illustrated is a system diagram illustrating an example environment <NUM> in which a data file <NUM> being accessed via a collaboration object <NUM> of a first web-service domain <NUM>(<NUM>) results in the data file <NUM> becoming accessible to a user group via a second web-service domain <NUM>(<NUM>). The first web-service domain <NUM>(<NUM>) may include one or more servers that implement aspects of a first application <NUM>(<NUM>) that provides a set of first functionalities <NUM>(<NUM>). For example, the first application <NUM>(<NUM>) may facilitate a collaboration object <NUM> between a group of users defined by a group definition <NUM>. The collaboration object <NUM> may be a prescheduled virtual meeting for which meeting invitations are sent to the group of users, an impromptu virtual call between the group of users (e.g., one user may call the others without prescheduling the event), a channel, a chat, an email thread, and so on.

The second web-service domain <NUM>(<NUM>) may be provide third-party services that are extendable into the first application <NUM>(<NUM>) via an application extension <NUM> that is executable by the first web-service domain <NUM>(<NUM>). For example, the second web-service domain <NUM>(<NUM>) may include one or more servers that implement aspects of a second application <NUM>(<NUM>) that provides a set of second functionalities <NUM>(<NUM>). Execution of the application extension <NUM> by the first application <NUM>(<NUM>) may expose the second functionalities <NUM>(<NUM>) to the group of users within the context of the collaboration object <NUM>. For example, under circumstances where the first application <NUM>(<NUM>) is a web-conferencing application and the second application <NUM>(<NUM>) is a data analytics application, execution of the application extension during a virtual communication session may enable the participants of the virtual communication session to collaboratively utilize data analytics functionalities provided by the second application <NUM>(<NUM>) within the context of the virtual communication session.

With respect to the data flow scenario of <FIG>, at time T<NUM> each of the first user device <NUM> through the Nth user device <NUM>(N) may be operating respective instances <NUM> of the first application <NUM>(<NUM>) in association the collaboration object <NUM>. For example, the instances <NUM> may be facilitating a communication session between the users of each of the first through Nth user device.

At time T<NUM> while communicating via the collaboration object <NUM>, the first user may generate an instruction <NUM> to cause the first application <NUM>(<NUM>) to begin running the application extension <NUM> to extend the <NUM>nd functionalities <NUM>(<NUM>) from the second web-service domain <NUM>(<NUM>) into the collaboration object <NUM>. For example, in the context of the collaboration object <NUM> being the communication session, the first user may select an icon, representing the second application <NUM>(<NUM>), that is presented by the first instance <NUM>(<NUM>). In the illustrated example, the first user already has access to the data file <NUM> and time T<NUM> and therefore a file pointer <NUM> may already reside within her user-specific instance <NUM> of the second application <NUM>(<NUM>). Furthermore, the first user provides an indication of the file pointer <NUM> within the instruction <NUM> to inform the first application <NUM>(<NUM>) that is operating in the first web-service domain <NUM>(<NUM>) of which specific data file is to be accessed from the second web-service domain <NUM>(<NUM>) and shared via the collaboration object <NUM>.

At time T<NUM>, the first web-service domain <NUM>(<NUM>) transmits update data <NUM> to the second web-service domain <NUM>(<NUM>) to inform the second web-service domain <NUM>(<NUM>) that the first user has elected to share the data file <NUM> with the group of users for the collaboration object <NUM>. In some embodiments, the update data <NUM> may cause the second web-service domain <NUM>(<NUM>) to update application configuration parameters <NUM> to reflect that the group of users associated with the collaboration session <NUM> have been granted access to the data file <NUM> identified within the instruction <NUM>.

Then, at time T<NUM>, the second web-service domain <NUM>(<NUM>) may transmit instances of application configuration parameters <NUM> to at least some of the user devices <NUM> that belong or correspond to the users defined by the group definition <NUM>. In some embodiments, one or both of the web-service domains <NUM> may map user account data <NUM> for the first application <NUM>(<NUM>) with user account data <NUM> for the second application <NUM>(<NUM>) to identify which users within the group have subscriptions already associated with respective instances <NUM> of the second application <NUM>(<NUM>). As illustrated, receipt of the second instance <NUM>(<NUM>) and Nth instance <NUM>(N) of the application configuration parameters cause the second instance <NUM>(<NUM>) and Nth instance <NUM>(N) of the second application <NUM>(<NUM>) to also include the file pointer <NUM>. Thus, as a result of the first user sharing the data file <NUM> into the collaboration object <NUM>, the instances <NUM> of the second application <NUM>(<NUM>) may be automatically updated to provide the other users with who the data file is shared with seamless access to the data file <NUM> via a completely different application that the one within which the file was shared by the first user. It can be appreciated therefore that the techniques described herein facilitate synchronization of shared data files across different applications - even when those applications are provided bv separate web service entities that operate different web-service domains <NUM>.

Turning now to <FIG>, illustrated is a system diagram illustrating an example environment <NUM> in which calendar activity <NUM> that occurs in association with instances <NUM> of a first application results in data content being selectively added to instances <NUM> of a second application. As a specific example, a file pointer <NUM> that is identified within the meeting invitations <NUM> and that points to a specific file (e.g., within an online storage location) may be added to user-specific instances <NUM> of a second application in response to individual users being sent an electronic invitation <NUM> via instances <NUM> of a first application.

In the illustrated example, the calendar activity <NUM> includes invitations <NUM> being generated via a first user-specific instance <NUM>(<NUM>) of a first application. The calendar activity <NUM> further includes the generated invitations <NUM> being transmitted over one more networks and received by a second user-specific instance <NUM>(<NUM>) of the first application and a third user-specific instance <NUM>(<NUM>) of the first application. In some embodiments, user response data that is generated via the second instance <NUM>(<NUM>) or the Nth instance <NUM>(N) of the first application may control application configuration data corresponding to the second instance <NUM>(<NUM>) or the Nth instance <NUM>(N) of the second application, respectively. For example, application configuration data may be generated based on whether a user accepts an invitation <NUM>, tentatively accepts an invitation <NUM>, responds to a meeting invitation by proposing a new time, declines a meeting invitation, or so on.

A collaboration application service <NUM> may generate calendar application data <NUM> based on the calendar activity <NUM>. The collaboration application service <NUM> may then transmit the calendar application data <NUM> to a content editing application service <NUM> which may then generate user interface data <NUM> based thereon. Generally described, the user interface data <NUM> may control aspects of a user experience that is generate via individual ones of the instances <NUM> of the second application. In the illustrated example, the calendar activity data <NUM> includes the second user declining the second meeting invitation <NUM>(<NUM>) via the second instance <NUM>(<NUM>) of the first application. As a result of the second user declining the second meeting invitation <NUM>(<NUM>), the user interface data <NUM> causes the second instance <NUM>(<NUM>) that is displayed via the second user device <NUM>(<NUM>) to omit the file pointer <NUM> to the data file <NUM> that is identified within the second meeting invitation <NUM>(<NUM>). As shown, the calendar activity data <NUM> further includes the Nth user accepting the Nth meeting invitation <NUM>(N) via the Nth instance <NUM>(N) of the first application. As a result of the Nth user accepting the Nth meeting invitation <NUM>(N), the user interface data <NUM> causes the Nth instance <NUM>(N) that is displayed via the Nth user device <NUM>(N) to include a graphical user interface element that is associated with the file pointer <NUM> to the data file <NUM> that is identified within the Nth meeting invitation <NUM>(N). In this way, the techniques described herein facilitate seamless integration of data content that is shared within calendar objects generated via a first application into a user experience for invitees of the calendar objects within a separate application.

<FIG> illustrate various aspects of exemplary GUIs that can be displayed in association with the technologies described herein. <FIG> are described below in the context of a sequence of operations resulting in various application configuration changes to user-specific instances of a collaboration application and a content editing application.

<FIG> illustrates an exemplary messaging GUI <NUM> that can be presented to a first user in association with the collaboration application. As illustrated, the messaging GUI <NUM> corresponds to a message thread between a group of three users. Furthermore, the messaging GUI <NUM> corresponds to a user-specific instance <NUM>, of the collaboration application, that is being run on a first user device <NUM>(<NUM>). The messaging GUI <NUM> includes a message generation field for typing and/or dictating message content in association with a persistent workplace chat as shown represented. Thus, by using the message generation field, a user may generate and transmit messages in association with the persistent workplace chat so that any other members of this persistent workplace chat receive and retain continued access to such messages. Exemplary such persistent workplace chats include, but are not limited to, a conversation thread within the MICROSOFT TEAMS collaboration platform, a SLACK conversation object, or any other type of multi-user persistent chat system.

For purposes of the present example, the messaging GUI <NUM> identifies the group definition <NUM> for the collaboration object of the message thread. Specifically, a set of graphical elements <NUM> identify each user that is included within the message thread. The messaging GUI <NUM> further includes a user interface element <NUM> that enables one or more users to initiate a virtual call between the entire group of users that are included within the group definition. To fully convey a contemplated use case scenario of the techniques described herein, the illustrated example shows a sequence of messages leading up to a virtual call that is facilitated by the collaboration application.

<FIG> illustrates an exemplary virtual call GUI <NUM> that can be presented to the first user in association with the collaboration application. As illustrated, the virtual call GUI <NUM> corresponds to a live virtual call between the group of three users of the message thread. The live virtual call may be initiated as a result of the first user selecting the user interface element <NUM>. Then, during the virtual call, the first user may further select a user interface element <NUM> that causes the collaboration application to utilize an application extension <NUM> to expose the second functionalities <NUM>(<NUM>) associated with a content editing application. In this way, the application extension <NUM> enables the group of users that are associated with a collaboration object (e.g., participants of a virtual call, members of a message thread, etc.) to implement the second functionalities <NUM>(<NUM>) of the content editing application while collaboratively viewing content of that application within the context of the collaboration object <NUM>. For example, as illustrated, the virtual call GUI <NUM> is displaying a set of graphical user interface elements that are selectable to implement the second functionalities <NUM>(<NUM>) and are arranged in accordance with a layout of the content editing application.

<FIG> illustrates an exemplary application extension GUI <NUM> that is configured to enable a user to define directory location data for content being generated via the application extension <NUM> directly through the virtual call GUI <NUM>. As illustrated, the first user has selected a graphical user interface element <NUM> that is displayed within the application extension GUI <NUM> in order to expose an organizational structure of the content editing application. For example, as shown, the displayed organizational structure includes various directory locations that exist within the first user's instance <NUM>(<NUM>) of the content editing application. As further illustrated, the application extension GUI <NUM> also enables the user to select from existing locations (e.g., location <NUM>, location <NUM>, and location <NUM>) and/or to generate a new location within his existing organizational structure for the content editing application. As described below, the first user's selection of a directory location for content being edited via the application extension GUI <NUM> that is shown within the collaboration object GUI may control where the content appears in both his instance <NUM>(<NUM>) of the content editing application as well as other participants instances <NUM>.

<FIG> illustrates an exemplary GUI <NUM> that corresponds to the second user's instance <NUM>(<NUM>) of the content editing application. The GUI <NUM> illustrates that as a result of the first user deploying the application extension <NUM> to share content with the group within the collaboration application (e.g., during a virtual call or any other collaboration object for that matter) the shared content automatically is compiled into the user-specific instances <NUM> of the content editing application for the entire group. Additionally, as shown the content may be synchronized to the same directory location for the entire group within the content editing application based on the directory location data generated via the application extension <NUM> directly through the collaboration application.

As shown in <FIG>, the GUI <NUM> that corresponds to the second user's instance <NUM>(<NUM>) of the content editing application enables the second user to generate and/or modify content that is shared via the collaboration object directly via the content editing application. Here, the second user has added the content shown in the box <NUM> into the content via the instance <NUM>(<NUM>) during the virtual call.

As shown in <FIG>, the second user's input via the instance <NUM>(<NUM>) during the virtual call causes the application extension GUI <NUM> of the first user's instance <NUM>(<NUM>). Furthermore, the application extension GUI <NUM> may include a status indicator <NUM> indicating which user (e.g., the second user in this case) is modifying content at specific locations within the data file. <FIG> illustrates an exemplary notification <NUM> that may be displayed in response to content for a second application being shared with a user via a collaboration object of a first application. In the illustrated example, the notification <NUM> is displayed in association with an instance of the second application that uniquely corresponds to the user that the content has been shared with. As illustrated, the notification <NUM> includes a message that is designed to inform the user that content has been shared with them by another user via a virtual meeting object. For example, the content may be shared in an ad hoc manner during the virtual meeting. As another example, the content may be shared with them via a meeting invitation for a yet to occur pre-scheduled meeting.

In some embodiments, the notification <NUM> may provide the recipient user with one or more options to select between. For example, as illustrated, the notification <NUM> informs the recipient user (i.e., the user with whom content is shared by another user) the name of the other user that has shared content with them. Specifically, the notification <NUM> states "Tom Price has shared OneNote content with you via a virtual meeting object. " Furthermore, the notification <NUM> may inquire whether the recipient user would like to have the content that has been shared with them pinned to their instance of the second application. For example, the illustrated notification <NUM> states "Would you like this content to be automatically pinned within your personal OneNote application?" As further illustrated, the notification <NUM> provides the recipient user with options to: (i) accept having their user-specific instance of the second application updated based on the content that is shared (e.g., by selecting the "YES" button), (ii) decline having their user-specific instance of the second application updated based on the content that is shared (e.g., by selecting the "NO" button), or (iii) electing to preview the content (e.g., by selecting the "SHOW ME A PREVIEW" button) prior to accepting or declining the option of having their user-specific instance of the second application updated based on the content that is shared. <FIG> is a diagram illustrating aspects of a routine <NUM> for responding to content being associated with a collaboration object of a first application by automatically configuring user-specific instances of a second application for a group of users associated with the collaboration object. It should be understood by those of ordinary skill in the art that the operations of the methods disclosed herein are not necessarily presented in any particular order and that performance of some or all of the operations in an alternative order(s) is possible and is contemplated. The operations have been presented in the demonstrated order for ease of description and illustration. Operations may be added, omitted, performed together, and/or performed simultaneously, without departing from the scope of the appended claims.

It should also be understood that the illustrated methods can end at any time and need not be performed in their entireties. Some or all operations of the methods, and/or substantially equivalent operations, can be performed by execution of computer-readable instructions included on a computer-storage media, as defined herein. The term "computer-readable instructions," and variants thereof, as used in the description and claims, is used expansively herein to include routines, applications, application modules, program modules, programs, components, data structures, algorithms, and the like. Computer-readable instructions can be implemented on various system configurations, including single-processor or multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based, programmable consumer electronics, combinations thereof, and the like.

Thus, it should be appreciated that the logical operations described herein are implemented (<NUM>) as a sequence of computer implemented acts or program modules running on a computing system such as those described herein) and/or (<NUM>) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof.

Additionally, the operations illustrated in <FIG> and the other figures can be implemented in association with the example presentation UIs described above. For instance, the various device(s) and/or module(s) described herein can generate, transmit, receive, and/or display data associated with content of a communication session (e.g., live content, broadcasted event, recorded content, etc.) and/or a presentation UI that includes renderings of one or more participants of remote computing devices, avatars, channels, persistent chat sessions, video streams, images, virtual objects, and/or applications associated with a communication session. The routine <NUM> starts at operation <NUM>, where a system receives collaboration object data that includes a group definition for a collaboration object corresponding to a first application. The collaboration object (communication session) may be a chat, , a virtual call, a prescheduled meeting, an email thread, and various other types of collaboration objects that are designed to facilitate collaborative communications between a group of users.

The routine <NUM> proceeds to operation <NUM>, where the system receives an instruction to associate a data file, corresponding to a second application, with the collaboration object corresponding to the first application. In some embodiments, the instruction causes the first application to provide access to content of the data file in association with the collaboration object via an application extension of the second application that is executable by the first application.

The routine <NUM> proceeds to operation <NUM>, where the system configures, in response to the instruction, object permissions data to grant a plurality of user accounts identified by the group definition with access to the content of the data file corresponding to the second application. The routine <NUM> proceeds to operation <NUM>, where the system updates, based on the object permission data, application configuration parameters for the second application in association with the plurality of user accounts.

The routine <NUM> proceeds to operation <NUM>, where the system transmits the application configuration parameters to instances of the second application that correspond to the plurality of user accounts.

It should be appreciated that the above-described subject matter may be implemented as a computer-controlled apparatus, a computer process, a computing system, or as an article of manufacture such as a computer-readable storage medium. The operations of the example methods are illustrated in individual blocks and summarized with reference to those blocks. The methods are illustrated as logical flows of blocks, each block of which can represent one or more operations that can be implemented in hardware, software, or a combination thereof. In the context of software, the operations represent computer-executable instructions stored on one or more computer-readable media that, when executed by one or more processors, enable the one or more processors to perform the recited operations.

Generally, computer-executable instructions include routines, programs, objects, modules, components, data structures, and the like that perform particular functions or implement particular abstract data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be executed in any order, combined in any order, subdivided into multiple sub-operations, and/or executed in parallel to implement the described processes. The described processes can be performed by resources associated with one or more device(s) such as one or more internal or external CPUs or GPUs, and/or one or more pieces of hardware logic such as field-programmable gate arrays ("FPGAs"), digital signal processors ("DSPs"), or other types of accelerators.

All of the methods and processes described above may be embodied in, and fully automated via, software code modules executed by one or more general purpose computers or processors. The code modules may be stored in any type of computer-readable storage medium or other computer storage device, such as those described below. Some or all of the methods may alternatively be embodied in specialized computer hardware, such as that described below. Any routine descriptions, elements or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code that include one or more executable instructions for implementing specific logical functions or elements in the routine. Alternate implementations are included within the scope of the examples described herein in which elements or functions may be deleted, or executed out of order from that shown or discussed, including substantially synchronously or in reverse order, depending on the functionality involved as would be understood by those skilled in the art.

<FIG> is a diagram illustrating an example environment <NUM> in which a system <NUM> can implement the techniques disclosed herein. In some implementations, a system <NUM> may function to collect, analyze, and share data defining one or more objects that are displayed to users of a communication session <NUM>.

As illustrated, the communication session <NUM> may be implemented between a number of client computing devices <NUM>(<NUM>) through <NUM>(N) (where N is a number having a value of two or greater) that are associated with or are part of the system <NUM>. The client computing devices <NUM>(<NUM>) through <NUM>(N) enable users, also referred to as individuals, to participate in the communication session <NUM>.

In this example, the communication session <NUM> is hosted, over one or more network(s) <NUM>, by the system <NUM>. That is, the system <NUM> can provide a service that enables users of the client computing devices <NUM>(<NUM>) through <NUM>(N) to participate in the communication session <NUM> (e.g., via a live viewing and/or a recorded viewing). Consequently, a "participant" to the communication session <NUM> can comprise a user and/or a client computing device (e.g., multiple users may be in a room participating in a communication session via the use of a single client computing device), each of which can communicate with other participants. As an alternative, the communication session <NUM> can be hosted by one of the client computing devices <NUM>(<NUM>) through <NUM>(N) utilizing peer-to-peer technologies. The system <NUM> can also host chat conversations and other team collaboration functionality (e.g., as part of an application suite).

In some implementations, such chat conversations and other team collaboration functionality are considered external communication sessions distinct from the communication session <NUM>. A computing system <NUM> that collects participant data in the communication session <NUM> may be able to link to such external communication sessions. Therefore, the system may receive information, such as date, time, session particulars, and the like, that enables connectivity to such external communication sessions. In one example, a chat conversation can be conducted in accordance with the communication session <NUM>. Additionally, the system <NUM> may host the communication session <NUM>, which includes at least a plurality of participants co-located at a meeting location, such as a meeting room or auditorium, or located in disparate locations.

In examples described herein, client computing devices <NUM>(<NUM>) through <NUM>(N) participating in the communication session <NUM> are configured to receive and render for display, on a user interface of a display screen, communication data. The communication data can comprise a collection of various instances, or streams, of live content and/or recorded content. The collection of various instances, or streams, of live content and/or recorded content may be provided by one or more cameras, such as video cameras. For example, an individual stream of live or recorded content can comprise media data associated with a video feed provided by a video camera (e.g., audio and visual data that capture the appearance and speech of a user participating in the communication session). In some implementations, the video feeds may comprise such audio and visual data, one or more still images, and/or one or more avatars. The one or more still images may also comprise one or more avatars.

Another example of an individual stream of live or recorded content can comprise media data that includes an avatar of a user participating in the communication session along with audio data that captures the speech of the user. Yet another example of an individual stream of live or recorded content can comprise media data that includes a file displayed on a display screen along with audio data that captures the speech of a user. Accordingly, the various streams of live or recorded content within the communication data enable a remote meeting to be facilitated between a group of people and the sharing of content within the group of people. In some implementations, the various streams of live or recorded content within the communication data may originate from a plurality of co-located video cameras, positioned in a space, such as a room, to record or stream live a presentation that includes one or more individuals presenting and one or more individuals consuming presented content.

A participant or attendee can view content of the communication session <NUM> live as activity occurs, or alternatively, via a recording at a later time after the activity occurs. In examples described herein, client computing devices <NUM>(<NUM>) through <NUM>(N) participating in the communication session <NUM> are configured to receive and render for display, on a user interface of a display screen, communication data. The communication data can comprise a collection of various instances, or streams, of live and/or recorded content. For example, an individual stream of content can comprise media data associated with a video feed (e.g., audio and visual data that capture the appearance and speech of a user participating in the communication session). Another example of an individual stream of content can comprise media data that includes an avatar of a user participating in the conference session along with audio data that captures the speech of the user. Yet another example of an individual stream of content can comprise media data that includes a content item displayed on a display screen and/or audio data that captures the speech of a user. Accordingly, the various streams of content within the communication data enable a meeting or a broadcast presentation to be facilitated amongst a group of people dispersed across remote locations.

A participant or attendee to a communication session is a person that is in range of a camera, or other image and/or audio capture device such that actions and/or sounds of the person which are produced while the person is viewing and/or listening to the content being shared via the communication session can be captured (e.g., recorded). For instance, a participant may be sitting in a crowd viewing the shared content live at a broadcast location where a stage presentation occurs. Or a participant may be sitting in an office conference room viewing the shared content of a communication session with other colleagues via a display screen. Even further, a participant may be sitting or standing in front of a personal device (e.g., tablet, smartphone, computer, etc.) viewing the shared content of a communication session alone in their office or at home.

The system <NUM> of <FIG> includes device(s) <NUM>. The device(s) <NUM> and/or other components of the system <NUM> can include distributed computing resources that communicate with one another and/or with the client computing devices <NUM>(<NUM>) through <NUM>(N) via the one or more network(s) <NUM>. In some examples, the system <NUM> may be an independent system that is tasked with managing aspects of one or more communication sessions such as communication session <NUM>. As an example, the system <NUM> may be managed by entities such as SLACK, WEBEX, GOTOMEETING, GOOGLE HANGOUTS, etc..

Network(s) <NUM> may include, for example, public networks such as the Internet, private networks such as an institutional and/or personal intranet, or some combination of private and public networks. Network(s) <NUM> may also include any type of wired and/or wireless network, including but not limited to local area networks ("LANs"), wide area networks ("WANs"), satellite networks, cable networks, Wi-Fi networks, WiMax networks, mobile communications networks (e.g., <NUM>, <NUM>, and so forth) or any combination thereof. Network(s) <NUM> may utilize communications protocols, including packet-based and/or datagram-based protocols such as Internet protocol ("IP"), transmission control protocol ("TCP"), user datagram protocol ("UDP"), or other types of protocols. Moreover, network(s) <NUM> may also include a number of devices that facilitate network communications and/or form a hardware basis for the networks, such as switches, routers, gateways, access points, firewalls, base stations, repeaters, backbone devices, and the like.

In some examples, network(s) <NUM> may further include devices that enable connection to a wireless network, such as a wireless access point ("WAP"). Examples support connectivity through WAPs that send and receive data over various electromagnetic frequencies (e.g., radio frequencies), including WAPs that support Institute of Electrical and Electronics Engineers ("IEEE") <NUM> standards (e.g., <NUM>, <NUM>. 7ac and so forth), and other standards.

In various examples, device(s) <NUM> may include one or more computing devices that operate in a cluster or other grouped configuration to share resources, balance load, increase performance, provide fail-over support or redundancy, or for other purposes. For instance, device(s) <NUM> may belong to a variety of classes of devices such as traditional server-type devices, desktop computer-type devices, and/or mobile-type devices. Thus, although illustrated as a single type of device or a server-type device, device(s) <NUM> may include a diverse variety of device types and are not limited to a particular type of device. Device(s) <NUM> may represent, but are not limited to, server computers, desktop computers, web-server computers, personal computers, mobile computers, laptop computers, tablet computers, or any other sort of computing device. A client computing device (e.g., one of client computing device(s) <NUM>(<NUM>) through <NUM>(N)) (each of which are also referred to herein as a "data processing system") may belong to a variety of classes of devices, which may be the same as, or different from, device(s) <NUM>, such as traditional client-type devices, desktop computer-type devices, mobile-type devices, special purpose-type devices, embedded-type devices, and/or wearable-type devices. Thus, a client computing device can include, but is not limited to, a desktop computer, a game console and/or a gaming device, a tablet computer, a personal data assistant ("PDA"), a mobile phone/tablet hybrid, a laptop computer, a telecommunication device, a computer navigation type client computing device such as a satellite-based navigation system including a global positioning system ("GPS") device, a wearable device, a virtual reality ("VR") device, an augmented reality ("AR") device, an implanted computing device, an automotive computer, a network-enabled television, a thin client, a terminal, an Internet of Things ("IoT") device, a work station, a media player, a personal video recorder ("PVR"), a set-top box, a camera, an integrated component (e.g., a peripheral device) for inclusion in a computing device, an appliance, or any other sort of computing device. Moreover, the client computing device may include a combination of the earlier listed examples of the client computing device such as, for example, desktop computer-type devices or a mobile-type device in combination with a wearable device, etc..

Client computing device(s) <NUM>(<NUM>) through <NUM>(N) of the various classes and device types can represent any type of computing device having one or more data processing unit(s) <NUM> operably connected to computer-readable media <NUM> such as via a bus <NUM>, which in some instances can include one or more of a system bus, a data bus, an address bus, a PCI bus, a Mini-PCI bus, and any variety of local, peripheral, and/or independent buses.

Executable instructions stored on computer-readable media <NUM> may include, for example, an operating system <NUM>, a client module <NUM>, a profile module <NUM>, and other modules, programs, or applications that are loadable and executable by data processing units(s) <NUM>.

Client computing device(s) <NUM>(<NUM>) through <NUM>(N) may also include one or more interface(s) <NUM> to enable communications between client computing device(s) <NUM>(<NUM>) through <NUM>(N) and other networked devices, such as device(s) <NUM>, over network(s) <NUM>. Such network interface(s) <NUM> may include one or more network interface controllers (NICs) or other types of transceiver devices to send and receive communications and/or data over a network. Moreover, client computing device(s) <NUM>(<NUM>) through <NUM>(N) can include input/output ("I/O") interfaces (devices) <NUM> that enable communications with input/output devices such as user input devices including peripheral input devices (e.g., a game controller, a keyboard, a mouse, a pen, a voice input device such as a microphone, a video camera for obtaining and providing video feeds and/or still images, a touch input device, a gestural input device, and the like) and/or output devices including peripheral output devices (e.g., a display, a printer, audio speakers, a haptic output device, and the like). <FIG> illustrates that client computing device <NUM>(<NUM>) is in some way connected to a display device (e.g., a display screen <NUM>(N)), which can display a UI according to the techniques described herein.

In the example environment <NUM> of <FIG>, client computing devices <NUM>(<NUM>) through <NUM>(N) may use their respective client modules <NUM> to connect with one another and/or other external device(s) in order to participate in the communication session <NUM>, or in order to contribute activity to a collaboration environment. For instance, a first user may utilize a client computing device <NUM>(<NUM>) to communicate with a second user of another client computing device <NUM>(<NUM>). When executing client modules <NUM>, the users may share data, which may cause the client computing device <NUM>(<NUM>) to connect to the system <NUM> and/or the other client computing devices <NUM>(<NUM>) through <NUM>(N) over the network(s) <NUM>.

The client computing device(s) <NUM>(<NUM>) through <NUM>(N) may use their respective profile modules <NUM> to generate participant profiles (not shown in <FIG>) and provide the participant profiles to other client computing devices and/or to the device(s) <NUM> of the system <NUM>. A participant profile may include one or more of an identity of a user or a group of users (e.g., a name, a unique identifier ("ID"), etc.), user data such as personal data, machine data such as location (e.g., an IP address, a room in a building, etc.) and technical capabilities, etc. Participant profiles may be utilized to register participants for communication sessions.

As shown in <FIG>, the device(s) <NUM> of the system <NUM> include a server module <NUM> and an output module <NUM>. In this example, the server module <NUM> is configured to receive, from individual client computing devices such as client computing devices <NUM>(<NUM>) through <NUM>(N), media streams <NUM>(<NUM>) through <NUM>(N). As described above, media streams can comprise a video feed (e.g., audio and visual data associated with a user), audio data which is to be output with a presentation of an avatar of a user (e.g., an audio only experience in which video data of the user is not transmitted), text data (e.g., text messages), file data and/or screen sharing data (e.g., a document, a slide deck, an image, a video displayed on a display screen, etc.), and so forth. Thus, the server module <NUM> is configured to receive a collection of various media streams <NUM>(<NUM>) through <NUM>(N) during a live viewing of the communication session <NUM> (the collection being referred to herein as "media data <NUM>"). In some scenarios, not all of the client computing devices that participate in the communication session <NUM> provide a media stream. For example, a client computing device may only be a consuming, or a "listening", device such that it only receives content associated with the communication session <NUM> but does not provide any content to the communication session <NUM>.

In various examples, the server module <NUM> can select aspects of the media streams <NUM> that are to be shared with individual ones of the participating client computing devices <NUM>(<NUM>) through <NUM>(N). Consequently, the server module <NUM> may be configured to generate session data <NUM> based on the streams <NUM> and/or pass the session data <NUM> to the output module <NUM>. Then, the output module <NUM> may communicate communication data <NUM> to the client computing devices (e.g., client computing devices <NUM>(<NUM>) through <NUM>(<NUM>) participating in a live viewing of the communication session). The communication data <NUM> may include video, audio, and/or other content data, provided by the output module <NUM> based on content <NUM> associated with the output module <NUM> and based on received session data <NUM>.

As shown, the output module <NUM> transmits communication data <NUM>(<NUM>) to client computing device <NUM>(<NUM>), and transmits communication data <NUM>(<NUM>) to client computing device <NUM>(<NUM>), and transmits communication data <NUM>(<NUM>) to client computing device <NUM>(<NUM>), etc. The communication data <NUM> transmitted to the client computing devices can be the same or can be different (e.g., positioning of streams of content within a user interface may vary from one device to the next).

In various implementations, the device(s) <NUM> and/or the client module <NUM> can include GUI presentation module <NUM>. The GUI presentation module <NUM> may be configured to analyze communication data <NUM> that is for delivery to one or more of the client computing devices <NUM>. Specifically, the UI presentation module <NUM>, at the device(s) <NUM> and/or the client computing device <NUM>, may analyze communication data <NUM> to determine an appropriate manner for displaying video, image, and/or content on the display screen <NUM> of an associated client computing device <NUM>. In some implementations, the GUI presentation module <NUM> may provide video, image, and/or content to a presentation GUI <NUM> rendered on the display screen <NUM> of the associated client computing device <NUM>. The presentation GUI <NUM> may be caused to be rendered on the display screen <NUM> by the GUI presentation module <NUM>. The presentation GUI <NUM> may include the video, image, and/or content analyzed by the GUI presentation module <NUM>.

In some implementations, the presentation GUI <NUM> may include a plurality of sections or grids that may render or comprise video, image, and/or content for display on the display screen <NUM>. For example, a first section of the presentation GUI <NUM> may include a video feed of a presenter or individual, a second section of the presentation GUI <NUM> may include a video feed of an individual consuming meeting information provided by the presenter or individual. The GUI presentation module <NUM> may populate the first and second sections of the presentation GUI <NUM> in a manner that properly imitates an environment experience that the presenter and the individual may be sharing.

In some implementations, the GUI presentation module <NUM> may enlarge or provide a zoomed view of the individual represented by the video feed in order to highlight a reaction, such as a facial feature, the individual had to the presenter. In some implementations, the presentation GUI <NUM> may include a video feed of a plurality of participants associated with a meeting, such as a general communication session. In other implementations, the presentation GUI <NUM> may be associated with a channel, such as a chat channel, enterprise teams channel, or the like. Therefore, the presentation GUI <NUM> may be associated with an external communication session that is different than the general communication session.

<FIG> illustrates a diagram that shows example components of an example device <NUM> (also referred to herein as a "computing device") configured to generate data for some of the user interfaces disclosed herein. The device <NUM> may generate data that may include one or more sections that may render or comprise video, images, virtual objects, and/or content for display on the display screen <NUM>. The device <NUM> may represent one of the device(s) described herein. Additionally, or alternatively, the device <NUM> may represent one of the client computing devices <NUM>.

As illustrated, the device <NUM> includes one or more data processing unit(s) <NUM>, computer-readable media <NUM>, and communication interface(s) <NUM>. The components of the device <NUM> are operatively connected, for example, via a bus <NUM>, which may include one or more of a system bus, a data bus, an address bus, a PCI bus, a Mini-PCI bus, and any variety of local, peripheral, and/or independent buses.

As utilized herein, data processing unit(s), such as the data processing unit(s) <NUM> and/or data processing unit(s) <NUM>, may represent, for example, a CPU-type data processing unit, a GPU-type data processing unit, a field-programmable gate array ("FPGA"), another class of DSP, or other hardware logic components that may, in some instances, be driven by a CPU. For example, and without limitation, illustrative types of hardware logic components that may be utilized include Application-Specific Integrated Circuits ("ASICs"), Application-Specific Standard Products ("ASSPs"), System-on-a-Chip Systems ("SOCs"), Complex Programmable Logic Devices ("CPLDs"), etc..

As utilized herein, computer-readable media, such as computer-readable media <NUM> and computer-readable media <NUM>, may store instructions executable by the data processing unit(s). The computer-readable media may also store instructions executable by external data processing units such as by an external CPU, an external GPU, and/or executable by an external accelerator, such as an FPGA type accelerator, a DSP type accelerator, or any other internal or external accelerator. In various examples, at least one CPU, GPU, and/or accelerator is incorporated in a computing device, while in some examples one or more of a CPU, GPU, and/or accelerator is external to a computing device.

Computer-readable media, which might also be referred to herein as a computer-readable medium, may include computer storage media and/or communication media. Computer storage media may include one or more of volatile memory, nonvolatile memory, and/or other persistent and/or auxiliary computer storage media, removable and non-removable computer storage media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Thus, computer storage media includes tangible and/or physical forms of media included in a device and/or hardware component that is part of a device or external to a device, including but not limited to random access memory ("RAM"), static random-access memory ("SRAM"), dynamic random-access memory ("DRAM"), phase change memory ("PCM"), read-only memory ("ROM"), erasable programmable read-only memory ("EPROM"), electrically erasable programmable read-only memory ("EEPROM"), flash memory, compact disc read-only memory ("CD-ROM"), digital versatile disks ("DVDs"), optical cards or other optical storage media, magnetic cassettes, magnetic tape, magnetic disk storage, magnetic cards or other magnetic storage devices or media, solid-state memory devices, storage arrays, network attached storage, storage area networks, hosted computer storage or any other storage memory, storage device, and/or storage medium that can be used to store and maintain information for access by a computing device.

In contrast to computer storage media, communication media may embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism. As defined herein, computer storage media does not include communication media. That is, computer storage media does not include communications media consisting solely of a modulated data signal, a carrier wave, or a propagated signal, per se.

Communication interface(s) <NUM> may represent, for example, network interface controllers ("NICs") or other types of transceiver devices to send and receive communications over a network. Furthermore, the communication interface(s) <NUM> may include one or more video cameras and/or audio devices <NUM> to enable generation of video feeds and/or still images, and so forth.

In the illustrated example, computer-readable media <NUM> includes a data store <NUM>. In some examples, the data store <NUM> includes data storage such as a database, data warehouse, or other type of structured or unstructured data storage. In some examples, the data store <NUM> includes a corpus and/or a relational database with one or more tables, indices, stored procedures, and so forth to enable data access including one or more of hypertext markup language ("HTML") tables, resource description framework ("RDF") tables, web ontology language ("OWL") tables, and/or extensible markup language ("XML") tables, for example.

The data store <NUM> may store data for the operations of processes, applications, components, and/or modules stored in computer-readable media <NUM> and/or executed by data processing unit(s) <NUM> and/or accelerator(s). For instance, in some examples, the data store <NUM> may store session data <NUM> (e.g., session data <NUM> as shown in FIGURE <NUM>), profile data <NUM> (e.g., associated with a participant profile), and/or other data. The session data <NUM> can include a total number of participants (e.g., users and/or client computing devices) in a communication session, activity that occurs in the communication session, a list of invitees to the communication session, and/or other data related to when and how the communication session is conducted or hosted. The data store <NUM> may also include content data <NUM>, such as the content that includes video, audio, or other content for rendering and display on one or more of the display screens <NUM>.

Alternately, some or all of the above-referenced data can be stored on separate memories <NUM> on board one or more data processing unit(s) <NUM> such as a memory on board a CPU-type processor, a GPU-type processor, an FPGA-type accelerator, a DSP-type accelerator, and/or another accelerator. In this example, the computer-readable media <NUM> also includes an operating system <NUM> and application programming interface(s) <NUM> (APIs) configured to expose the functionality and the data of the device <NUM> to other devices. Additionally, the computer-readable media <NUM> includes one or more modules such as the server module <NUM>, the output module <NUM>, and the GUI presentation module <NUM>, although the number of illustrated modules is just an example, and the number may vary higher or lower. That is, functionality described herein in association with the illustrated modules may be performed by a fewer number of modules or a larger number of modules on one device or spread across multiple devices.

Claim 1:
A computer-implemented method for managing operation of a collaboration platform (<NUM>), comprising:
receiving collaboration object data that defines a collaboration object (<NUM>) of a first application (<NUM>(<NUM>)) in the collaboration platform, the collaboration object being a communication session, wherein the collaboration object data further defines a group definition (<NUM>) that associates a plurality of user accounts with the communication session;
receiving an instruction (<NUM>) that causes the collaboration platform to provide access to content of a data file (<NUM>) of a second application (<NUM>(<NUM>)) by exposing one or more functionalities (<NUM>(<NUM>)) of the second application to the communication session of the first application;
responsive to the instruction, associating the data file of the second application with the communication session of the first application;
based on the associating of the data file of the second application with the communication session of the first application, updating application configuration parameters (<NUM>) for the second application in association with the plurality of user accounts of the communication session; and
responsive to the updating of the second application configuration parameters, causing an instance of the second application (<NUM>) corresponding to one of the plurality of accounts to render a user interface element configured to provision access to the data file of the second application via a file system of the instance of the application, wherein the instance of the second application has no access to the data file via the file system prior to the associating of the data file with the communication session;
characterized in that:
the data file is a new data file generated as a result of the instruction being received through the first application during the communication session.