Generating collaboration documents for virtual conferences in communication platform

Abstract

Techniques are discussed herein for providing collaboration documents in association with a virtual conference on a communication platform. The user may communicate within the communication platform via text-based messages, which may include links, documents, videos, etc. A user may request a virtual conference with audio and / or video capabilities. In response to the request, a user within the communication channel may be invited to the virtual conference and collaboration document. Collaborative documents may implement messaging and sharing functionality that can be attributed to virtual space. The collaboration document may be populated with communications previously exchanged within the communication channel such that links, documents, videos, content, etc. that occur or are shared within the communication channel may be indicated within the collaboration document to provide the context of the virtual conference. Users may participate in audio and / or video communications within collaborative documents, as well as share links, documents, screens (i.e., screen shares), etc.

Description

[0001] Related Applications

[0002] This PCT international application claims priority to U.S. patent application No. 17 / 831,748, filed on June 3, 2022, entitled “GENERATING COLLABORATIVE DOCUMENTS FOR VIRTUAL MEETINGS IN A COMMUNICATION PLATFORM,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] Communication platforms are becoming increasingly popular in facilitating work-related communications, such as for project collaboration within a single organization and across two or more organizations. For example, a meeting can be arranged to discuss a specific project or part thereof. A meeting may include means for transmitting written communications (e.g., communication channels, direct message instances, etc.) and / or means for transmitting verbal communications (e.g., audio calls, video calls, etc.). Typically, during a meeting, users often share information via documents, links, screen sharing, etc., or more generally, share content. However, existing technologies for sharing information are typically confusing, limited in functionality, and may result in information loss. In addition, existing technologies are typically general, requiring users to upload content separately. These limitations may require users to use different means to chat, manage tasks, and collaborate in other ways. Therefore, additional features may facilitate collaboration between users. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The detailed description is made with reference to the accompanying drawings. In the drawings, the leftmost digit of a reference number identifies the drawing in which the reference number first appears. The use of the same reference number in different drawings indicates similar or identical components or features. The drawings are not drawn to scale.

[0005] Figure 1 An exemplary system for performing the techniques described herein is shown.

[0006] Figure 2 An exemplary user interface for requesting a virtual meeting as described herein is shown.

[0007] Figure 3 An exemplary user interface for inviting users to a virtual meeting as described herein is shown.

[0008] Figure 4 An exemplary user interface illustrating generation of a collaborative document in association with a virtual document as described herein is shown.

[0009] Figure 5An exemplary user interface illustrating generation of a collaborative document in association with a virtual document as described herein is shown.

[0010] Figure 6 An exemplary user interface illustrating generation of a collaborative document in association with a virtual document as described herein is shown.

[0011] Figure 7 An exemplary user interface illustrating generation of a collaborative document in association with a virtual document as described herein is shown.

[0012] Figure 8 An exemplary user interface illustrating generation of a collaborative document in association with a virtual document as described herein is shown.

[0013] Fig. 9 An exemplary user interface illustrating generation of a collaborative document in association with a virtual document as described herein is shown.

[0014] Fig.10 An exemplary user interface illustrating generation of a collaborative document in association with a virtual document as described herein is shown.

[0015] Fig.11 An exemplary user interface showing a collaboration document associated with a message in a communication channel as described herein is shown.

[0016] Fig.12 An exemplary process for generating a collaborative document in association with a virtual meeting as described herein is shown.

[0017] Fig.13 An exemplary process for acquiring a collaborative document as described herein is shown. DETAILED DESCRIPTION

[0018] The present application relates at least in part to providing collaborative documents in association with virtual meetings arranged on a communication platform. In some examples, the communication platform can be a group-based communication platform, a channel-based communication platform, a permission-based communication platform, a channel-based messaging platform and / or any other platform for facilitating communication between and among users, and the communication platform can enable users to exchange messages and / or other data via the communication platform. Initially, within the communication platform, users can communicate with each other via a communication channel by exchanging text-based messages. In some examples, these text-based messages can include links, documents (e.g., images, files, PDF), videos, etc. However, users may occasionally desire more immersive experiences and / or different forms of communication. For example, a user can arrange a virtual meeting with audio and / or video capabilities instead of sending and receiving text-based messages. In response to a request, users within a communication channel can be invited to collaborate with each other to a virtual meeting and a collaborative document. In some examples, collaborative documents implement messaging and sharing functionality that can be attributed to a virtual space. For example, a collaborative document can be filled with or otherwise indicate a communication previously exchanged within a communication channel. For example, links, documents, videos, content, etc. occurring or shared within a communication channel may be indicated within a collaborative document as a way to provide context for a virtual meeting. In doing so, within a collaborative document, users may participate in audio and / or video communications, as well as share links, documents, screens (i.e., screen sharing), etc. This increased form of communication may enhance the user experience and result in effective and efficient collaboration.

[0019] Generally speaking, a collaborative document can be associated with a document identifier (e.g., a virtual space identifier, a communication channel identifier, etc.), which is configured to implement messaging and sharing functionality within the collaborative document that can be attributed to the virtual space (e.g., a communication channel). That is, a collaborative document can be viewed as a virtual space (such as a communication channel) and includes functionality associated with a virtual space (such as a communication channel). Thus, within a collaborative document, users can communicate, exchange messages, share content, etc. In some examples, and as explained herein, a collaborative document can be created in association with a virtual meeting in which users communicate via audio and / or video. A collaborative document can be initiated for a real-time conversation that allows users to share and / or create files and screens that come alive with cursor tracking, drawing, and telepresence.

[0020] In some examples, a user can request a virtual meeting with audio and / or video. In some examples, a user can request a virtual meeting within a communication channel. For example, a first user can interact within a communication channel via a first user interface. The first user can request a virtual meeting and one or more additional users who will be invited to collaborate within the virtual meeting. In some examples, the communication platform can identify a second user account associated with the virtual meeting (e.g., a second user associated with the second user account is a member of the virtual space). In examples where a request is submitted via a communication channel, the communication platform can identify one or more members of the communication channel as users to be associated with the virtual meeting. That is, a user identifier associated with a communication channel can be additionally associated with the virtual meeting so that any member of the communication channel is added to the virtual meeting.

[0021] In addition, in some examples, a virtual meeting can be created independently of a communication channel, and the communication platform can identify the requesting user (e.g., the first user) as the user to be associated with the virtual meeting. That is, the first user can submit a request to create a virtual meeting independently of the communication channel (e.g., associated with the user account of the first user). In some examples, the identifier can be stored as metadata and can include a unique code (e.g., numbers, letters, symbols, and / or combinations thereof) that can be used to identify the virtual meeting. In other examples, a user identifier associated with a specific communication (e.g., a message) within a communication channel can be associated with the virtual meeting, so that users who have responded to the specific communication, reacted to the specific communication (e.g., like, dislike, emoticon, etc.), etc. are associated with the virtual meeting.

[0022] Moreover, in some examples, a virtual meeting can be requested from a sidebar of the user interface and / or from a dashboard of the communication platform. In some examples, the sidebar can include a portion of the user interface that includes a list of communication channels associated with a particular user account. For example, the sidebar can include a list of workspaces, communication channels, direct messaging instances, etc. associated with the user account. With respect to the sidebar, a user can request a virtual meeting and invite one or more other users to the virtual meeting.

[0023] In some examples, the virtual meeting can be a self-organized asynchronous meeting, such that the first user can generate the asynchronous meeting, and once the asynchronous meeting is generated, messages associated with the asynchronous meeting can be posted to the communication channel. Such an asynchronous meeting can be a "one-off" meeting or an initial meeting of a set of consecutive meetings. In some examples, the asynchronous meeting can be scheduled such that the first user can generate the asynchronous meeting.

[0024] In some examples, and as described above, a virtual meeting may be requested from a message posted within a communication channel, or in association with a message posted within a communication channel. These messages may include, but are not limited to, text (e.g., which may be editable), files (e.g., text, audio, video, applications, etc.), tasks to be completed, work orders to be resolved, events (e.g., pre-scheduled events, calendar invitations, calendar instances, etc.), messages previously transmitted via the communication platform, images, graphics, links to local objects, links to remote objects (e.g., third-party objects), etc. In some examples, the communication platform may identify an object based on user input from a creating user (e.g., a first user). For example, a first user may request to create a virtual meeting in association with a specific document shared within a communication channel. Here, based on user input, the communication platform may enable a virtual meeting to be created around a document. In some examples, this may allow users to collaborate around a document.

[0025] Regardless of the specific implementation, in response to receiving the request, the communication platform may identify one or more users, such as a first user and a second user, to be associated with the virtual meeting. As part of creating the virtual meeting, the communication platform may generate a collaborative document. The collaborative document may be attached to the virtual meeting or otherwise associated with the virtual meeting. As an example, as part of the request, the communication platform may identify one or more objects to be associated with the virtual meeting and the collaborative document.

[0026] As part of generating a collaborative document, the communication platform may cause an affordance associated with the virtual meeting and / or collaborative document to be presented via a user interface associated with each member of the virtual meeting. In some examples, the communication platform may modify the user interface corresponding to one or more users associated with the virtual meeting to include an affordance. For example, based on the identification of the second user account, the communication platform may cause a notification associated with the request to be presented on a second user interface associated with the second user, such as presented in association with an affordance corresponding to the virtual meeting (e.g., an identifier, an indicator, a selectable control, a user interface element, a graphical element, an icon, text, an image, etc.). In various examples, the affordance may include a selectable icon that, when selected by the corresponding user, causes the virtual meeting and collaborative document to be presented via a user interface associated with the user. For example, the second user may select affordances and / or notifications to access collaborative documents and join the virtual meeting. Here, the second user (as well as the first user) may indicate whether to enable their audio and / or video.

[0027] Additionally or alternatively, affordances of the virtual meeting may be presented in a sidebar of the user interface, respectively. Moreover, in some examples, affordances associated with the virtual meeting may be presented in association with the communication channel via which the virtual meeting was created (e.g., as a message within the communication channel).

[0028] In at least one example, the affordance displayed to the invited user can indicate the topic of discussion that will occur in the virtual meeting. For example, if a first user submits a request for a virtual meeting around an object (e.g., a document), the affordance displayed to a second user can indicate that the first user wants to discuss the object. Additionally, the communication platform can utilize objects as a way to import communications into a collaborative document. For example, if a collaborative document is created in association with an object, the communication platform can populate the collaborative document with communications about the object. This can be accomplished using identifiers and threads within a communication channel.

[0029] In some examples, in response to receiving an indication of a selection of an affordance associated with a virtual meeting, the communication platform may cause a collaborative document to be displayed on a corresponding user interface of the user. In some examples, the collaborative document includes communications, document affordances, links, and the like exchanged within a communication channel, and the like. For example, continuing with the above example, if a virtual meeting is created in association with an object, the object itself may be displayed as an affordance within the collaborative document. Additional documents, files, links, and the like presented or published within the communication channel may also be populated within the collaborative document. As described above, in some examples, a requesting user (e.g., a first user) may determine those documents, files, links, and the like that are populated within a collaborative document based on which object the collaborative document is created around.

[0030] Within a collaborative document, users can enable audio and / or video communications via their respective user interfaces. For example, a first user and / or a second user can enable audio and / or video communications via their respective user interfaces. In some examples, the first user and / or the second user can interact with one or more affordances to enable audio and / or video. In response to the input, the user interface can display the video of the first user and the second user, respectively, and / or can output the audio of the first user and / or the second user. For example, the second user (and other users) can indicate whether they wish to enable their audio and / or video.

[0031] As described above, collaborative documents can support messaging functionality (e.g., chat channels), message timing documentation (e.g., timestamps), file uploads, notifications (e.g., new messages posted, mentions or tags, etc.), mentions or tags functionality, event communication, workflow management and tracking, access permissions, and / or other functionality within a virtual meeting. In other words, the communication platform can treat collaborative documents as communication channels, so that the functionality of communication channels can be integrated into collaborative documents. In addition, collaborative documents can include the ability for users to share their screens, present documents, links, files, etc. Collaborative documents can also include message threads that allow users to communicate with each other within the collaborative document and separately from the communication channel. For example, a user can post messages, links, documents, etc. within a message thread of a collaborative document. After the collaborative document is terminated or closed, these messages can be tracked, recorded, and populated within the communication channel in association with the virtual meeting. A message thread can be a message associated with another message that is not posted to a communication channel, direct message, or other virtual space, but is instead maintained within an object associated with the original message. Thus, messages or communications occurring during a virtual meeting may be tracked and recorded within a collaborative document for access at a later time.

[0032] A collaborative document may include enablement representations of those users that are within the collaborative document or that have been invited to the collaborative document. For example, a first enablement representation of a first user may be presented in association with the collaborative document and / or a second enablement representation of a second user may be presented. Of course, a collaborative document may include more than two users, and in such examples, more than two enablement representations of these users may be presented separately. Generally speaking, these enablement representations may provide an indication of the users that are within the collaborative document. Additionally, other users may be invited even after the collaborative document is generated.

[0033] In some examples, a collaborative document or a user's user interface within a collaborative document may indicate the corresponding content that the user is viewing. For example, an affordance representation indicating which content the user is viewing and / or which content the user has viewed may be displayed. This may indicate the user's interaction and / or participation to others within the collaborative document. Additionally or alternatively, a collaborative document may indicate the position of the user's corresponding cursor. For example, if the first user is presenting content, the collaborative document may indicate the cursor position associated with the second user in association with the content being presented by the first user. In some examples, this may allow the first user to understand part of the content that the second user is currently viewing. However, the second user may be working on other content (e.g., documents, applications, etc.) that is separate from the content being presented or discussed by the first user. In such examples, the collaborative document may present affordance representations of the content that the first user is currently presenting and affordance representations of the content that the second user is currently viewing (e.g., based on the position of the second user's cursor). Of course, users may initially opt-in or authorize sharing of their screens and / or cursor tracking.

[0034] In some examples, a collaborative document may be associated with permissions that define which users of the communication platform can share content within the collaborative document, post messages to the collaborative document, and the like. In various examples, permissions may be defined or otherwise specified based on the parameters used to create the collaborative document. Additionally, permissions may include which users can invite other users to the collaborative document, and / or which users cannot invite users to the collaborative document. For example, a user associated with the creation of a collaborative document may include permissions to invite additional users, while a user receiving an invitation to join a virtual space may not include permissions to invite additional users. However, in some examples, all members of the collaborative document and / or the objects around which the collaborative document was created may be able to invite additional users, upload documents, and the like.

[0035] After the collaborative document ends, the communication that occurred in the collaborative document can be backfilled in the communication channel. For example, a message posted to a message thread can be displayed in the communication channel. In addition, an affordance representation of the collaborative document can be presented in the communication channel. For example, in the communication channel, an affordance representation indicating the occurrence of the collaborative document can be presented. In some examples, the communication channel can indicate the time when the collaborative document was created, the user of the collaborative document, etc. In some examples, the affordance representation is presented as a recent message in the communication channel to indicate in the communication channel that the collaborative document was created and a virtual meeting occurred. In addition, by posting messages in a message thread to a communication channel, the history of the message can be recorded and accessed later by the user. However, in some examples, the communication channel can be updated in real time or near real time so that the information conveyed in the virtual space is filled in the communication channel. In some examples, this can eliminate potential confusion about current communications in the communication channel.

[0036] After the virtual meeting is terminated, the collaborative document is stored and archived for later use and / or reference. For example, when the virtual meeting ends, the collaborative document still persists so that users do not lose the discussion, files, or links shared in the virtual meeting. In addition, at a later time, another virtual meeting around the same subject may occur, and in such instances, the collaborative document is accessed. Additional communications that occur are tracked and recorded, and updates to the collaborative document are made.

[0037] Although the virtual meeting and collaborative document are described as being performed by or implemented on the communication platform, the technology described herein can occur within a third-party application. For example, a collaborative document can be generated in association with a virtual meeting arrangement on a third-party application that is separate from the communication platform. In such instances, the collaborative document can be embedded in the virtual meeting so that users participating in the virtual meeting can send messages and / or exchange data, for example, via the collaborative document and within the third-party video conferencing application.

[0038] In addition, the technology herein is described in conjunction with generating a collaborative document in association with a virtual meeting, however, the collaborative document may exist previously and before the virtual meeting. In this case, the collaborative document may exist before or after the real-time conversation (e.g., the virtual meeting). In some examples, virtual meetings may be scheduled around the same collaborative document and at different times. For example, after collaborating within a virtual meeting at a first time instance, at a second time instance, another virtual meeting may occur. In an example, a collaborative document may be associated with each of these virtual meetings, for example, where a user wants to virtually conduct a meeting and discuss a collaborative document.

[0039] The technology described herein greatly enhances the practicality and functionality within the communication platform. As described above, conventional technology cannot fill collaborative documents with files, documents, links, etc. that occurred previously within a communication channel. In such examples, users of collaborative documents are left with very little context and / or history of previous communications within the communication channel. In some examples, this can reduce the number of instances or applications operated when collaborating on a project. For example, assuming that a collaborative document is filled with communications within a communication channel, a user may not have to switch back and forth between panes, user interfaces, etc. to access previous communications and / or shared content. In other words, when a user switches back and forth, the user loses the context associated with the collaborative document. Therefore, the prior art results in intermittent conversations and provides a poor user experience.

[0040] In addition, when the user switches back and forth, the user is required to switch back and forth between or interact with multiple display windows (e.g., third-party applications and applications and / or web browsers that provide communication platform functionality). Here, the prior art consumes computing resources by presenting multiple windows on the user's computing device. In addition, the prior art provides a user experience that is not optimal because the user needs to switch back and forth between computing resources. In addition, the sharing capabilities within the collaborative document can enhance the user experience and provide a way for the user to understand what other users are currently viewing. In some examples, due to the enhanced functionality provided by the collaborative document, the technology described herein can reduce the number of applications running on the user's computing device to monitor and / or manage projects. Therefore, the technology described herein can reduce the amount of computing resources utilized in collaboration.

[0041] The disclosure provides a comprehensive understanding of the principles of the structures, functions, devices and systems disclosed herein. One or more examples of the disclosure are shown in the accompanying drawings. It will be understood by those of ordinary skill in the art that the devices and / or systems specifically described herein and shown in the accompanying drawings are non-limiting embodiments. Features shown or described in conjunction with one embodiment may be combined with features of other embodiments. Such modifications and variations are intended to be included within the scope of the appended claims.

[0042] Figure 1 An exemplary environment 100 for performing the techniques described herein is shown. In at least one example, the environment 100 may be associated with a communication platform that may utilize a network-based computing system to enable users of the communication platform to exchange data. In at least one example, the communication platform may be "group-based" so that the platform and associated systems, communication channels, messages, collaborative documents, canvases, audio / video conversations, and / or other virtual spaces have security (which may be defined by permissions) to limit access to a defined user group. In some examples, such user groups may be defined by group identifiers that may be associated with public access credentials, domains, and the like. In some examples, the communication platform may be a hub that provides a secure and private virtual space to enable users to chat, meet, call, collaborate, transfer files or other data, or otherwise communicate with each other or among them. In some examples, each group may be associated with a workspace, so that users associated with the group may chat, meet, call, collaborate, transfer files or other data, or otherwise communicate with each other or among them in a secure and private virtual space. In some examples, members of the group and therefore the workspace may be associated with the same organization. In some examples, members of a group, and therefore a workspace, may be associated with different organizations (eg, entities with different organization identifiers).

[0043] In at least one example, environment 100 may include one or more server computing devices (or "servers") 102. In at least one example, server 102 may include one or more servers or other types of computing devices that may be embodied in any number of ways. For example, in the example of a server, functional components and data may be implemented on a single server, a cluster of servers, a server farm or data center, a cloud-hosted computing service, a cloud-hosted storage service, etc., although other computer architectures may additionally or alternatively be used.

[0044] In at least one example, the server 102 can communicate with the user computing device 104 via one or more networks 106. That is, the server 102 and the user computing device 104 can use the network 106 to transmit, receive and / or store data (e.g., content, information, etc.), as described herein. The user computing device 104 can be any suitable type of computing device, such as portable, semi-portable, semi-fixed or fixed. Some examples of the user computing device 104 can include a tablet computing device, a smart phone, a mobile communication device, a laptop, a netbook, a desktop computing device, a terminal computing device, a wearable computing device, an augmented reality device, an Internet of Things (IOT) device, or any other computing device capable of sending communications and performing functions according to the technology described herein. Although a single user computing device 104 is shown, in practice, the environment 100 can include multiple (e.g., tens, hundreds, thousands, millions) of user computing devices. In at least one example, among other aspects, a user computing device (such as a user computing device 104) can be operated by a user to access a communication service via a communication platform. A user can be an individual, a group of individuals, an employer, a business, an organization, etc.

[0045] The network 106 may include, but is not limited to, any type of network known in the art, such as a local area network (LAN) or a wide area network (WAN), the Internet, a wireless network, a cellular network, a local wireless network, Wi-Fi, and / or short-range wireless communication, Bluetooth Low Energy (BLE), Near Field Communication (NFC), a wired network, or any such network or any combination thereof. The components used for such communications may depend, at least in part, on the type of network, the selected environment, or both. The protocols used to communicate over the network 106 are well known and are not discussed in detail herein.

[0046] In at least one example, server 102 may include one or more processors 108 , computer-readable media 110 , one or more communication interfaces 112 , and input / output devices 114 .

[0047] In at least one example, each of the processors 108 can be a single processing unit or multiple processing units, and can include a single or multiple computing units or multiple processing cores. The processor 108 can be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units (CPUs), graphics processing units (GPUs), state machines, logic circuits, and / or any device that manipulates signals based on operating instructions. For example, the processor 108 can be one or more hardware processors and / or any suitable type of logic circuit that is specifically programmed or configured to perform the algorithms and processes described herein. The processor 108 can be configured to fetch and execute computer-readable instructions stored in a computer-readable medium that can program the processor to perform the functions described herein.

[0048] The computer-readable medium 110 may include volatile and non-volatile memory and / or removable and non-removable media implemented with any type of technology for storing data such as computer-readable instructions, data structures, program modules, or other data. The computer-readable medium 110 may include, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, optical storage, solid-state storage, tape, disk storage, RAID storage system, storage array, network attached storage, storage area network, cloud storage, or any other medium that can be used to store desired data and can be accessed by a computing device. Depending on the configuration of the server 102, the computer-readable medium 110 may be a type of computer-readable storage medium and / or may be a tangible non-transient medium to the extent that when referred to, non-transient computer-readable media exclude media such as energy, carrier signals, electromagnetic waves, and signals themselves.

[0049] The computer-readable medium 110 may be used to store any number of functional components that are executable by the processor 108. In many implementations, these functional components include instructions or programs that are executable by the processor 108 and that, when executed, specifically configure the processor 108 to perform the actions attributed above to the server 102. The functional components stored in the computer-readable medium may optionally include a messaging component 116, an audio / video component 118, a collaborative document component 120, an operating system 122, and a data repository 124.

[0050] In at least one example, the messaging component 116 can process messages between users. That is, in at least one example, the messaging component 116 can receive outgoing messages from the user computing device 104 and can send the message as an incoming message to the second user computing device 104. The message may include a direct message sent from the originating user to one or more specified users and / or a communication channel message sent from the originating user to one or more users associated with the communication channel via a communication channel. In addition, the message can be transmitted in association with a collaborative document, a canvas, or other collaborative space (such as a virtual meeting discussed herein). In at least one example, a virtual meeting may include a flexible canvas for planning, organizing, and sharing information collections between users. In at least one example, a collaborative document may be associated with a document identifier (e.g., a virtual space identifier, a communication channel identifier, etc.), and the document identifier is configured to implement messaging functionality that can be attributed to a virtual space (e.g., a communication channel) within the collaborative document. That is, the collaborative document can be viewed as a virtual space (such as a communication channel) and includes functionality associated with a virtual space (such as a communication channel). A virtual space or a communication channel may be a data route for exchanging data between and among systems and devices associated with a communication platform.

[0051] In at least one example, the messaging component 116 can establish communication routes between and among various user computing devices, thereby allowing user computing devices to communicate and share data between and among each other. In at least one example, the messaging component 116 can manage such communications and / or data sharing. In some examples, data associated with the virtual space (such as a collaborative document) can be presented via a user interface. In addition, metadata associated with each message transmitted via the virtual space, such as a timestamp associated with the message, a sending user identifier, a recipient user identifier, a conversation identifier, and / or a root object identifier (e.g., a conversation associated with a thread and / or a root object), etc. can be stored in association with the virtual space.

[0052] In various examples, messaging component 116 may receive a message transmitted in association with a virtual space (e.g., a direct message instance, a communication channel, a canvas, a collaborative document, etc.). In various examples, messaging component 116 may identify one or more users associated with the virtual space and may cause the message to be presented in association with the instance of the virtual space on the respective user computing devices 104. In various examples, messaging component 116 may identify the message as an update to the collaborative document and, based on the identified update, may cause a notification associated with the update to be presented in association with a sidebar of a user interface associated with one or more of the users associated with the collaborative document. For example, messaging component 116 may receive a message transmitted in association with a collaborative document from a first user account. In response to receiving the message (e.g., interaction data associated with an interaction of the first user with the virtual space), messaging component 116 may identify a second user associated with the collaborative document (e.g., another user who is a member of the virtual space). In some examples, messaging component 116 may cause a notification of the update to the collaborative document to be presented via a sidebar of a user interface associated with a second user account of the second user. In some examples, messaging component 116 can cause presentation of a notification in response to determining that a sidebar of a user interface associated with a second user account includes an affordance associated with a collaborative document. In such examples, the notification can be presented in association with an affordance associated with the collaborative document.

[0053] In various examples, messaging component 116 may be configured to identify mentions or tags associated with messages transmitted in association with a collaborative document. In at least one example, a mention or tag may include an @ mention (or other special characters) of a user identifier associated with a communication platform. A user identifier may include a username, a real name, or other unique identifier associated with a particular user. In response to identifying a mention or tag of a user identifier, messaging component 116 may cause a notification to be presented on a user interface associated with the user identifier, such as in a sidebar of a user interface associated with a particular user and / or in a collaborative document associated with a mention and reaction in association with an affordance associated with the collaborative document. That is, messaging component 116 may be configured to alert a particular user that they are mentioned in a collaborative document.

[0054] In at least one example, the audio / video component 118 can be configured to manage audio and / or video communications between and among users during a virtual meeting. In some examples, the audio and / or video communications can be associated with the virtual meeting. In at least one example, the virtual meeting can include a discrete identifier configured to uniquely identify the virtual meeting. In some examples, the audio / video component 118 can store user identifiers associated with user accounts of members of a particular virtual meeting, such as to identify users with appropriate permissions to access a particular virtual meeting.

[0055] In some examples, communications associated with the virtual meeting can be synchronous and / or asynchronous. That is, the virtual meeting can include a real-time audio and / or video conversation between a first user and a second user over a period of time, and after the first period of time, a third user associated with the conversation (e.g., as a member of the conversation) can contribute to the virtual meeting. The audio / video component 118 can be configured to store audio and / or video data associated with the virtual meeting, such as to enable users with appropriate permissions to listen to and / or view the audio and / or video data.

[0056] In some examples, the audio / video component 118 may be configured to generate a transcription of the virtual meeting, and the transcription may be stored in association with the audio and / or video data. The transcription may include a text representation of the audio and / or video data. In at least one example, the audio / video component 118 may generate the transcription using known speech recognition techniques. In some examples, the audio / video component 118 may generate the transcription simultaneously or substantially simultaneously with the virtual meeting. That is, in some examples, the audio / video component 118 may be configured to generate a text representation of the conversation while the conversation is ongoing. In some examples, the audio / video component 118 may generate the transcription after receiving an indication that the virtual meeting has been completed. The indication that the virtual meeting has been completed may include an indication that the host or administrator associated with it has stopped the virtual meeting, an indication that a threshold number of meeting attendees have closed the associated interface, etc. That is, the audio / video component 118 may identify the completion of the virtual meeting, and may generate a transcription associated with it based on the completion.

[0057] In at least one example, the audio / video component 118 can be configured to present a transcription in association with a collaborative document associated with the virtual meeting. For example, a first user can initiate a virtual meeting in association with a communication channel. The audio / video component 118 can process audio and / or video data between attendees of the virtual meeting, and can generate a transcription of the audio and / or video data. In response to generating the transcription, the audio / video component 118 can cause the transcription to be published or otherwise presented via the communication channel. In at least one example, the audio / video component 118 can render one or more segments of the transcription as selectable for comment, such as to enable members of the communication channel to comment on the virtual meeting or further contribute to the virtual meeting. In some examples, the audio / video component 118 can update the transcription based on the comment.

[0058] In at least one example, the audio / video component 118 can manage one or more virtual meetings in association with a collaborative document associated with a group (e.g., organization, team, etc.) administrator or command center. The group administrator or command center may be referred to herein as a virtual (and / or digital) headquarters associated with the group. In at least one example, the audio / video component 118 may be configured to coordinate with the messaging component 116 and / or other components of the server 102 to transmit communications in association with other collaborative documents associated with the virtual headquarters. That is, the messaging component 116 may transmit data (e.g., messages, images, drawings, files, etc.) associated with one or more communication channels, direct messaging instances, collaborative documents, canvases, etc. associated with the virtual headquarters. In some examples, the communication channels, direct messaging instances, collaborative documents, canvases, etc. may have one or more virtual meetings associated therewith that are managed by the audio / video component 118. That is, a virtual meeting associated with the virtual headquarters may be further associated with one or more other collaborative documents of the virtual headquarters or independent of one or more other collaborative documents of the virtual headquarters.

[0059] In at least one example, the collaborative document component 120 can manage collaborative documents associated with audio / video communications. For example, in at least one example, a user of the communication platform can request an audio / video communication as part of a virtual meeting, as described above. In some examples, a virtual meeting can be associated with a communication channel, an object shared within a communication channel, or can be generated outside of a specific communication channel. In response to receiving a request for a virtual meeting, the collaborative document component 120 can generate a collaborative document. As described above, a collaborative document can include a flexible canvas for planning, organizing, and sharing information collections between users. In at least one example, a collaborative document is configured to implement messaging functionality that can be attributed to a virtual space, and can include functionality associated with a virtual space. A collaborative document is attached to a virtual meeting or created in association with a virtual meeting to enable information to be shared between users of the virtual meeting.

[0060] In some examples, the collaborative document component 120 can manage collaborative documents created in association with a virtual meeting with audio / video communications. That is, the collaborative document component 120 can receive a request to associate a user with a virtual meeting, and the collaborative document component 120 can associate a user account associated with such a user with a group identifier associated with the collaborative document. For example, in response to receiving a request to create a virtual meeting with audio / video communications, the collaborative document component 120 can associate the user account of the user with the group identifier of the collaborative document. The collaborative document component 120 can also disassociate a user account and a group identifier, for example, when removing a user from a collaborative document.

[0061] In at least one example, the collaborative document component 120 can receive a request or other indication to create a collaborative document for collaboration between users, as described herein. In such examples, a user interface is generated via a user computing device of a user associated with the collaborative document. In addition, the collaborative document component 120 can integrate communications, documents, files, etc. that occur within a communication channel into the collaborative document. For example, the collaborative document can be populated with information shared between users in the communication channel in an organized manner. The collaborative document component 120 can also facilitate communications within the collaborative document, as well as content sharing (e.g., screen sharing), file uploads, link sharing, etc.

[0062] In at least one example, operating system 122 can manage processor 108 , computer-readable media 110 , hardware, software, etc. of server 102 .

[0063] The collaborative document component 120 may also determine user interactions indicating one or more interactions of one or more users with the collaborative document. For example, the collaborative document component 120 may determine such interactions from a user computing device, such as whether a user account is viewing the collaborative document, presenting content, screen sharing, typing a message within a thread, etc.

[0064] In at least one example, data repository 124 can be configured to store data that can be accessed, managed, and updated. In some examples, data repository 124 can be integrated with server 102, such as Figure 1 In other examples, the data repository 124 may be located remotely from the server 102 and may be accessible by the server 102 and / or a user device, such as a user computing device 104. The data repository 124 may include multiple databases that may include user / organization data 126 and / or collaborative document data 128. Additional or alternative data may be stored in the data repository and / or one or more other data repositories.

[0065] In at least one example, user / organization data 126 may include data associated with a user of a communication platform. In at least one example, user / organization data 126 may store data in a user profile (which may also be referred to as a "user account"), which may store data associated with a user, including, but not limited to: one or more user identifiers associated with multiple different organizations or entities with which the user is associated, one or more communication channel identifiers associated with communication channels to which the user has been authorized to access, one or more group identifiers of groups (or organizations, teams, entities, etc.) with which the user is associated, an indication of whether the user is the owner or manager of any communication channel, an indication of whether the user has any communication channel constraints, multiple messages, multiple emoticons, multiple conversations, multiple conversation topics, avatars, email addresses, real names (e.g., John Doe), usernames (e.g., j doe), passwords, time zones, statuses, tokens, etc.

[0066] In at least one example, user / organization data 126 may include permission data associated with permissions for individual users of the communication platform. In some examples, permissions may be set automatically or by an administrator of the communication platform, an employer, an enterprise, an organization, or other entities utilizing the communication platform, a team leader, a group leader, or other entities utilizing the communication platform to communicate with team members, group members, etc., individual users, etc. The permissions associated with individual users may be mapped to an account or profile within user / organization data 126, or otherwise associated with an account or profile. In some examples, permissions may indicate which users may communicate directly with other users, which channels are permitted for users to access, constraints on individual channels, which workspaces are permitted for users to access, constraints on individual workspaces, etc. In at least one example, permissions may support the communication platform by maintaining security for limiting access to a defined group of users. In some examples, such users may be defined by public access credentials, group identifiers, etc., as described above.

[0067] In at least one example, user / organization data 126 may include data associated with one or more organizations of the communication platform. In at least one example, user / organization data 126 may store data in an organization profile, which may store data associated with the organization, including, but not limited to: one or more user identifiers associated with the organization, one or more virtual space identifiers associated with the organization (e.g., workspace identifiers, communication channel identifiers, direct message instance identifiers, collaborative document identifiers, canvas identifiers, audio / video conversation identifiers, etc.), an organization identifier associated with the organization, one or more organization identifiers associated with other organizations authorized to communicate with the organization, and the like.

[0068] In some examples, user / organization data 126 may include permissions for users of the communication platform. In some examples, permissions may be automatically set or set by an administrator of the communication platform, an employer, an enterprise, an organization, or other entities utilizing the communication platform, a team leader, a group leader, or other entities utilizing the communication platform to communicate with team members, group members, etc., a separate user, etc. In some examples, permissions associated with separate users may be mapped to a profile or account associated with user / organization data 126, or otherwise associated with a profile or account. In some examples, permissions may indicate which users may communicate directly with other users, which channels are permitted for users to access, constraints on separate channels, which workspaces are permitted for users to access, constraints on separate workspaces, etc. In at least one example, permissions may support the communication platform by maintaining security for limiting access to a defined user group. In some examples, such users may be limited by public access credentials, group identifiers, etc., as described above.

[0069] In some examples, user / organization data 126 may store data associated with permissions for groups associated with a communication platform. In some examples, permissions may be set automatically or by an administrator of the communication platform, an employer, a business, an organization, or other entities utilizing the communication platform, a team leader, a group leader, or other entities utilizing the communication platform to communicate with team members, group members, etc., a separate user, etc. In some examples, permissions associated with a group may be mapped to data associated with the group, or otherwise associated with the data. In some examples, permissions may indicate constraints on separate groups, constraints on channels associated with separate groups, constraints on users associated with separate groups, etc. In at least one example, permissions may support a communication platform by maintaining security for limiting access to a defined group of users. In some examples, such groups may be defined by public access credentials, group identifiers, etc., as described above.

[0070] In some examples, user / organization data 126 may store data associated with permissions for individual communication channels. In some examples, permissions may be set automatically or by an administrator of the communication platform, an employer, a business, an organization, or other entity utilizing the communication platform, a team leader, a group leader, or other entity utilizing the communication platform to communicate with team members, group members, etc., an individual user, etc. In some examples, permissions associated with a channel may be mapped to data associated with the communication channel, or otherwise associated with the data. In some examples, permissions may indicate constraints on individual channels, constraints on users associated with individual channels, etc.

[0071] In at least one example, individual users can be associated with specific permissions, users with specific user types and / or roles (e.g., admin users, reviewers, moderators, etc.) can be associated with specific permissions, objects (e.g., messages or others) can be associated with specific permissions, virtual spaces can be associated with specific permissions, etc. That is, the user / organization data 126 can store various permissions for various components of the environment 100. Permissions can also be associated with collaborative documents, such as which users can edit, view, etc. the collaborative document, share content within the collaborative document, post messages within the collaborative document, etc. In at least one example, the collaborative document component 120 can update the collaborative document instance presented to the user of the collaborative document so that the data associated with the collaborative document is updated in real time or near real time.

[0072] In at least one example, the collaborative document data 128 may include data associated with one or more collaborative documents associated with the communication platform. The collaborative document data 128 may include text data, audio data, video data, images, files, and / or any other type of data configured to be transmitted in association with a collaborative document or a virtual meeting associated with a collaborative document. Non-limiting examples of collaborative documents include workspaces, communication channels, direct messaging instances, canvases, and audio and / or video conversations. In at least one example, the collaborative document data 128 may store data associated with separate collaborative documents, such as based on discrete identifiers associated with each collaborative document. In some examples, a first collaborative document may be associated with a second collaborative document. In such examples, first collaborative document data associated with a first collaborative document may be stored in association with a second collaborative document. For example, data associated with a collaborative document generated in association with a communication channel may be stored in association with the communication channel. As another example, data associated with an audio and / or video conversation conducted in association with a communication channel may be stored in association with the communication channel.

[0073] As described above, each collaborative document of the communication platform may be assigned a discrete identifier that uniquely identifies the virtual space. In some examples, the collaborative document identifier associated with the virtual meeting may include a physical address in the collaborative document data 128 where data related to the collaborative document is stored. A collaborative document may be "public," which may allow any user within an organization (e.g., associated with an organization identifier) ​​to join and participate in data sharing through the collaborative document, or a collaborative document may be "private," which may restrict data communication in the collaborative document to certain users or users with appropriate viewing permissions.

[0074] In some examples, the data repository 124 can be divided into discrete data items (e.g., data shards) that can be accessed and managed separately. Data shards can simplify many technical tasks, such as data retention, expansion (e.g., detecting that message content includes links, crawling metadata for links, and determining a unified overview of metadata), and integration setup. In some examples, data shards can be associated with organizations, groups (e.g., workspaces), communication channels, users, etc.

[0075] In some examples, separate organizations can be associated with database shards within the data repository 124 that store data associated with a particular organization identity. For example, a database shard can store electronic communication data associated with members of a particular organization, which enables members of the particular organization to communicate and exchange data with other members of the same organization in real time or near real time. In examples, the organization itself can be the owner of the database shard and have control over where and how the relevant data is stored. In some examples, a database shard can store data associated with two or more organizations (e.g., such as in a shared virtual space).

[0076] In some examples, individual groups may be associated with database shards within the data repository 124 that store data associated with a particular group identity (e.g., a workspace). For example, a database shard may store electronic communication data associated with members of a particular group, which enables members of the particular group to communicate and exchange data with other members of the same group in real time or near real time. In an example, the group itself may be the owner of the database shard and have control over where and how the relevant data is stored.

[0077] In some examples, a virtual space may be associated with a database shard within data repository 124 that stores data associated with a particular virtual space identity. For example, a database shard may store electronic communication data associated with a virtual space, which enables members of a particular virtual space to communicate and exchange data with other members of the same virtual space in real time or near real time. As described above, communications via the virtual space may be synchronous and / or asynchronous. In at least one example, a group or organization may be the owner of a database shard and may control where and how the associated data is stored.

[0078] In some examples, individual users may be associated with a database shard within data repository 124 that stores data associated with a particular user account. For example, a database shard may store electronic communication data associated with an individual user, which enables the user to communicate and exchange data with other users of a communication platform in real time or near real time. In some examples, the user themselves may be the owner of the database shard and have control over where and how the relevant data is stored.

[0079] The communication interface 112 may include one or more interfaces and hardware components for enabling communication with various other devices (e.g., user computing device 104), such as through network 106 or directly. In some examples, the communication interface 112 may facilitate communication via Websockets, an application programming interface (API) (e.g., using API calls), Hypertext Transfer Protocol (HTTP), etc.

[0080] The server 102 may also be equipped with various input / output devices 114 (eg, I / O devices). The I / O devices 114 may include a display, various user interface controls (eg, buttons, joysticks, keyboards, mice, touch screens, etc.), audio speakers, connection ports, etc.

[0081] In at least one example, user computing device 104 may include one or more processors 130 , computer-readable media 132 , one or more communication interfaces 134 , and input / output devices 136 .

[0082] In at least one example, each of processors 130 may be a single processing unit or multiple processing units and may include a single or multiple computing units or multiple processing cores. Processor 130 may include any type of processor described above with reference to processor 108 and may be the same as or different from processor 108.

[0083] Computer readable media 132 may include any type of computer readable media 132 described above with reference to computer readable media 110, and may be the same as or different from computer readable media 110. Functional components stored in the computer readable media may optionally include at least one application 138 and an operating system 140.

[0084] In at least one example, application 138 may be a mobile application, a web application, or a desktop application, which may be provided by the communication platform or it may be another dedicated application. In some examples, a separate user computing device associated with environment 100 may have an instance or versioned instance of application 138, which may be downloaded from an application store, accessible via the Internet, or otherwise executable by processor 130 to perform operations as described herein. That is, application 138 may be an access point that enables user computing device 104 to interact with server 102 to access and / or use communication services available via the communication platform. In at least one example, application 138 may facilitate data exchange between and among various other user computing devices, for example, via server 102. In at least one example, application 138 may present a user interface, as described herein. In at least one example, a user may interact with the user interface via touch input, keyboard input, mouse input, voice input, or any other type of input.

[0085] Figure 1 A non-limiting example of user interface 142 is shown in FIG. Figure 1As shown, user interface 142 can present data associated with one or more communication channels (which may include one or more workspaces). That is, in some examples, user interface 142 can integrate data from multiple workspaces into a single user interface so that a user (e.g., of user computing device 104) can access data associated with multiple workspaces associated with it and / or interact with it and / or otherwise communicate with other users associated with multiple workspaces. In some examples, user interface 142 may include a first area 144 or pane, which includes indicators (e.g., user interface elements or objects) associated with a workspace associated with a user (e.g., a user's account) and / or indicators (e.g., user interface elements, affordances, objects, etc.) representing data associated with a workspace associated with a user (e.g., a user's account). In at least one example, first area 144 may represent a sidebar of user interface 142.

[0086] In at least one example, the user interface 142 may include a second area 146 or pane that may be associated with a data feed (or "feed") indicating messages posted to one or more communication channels used to facilitate communication and / or actions taken with respect to one or more communication channels, as described herein. In at least one example, the data associated with the second area 146 may be associated with the same or different workspaces. That is, in some examples, the second area 146 may present data associated with the same or different workspaces via an integrated feed. In some examples, the data may be organized and / or sorted by workspace, time (e.g., the time when the associated data was posted or the associated action was otherwise performed), action type, communication channel, user, and the like. In some examples, such data may be associated with an indication of which user (e.g., a member of a communication channel) posted the message and / or performed the action. In examples where the second area 146 presents data associated with multiple workspaces, at least some of the data may be associated with an indication of which workspace the data is associated with. Reference below Figure 2 Additional details associated with user interface 142 and second area 146 are described.

[0087] User interface 142 is shown as displaying an affordance 148 for generating or otherwise creating a virtual meeting and collaborative document associated with a communication channel (e.g., channel A) that the user is accessing. In some examples, affordance 148 is displayed after the user's cursor (e.g., input / output device 136) hovers over a particular area of ​​a message (or other object) within the communication channel or over the message itself. Affordance 148 allows the user to create or request the creation of a collaborative document associated with the virtual meeting. For example, Figure 1In the user interface 142 shown in , users of a communication channel (e.g., channel A) may be communicating via text-based messages. However, in some examples, users may desire to interact via audio and / or video. Here, in order to create a virtual meeting with audio and / or video capabilities, one of these users can request a virtual meeting via selecting an affordance 148. As will be explained herein, a virtual meeting can be requested from different messages, links, and other objects posted within a communication channel. An object can include a text document, an image, a video, or any other file or data item. In addition, as will be explained herein, in response to requesting a virtual meeting, a collaborative document is generated and a coworking space is provided, in which users can participate in audio and / or video communications in addition to or in lieu of text-based communications. In addition, within a virtual meeting, users can share documents, content, links, and the like.

[0088] In at least one example, operating system 140 can manage processor 130 , computer-readable media 132 , hardware, software, etc. of server 102 .

[0089] The communication interface 134 may include one or more interfaces and hardware components for enabling communication with various other devices (e.g., user computing device 104), such as through network 106 or directly. In some examples, the communication interface 134 may facilitate communication via Websockets, APIs (e.g., using API calls), HTTP, etc.

[0090] The user computing device 104 may also be equipped with various input / output devices 136 (e.g., I / O devices). Such I / O devices 136 may include a display, various user interface controls (e.g., buttons, joysticks, keyboards, mice, touch screens, etc.), audio speakers, connection ports, etc.

[0091] Although the techniques described herein are described as being performed by messaging component 116, audio / video component 118, collaborative document component 120, and application 138, the techniques described herein may be performed by any other component or combination of components that may be associated with server 102, user computing device 104, or a combination thereof.

[0092] Figure 2 Additional details associated with presenting data associated with a communication channel, virtual space, or collaborative document are shown, as described above with reference to the user interface 142. Figure 1 as described.

[0093] As described above, in at least one example, user interface 142 may include a first area 144 or pane that includes an indicator (e.g., a user interface element or object) of a workspace associated with a user (e.g., a user's account) and / or an indicator (e.g., a user interface element or object) representing a virtual space associated with a workspace associated with a user (e.g., a user's account). In at least one example, first area 144 may represent a sidebar of user interface 142.

[0094] In at least one example, the first area 144 may include one or more sub-sections or sub-panes, and the one or more sub-sections or sub-panes may represent different virtual spaces. For example, the first sub-section 200 may include an indicator representing a virtual space that can aggregate data associated with multiple virtual spaces of which the user is a member. In at least one example, each virtual space may be associated with an indicator in the first sub-section 200. In some examples, the indicator may be associated with an actuation mechanism (e.g., an affordance) such that when actuated, it may cause the application 138 to present data associated with the corresponding virtual space via the second area 146. In at least one example, the virtual space may be associated with all unread data, and all unread data is associated with each of the workspaces associated with the user. That is, in some examples, if the user requests access to a virtual space associated with "unread", all data that the user has not yet read (e.g., viewed) may be presented in the second area 146, for example, in a feed. In such examples, different types of events and / or actions that may be associated with different virtual spaces may be presented via the same feed. In some examples, such data may be organized and / or sorted by associated virtual space (e.g., the virtual space via which communications are transmitted), time, action type, user, etc. In some examples, such data may be associated with an indication of which user (e.g., a member of the associated virtual space) posted a message and / or performed an action.

[0095] In some examples, virtual spaces can be associated with events and / or actions of the same type. For example, a "thread" can be associated with messages, files, etc. posted in a thread to messages posted in a virtual space, and "mentions and reactions" (e.g., "M&R (mentions & reactions)") can be associated with messages or threads in which a user (e.g., user F) has been mentioned (e.g., via a tag) or another user has reacted to a message or thread posted by the user (e.g., via an emoticon, reaction, etc.). That is, in some examples, events and / or actions of the same type that can be associated with different virtual spaces can be presented via the same feed. As with the "unread" virtual space, data associated with such a virtual space can be organized and / or sorted by virtual space, time, action type, user, etc.

[0096] In some examples, the virtual space can be associated with facilitating communications between the user and other users of the communication platform. For example, "connect" can be associated with enabling the user to generate an invitation to communicate with one or more other users. In at least one example, in response to receiving an indication of selection of the "connect" indicator, the communication platform can cause a connection interface to be presented in second area 146.

[0097] In some examples, a virtual space can be associated with a group (e.g., organization, team, etc.) headquarters (e.g., an administrator or command center). In at least one example, a group headquarters can include a virtual or digital headquarters for administrator or command functions associated with a group of users. For example, "HQ" can be associated with an interface that includes a list of indicators associated with virtual spaces that are configured to enable associated members to communicate. In at least one example, a user can associate one or more virtual spaces with the "HQ" virtual space, such as via a drag and drop operation. That is, a user can determine the relevant virtual spaces to be associated with the virtual or digital headquarters, such as to associate virtual spaces that are important to the user with it.

[0098] Although not shown, in some examples, the virtual space can be associated with one or more boards or documents associated with the user. In at least one example, if the user requests access to a virtual space associated with one or more documents associated with the user, the one or more documents can be presented via the user interface 142 (e.g., in the second area 146). In at least one example, as described herein, a document can be associated with an individual (e.g., a user's private document), associated with a group of users (e.g., a collaborative document), and / or associated with one or more communication channels (e.g., members of a communication channel are given access permissions to the document), such as to enable users of the communication platform to create data associated with such documents, interact with such documents, and / or view data associated with such documents.

[0099] In addition, although not shown, in some examples, the virtual space may be associated with one or more canvases associated with the user. In at least one example, the canvas may include a flexible canvas for planning, organizing and sharing information collections between users. That is, the canvas may be configured to be accessed and / or modified by two or more users with appropriate permissions. In at least one example, the canvas may be configured to enable sharing of text, images, videos, GIFs, drawings (e.g., drawings generated by users via a canvas interface), game content (e.g., users synchronously or asynchronously manipulate game controls), etc. In at least one example, modifications to the canvas may include adding, deleting, and / or modifying previously shared (e.g., transmitted, presented) data. In some examples, the content associated with the canvas may be shareable via another virtual space, so that the data associated with the canvas can be accessed and / or rendered by members of the virtual space to enable interaction by members of the virtual space.

[0100] In some examples, if the first sub-section 200 includes a user interface element actuated by a user that represents a virtual space associated with audio and / or video communications (e.g., conversations, multimedia clips (e.g., videos, audio files, dynamics, etc.), audio and / or video data associated with the user can be presented via the second area 146, which audio and / or video data can be associated with different audio and / or video conversations, multimedia clips, dynamics, etc. In some examples, such audio and / or video data can be presented via a feed. For purposes of the present discussion, the audio and / or video data can correspond to audio and / or video content provided by a user associated with the communication platform.

[0101] The first area 144 of the user interface 142 may also include a second subsection 202 or subpane, which is a personalized subsection associated with a personal document associated with the user account. In at least one example, the user may select a personal document to be associated with the second subsection 202, such as by dragging and dropping, setting a pin, or otherwise associating the selected personal document into the second subsection 202. As described above, a personal document may include a collaborative document of which the user is the only member. For example, a personal document may include a to-do list, a document with saved items, etc.

[0102] In at least one example, the first area 144 of the user interface 142 may include a third sub-section 204 or sub-pane, which includes an indicator representing a communication channel. In some examples, the communication channel may include a public channel, a private channel, a shared channel (e.g., between a group or organization), a single workspace channel, a cross-workspace channel, a combination of the foregoing channels, and the like. In some examples, the represented communication channel may be associated with a single workspace. In some examples, the represented communication channel may be associated with different workspaces (e.g., cross-workspaces). In at least one example, if the communication channel is a cross-workspace (e.g., associated with different workspaces), the user may be associated with both workspaces, or may be associated with only one of the workspaces. In some examples, the represented communication channel may be associated with a combination of a communication channel associated with a single workspace and a communication channel associated with different workspaces.

[0103] In some examples, the third subsection 204 may depict all communication channels or a subset of all communication channels to which the user has access permissions (e.g., as determined by the permissions data). In such examples, the communication channels may be arranged alphabetically, based on the most recent interaction, based on the frequency of interaction, based on the type of communication channel (e.g., public, private, shared, cross-workspace, etc.), based on the workspace, in a user-specified section, etc. In some examples, the third subsection 204 may depict all communication channels or a subset of all communication channels to which the user is a member, and the user may interact with the user interface 142 to browse or view other communication channels to which the user is not a member but which are not currently displayed in the third subsection 204. In some examples, different types of communication channels (e.g., public, private, shared, cross-workspace, etc.) may be in different sections of the third subsection 204, or may have their own sub-areas or sub-panes in the user interface 142. In some examples, communication channels associated with different workspaces may be in different sections of the third subsection 204, or may have their own areas or panes in the user interface 142.

[0104] In at least one example, the second area 146 may include a fourth sub-section 206 or sub-pane that may include an indicator representing communications with an individual user or multiple specified users (e.g., rather than all members of an organization or a subset thereof). Such communications may be referred to as "direct messages." That is, the fourth sub-section 206 or sub-pane may include an indicator representing a virtual space associated with private messages between one or more users.

[0105] In at least one example, the second area 146 may include a fifth sub-segment 208 or sub-pane, which may include an indicator indicating the start of a virtual meeting with audio and / or video capabilities. For example, the fifth sub-segment 208 may include an affordance 210 in which a user may toggle back and forth to request a virtual meeting. In response, the user interface 142 may cause a collaborative document to be presented within the second area 146, and the user may utilize audio and / or video communications. In addition, as will be explained herein, as part of requesting a collaborative document, one or more users associated with the collaborative document may be identified. In addition, as described above, a collaborative document may also be requested via affordance 148 presented within the second area 146. In some examples, and as will be explained herein, affordance 148 may be selected to create a virtual meeting around a specific message within a communication channel, while affordance 210 may be selected to create a virtual meeting disassociated from the communication channel.

[0106] That is, selecting affordance 210 may request a collaborative document independently of an existing communication channel in the communication platform. In such examples, the request may be received in association with a user account of the requesting user, and the requesting user may be the sole member of the collaborative document until the collaborative document is shared with one or more additional users, or until other users are invited to the collaborative document. In some examples, the request may be received in association with a virtual conference that includes audio and / or video communications.

[0107] As described above, in at least one example, user interface 142 may include a second region 146 or pane associated with a feed indicating messages posted to and / or actions taken with respect to a virtual space used to facilitate communications (e.g., a virtual space associated with direct message communications, a virtual space associated with communication channel communications, a virtual space associated with collaborative document communications (e.g., via messaging or a chat interface within a collaborative document), a virtual space associated with audio and / or video communications, etc.). Figure 2 , a user (e.g., user F) may interact with user interface 142 to view data associated with the virtual space and / or request collaborative documents via affordance 148.

[0108] In some examples, collaborative documents may be requested from messages (or other objects) posted within a communication channel, or in association with messages (or other objects) posted within a communication channel. These messages may include, but are not limited to, text (e.g., which may be editable), files (e.g., text, audio, video, applications, etc.), tasks to be completed, work orders to be resolved, events (e.g., pre-scheduled events, calendar invitations, calendar instances, etc.), messages previously transmitted via the communication platform, images, graphics, links to local objects, links to remote objects (e.g., third-party objects), etc. As an example, as part of the request, the communication platform may identify one or more objects to be associated with the virtual meeting. In some examples, the communication platform may identify the object based on user input from the creating user (e.g., the first user). For example, the first user may request to create a virtual meeting in association with a specific document shared within the communication channel. Here, based on user input, the communication platform may enable the creation of virtual meetings and collaborative documents around documents. In some examples, this may allow users to form document-centric meetings.

[0109] More specifically, in Figure 2 , an indicator 212 of a message is shown as being presented in the second area 146. Indicator 212 may be generated by a user (e.g., user F) in response to other communications within a communication channel (e.g., channel A). As shown, other users may have replied to the message, which is represented by an indicator 214 (e.g., a user interface element, an object, etc.) associated with the communication channel (e.g., #channelA). Other users may additionally or alternatively react to the message by emoticons, etc. In addition, the user may have uploaded a document represented by affordance 216. For the purposes of this discussion, a "message" may refer to any electronically generated digital object provided by a user using a user computing device 104 and configured for display in a communication channel as described herein and / or other virtual spaces for facilitating communication (e.g., a virtual space associated with direct messaging, etc.). A message may include any text, image, video, audio, or combination thereof provided by a user (using a user computing device). For example, a user may provide a message that includes text within the message as well as images and videos as message content. In such examples, text, images, and videos will include a message. Each message sent or published to a communication channel of the communication platform may include metadata including a sending user identifier, a message identifier, message content, a group identifier, a communication channel identifier, etc. In at least one example, each of the foregoing identifiers may include American Standard Code for Information Interchange (ASCII) text, a pointer, a memory address, etc.

[0110] In some examples, a user may comment on a message in a "thread." A thread may be a message associated with another message that is not posted to a communication channel but instead maintained within an object associated with the original message. Messages and / or threads may be associated with files, emoticons, applications, etc. For example, regarding indicator 214 of a message, there are three replies to a message of user F, and these replies are a "thread" of messages for a user (e.g., user F).

[0111] A communication channel or other virtual space may be associated with data and / or content that is different from or associated with a message. For example, non-limiting examples of additional data that may be presented via the second area 146 of the user interface 142 include collaborative documents (e.g., documents that may be collaboratively edited in real time or near real time, etc.), audio and / or video data associated with a conversation, members added to and / or removed from a communication channel, files (e.g., file attachments uploaded and / or removed from a communication channel), applications added to and / or removed from a communication channel, publications added to and / or removed from a communication channel (data that may be collaboratively edited in near real time by one or more members of a communication channel), descriptions added to, modified and / or removed from a communication channel, modifications to properties of a communication channel, etc.

[0112] In some examples, the second area 146 may include a feed associated with a single virtual meeting and / or a single collaborative document. In such examples, data associated with the collaborative document may be presented via a feed. In at least one example, the data associated with the collaborative document may be viewable by at least some of a group of users associated with the same group identifier, such as users with appropriate permissions to access the collaborative document. In some examples, for members of a collaborative document, the content of the collaborative document (e.g., messaging communications) may be displayed to each member of the collaborative document. For example, a common collection of group-based messaging communications may be displayed to each member of the collaborative document, so that the content of the collaborative document (e.g., messaging communications) may not vary according to the members of the collaborative document. In some examples, the data associated with the collaborative document may appear differently for different users (e.g., based on personal configuration, group membership, etc.).

[0113] In at least one example, the format of a collaborative document may appear differently for different users. In some examples, the format of a collaborative document may appear differently based on which workspace a user is currently interacting with or has recently interacted with. In some examples, the format of a separate virtual space may appear differently for different users (e.g., based on personal configuration, group membership, etc.).

[0114] As will be explained herein, in response to requesting a virtual meeting and generating a collaborative document, an invitation may be sent to other users. In some examples, the invitation may indicate an object (e.g., a message) in which the virtual meeting is created to provide the context of the virtual meeting and indicate to other users the reason for arranging the virtual meeting.

[0115] In at least one example, user interface 142 may include a search mechanism 218 where a user may enter a search term and server 102 may perform a search associated with the communication platform. In some examples, the search may be performed across each workspace associated with the user, or the search may be constrained to a particular workspace based on user specifications.

[0116] The user interface 142 is a non-limiting example of a user interface that may be presented via the user computing device 104 (e.g., by the application 138). In some examples, the application 138 may receive data from the messaging component 116, the audio / video component 118, and / or the collaborative document component 120, and the application 138 may generate and present the user interface 142 based on the data. In other examples, the application 138 may receive data from the messaging component 116 and / or the audio / video component 118, and receive instructions from the messaging component 116, the audio / video component 118, and / or the collaborative document component 120 for generating the user interface 142. In such examples, the application 138 may present the user interface 142 based on the instructions. Additional or alternative data may be presented via the user interface, and additional or alternative configurations are envisioned.

[0117] Figure 3 An exemplary user interface 142 for inviting a user to a virtual meeting is shown. For example, user interface 142 is shown as displaying window 300. In some examples, window 300 may be displayed after a user selects affordance 148 or affordance 210. For example, in response to requesting a virtual meeting, user interface 142 may display window 300.

[0118] Window 300 includes a field 302 for a user to enter the name of a user to be invited to the virtual meeting or to search for a user to be invited to the virtual meeting. In some examples, window 300 may present a list of users who are members of a communication channel (e.g., channel A) to increase the ease of inviting users to the virtual meeting. The user may select an affordance of a user to invite the user to the virtual meeting individually.

[0119] like Figure 3As further shown in FIG. 2 , the affordance 210 may have been actuated (e.g., switched on) to indicate that the user is requesting a virtual meeting. In response, the fifth sub-segment 208 may indicate the users within the virtual meeting (or the users who have been invited to the virtual meeting). Additionally or alternatively, the fifth sub-segment 208 may include affordances for enabling audio, sharing content, messaging, etc.

[0120] Figure 4 An exemplary user interface 142 is shown showing a collaborative document 400 generated in response to a virtual meeting being scheduled. As described above, the collaborative document 400 is presented via the user interface 142 and includes functionality associated with a virtual space, such as a communication channel in which users can collaborate. In some examples, the collaborative document 400 can be a virtual space, board, canvas, page, etc. for collaborative communication and / or data organization within a communication platform. In at least one example, the collaborative document 400 can support editable text and / or objects that can be sorted, added, deleted, modified, etc. In some examples, the collaborative document 400 can be associated with permissions that define which users of the communication platform can view and / or edit the document.

[0121] The collaborative document 400 includes a first indication of a user 402 and a second indication of a file 404. The users may be those users invited to collaborate within the collaborative document 400, and the files may be those files shared within a communication channel. For example, the collaborative document 400 may be created from a communication channel or certain communications (e.g., messages) within the communication channel. Files shared (e.g., uploaded, posted, etc.) into the communication channel may be populated within the collaborative document 400. This allows users within the collaborative document 400 to easily access previously shared files within the communication channel, and may avoid users switching back and forth between windows to access files.

[0122] In some examples, collaborative document 400 may include first area 406 and second area 408. First area 406 may be arranged vertically above second area 408. A user may share content within collaborative document 400 by selecting to present affordance 410. In some examples, present affordance 410 allows users to share their screens (e.g., share screens) respectively. In some examples, upon selecting to present affordance 410, content may be presented within second area 408. Accordingly, icons 412 of users (and other users in collaborative document 400) may be presented vertically above, vertically below, next to, etc., second area 408.

[0123] The second area 408 or a portion of the collaborative document 400 may represent an area where a file is presented, a screen is shared, a video stream is presented, etc. For example, in Figure 34, an icon 412 associated with a user (e.g., user F) is displayed in the second area 408. In some examples, the icon 412 is displayed after the first indication 402 is selected. For example, the user can select the first indication 402 to view those users who are collaborating within the collaborative document 400. Here, the user (e.g., user F) is shown as the only user within the collaborative document 400, however, as other users join, the collaborative document 400 (and the icon) can be updated.

[0124] Collaborative document 400 may also include one or more affordances for interacting within collaborative document 400. For example, audio affordance 414 allows a user to mute or unmute themselves. Video affordance 416 allows a user to turn their camera on and off. In an example where a user turns on their camera, second area 408 may present a live stream (e.g., feed) of the user's image / video data. Conference affordance 418 (which may be similar to affordance 210) allows a user to terminate (e.g., leave) collaborative document 400. For example, in Figure 4 , conference affordance 418 is shown as being switched on, whereby the user is participating in collaborative document 400. If the user desires to leave collaborative document 400, the user may select (e.g., click) conference affordance 418 to switch conference affordance 418 off. In response, the user may be directed back to the communication channel, e.g., as Figure 2 Other affordances may allow the user to invite others to collaborative document 400, react to content being shared within collaborative document 400 (e.g., emoticons, likes, etc.), and the like.

[0125] The collaborative document 400 also includes a thread 420 in which users within the collaborative document 400 communicate. Messages are posted within the thread 420. In some examples, users can type, upload / share documents, respond to other messages, etc. within the thread 420. For example, the thread 420 may include a messaging box 422 that allows users within the collaborative document 400 to communicate. In a non-limiting example, a user can type within the messaging box 422, upload images, documents, etc., react to postings, etc. In response to the message, the messaging component 116 may cause the collaborative document 400 to update and display the message. In some examples, the messaging component 116 may be configured to identify a mention or tag. In at least one example, the mention or tag may include an @ mention (or other special characters) of a user identifier associated with a communication platform. The user identifier may include a username, a real name, or other unique identifier associated with a particular user. In response to identifying a mention or tag of a user identifier, the messaging component 116 may cause a notification to be presented on a user interface associated with the user identifier.

[0126] In some examples, thread 420 is preloaded or otherwise filled with messages occurring in a communication channel. In this sense, collaborative document 400 may include a canvas generated using communications, files, etc. shared in a communication channel or generated in association with an object. For example, thread 420 is shown as displaying three messages, two of which include files. These messages and files may have been posted in a communication channel around the object around which collaborative document 400 was created. In this sense, collaborative document 400 may not include all communications occurring in a communication channel, but only those communications around the object in which collaborative document 400 was created. By filling collaborative document 400 with communications occurring in a communication channel, users of collaborative document 400 can quickly and easily determine context and previous communications occurring. Therefore, users can be able to access messages and / or data exchanged via a communication channel before arranging a virtual meeting.

[0127] For example, temporarily return to Figure 2 , a user (eg, user F) posted a message, and three replies are shown (eg, via indicator 214). Figure 4 Thread 420 in includes messages posted by the user and replies (e.g., three replies) from other users. Scrolling 424 is provided to allow the user to view these replies as well as the messages. In addition, an affordance 216 of a document, such as one included by the user in the message, is further displayed in the thread. The document may be accessed additionally or alternatively via a second indication 404 associated with the file. In some examples, selecting affordance 216 of a document or affordances of other documents in the thread may open a new window, application, pop-up window, etc. for viewing the document.

[0128] Collaborative document 400 allows users to use links, files, slides, documents, screen sharing, audio, video, etc. as a way to record communications, content, etc. when meeting about a particular object. In some examples, collaborative document 400 provides an archive to be referenced, edited, added to, etc. after the virtual meeting occurs. In this way, collaborative document 400 is intended to serve as a collaborative space for sharing and discussing content in real time, and afterward, collaborative document 400 can be reopened and edited by anyone with access. In some examples, collaborative document 400 can be used within synchronous or asynchronous work. For example, collaborative document 400 can be generated independently of a virtual meeting.

[0129] Figure 5 An exemplary user interface 142 is shown illustrating a collaborative document 500 generated in response to a virtual meeting being scheduled. Figure 5 The collaborative document 500 in may be similar to the above description of Figure 4 The collaborative document 400 discussed. However, Figure 5, collaborative document 500 is shown to include, for example, canvases of different styles.

[0130] For example, collaborative document 500 is shown to include a first area 502 including icons of users within collaborative document 500. Users can each include an icon (e.g., a picture, image, emoticon, etc.) to indicate their presence within collaborative document 500. For example, first icon 504 can be associated with a first user, second icon 506 can be associated with a second user, and third icon 508 can be associated with a third user. Fourth icon 510 allows a user to invite other users to collaborative document 500.

[0131] In some examples, collaborative document 500 includes a second area 512 located vertically below first area 502. Second area 512 may include affordances associated with adding a file to collaborative document 500, sharing a screen within collaborative document 500, and / or pasting a link into collaborative document 500 (e.g., a URL). For example, first affordance 514 may be associated with adding a file to collaborative document 500. In response to selecting first affordance 514, collaborative document 500 may include a pop-up window that allows a user to add a file to collaborative document 500. In some examples, the pop-up window may display files that the user has recently shared within the communication platform (whether within or outside of the communication channel).

[0132] The second affordance 516 allows the user to share their screen and present content. In such an example, the shared content can be displayed in the second area 512 of the collaborative document 500. At the same time, the third affordance 518 allows the user to paste a link to the collaborative document 500. For example, the user can provide a link (e.g., URL) to a third-party document, website, etc. The collaborative document 500 is also shown to include a thread 520, which can be similar to the thread 420 described above.

[0133] In some examples, second region 512 may represent a level of collaborative document 500 where content is shared and presented. For example, when a link is added, an affordance of the link may be presented in second region 512. For another example, if a file is attached, an affordance of the file may be presented in second region 512.

[0134] As described above, when a virtual meeting begins, a collaborative document 500 (such as thread 520) is populated with communications occurring within a communication channel. In some examples, messages are based at least in part on the object (e.g., message) around which the collaborative document 500 is created. The collaborative document 500 can represent a virtual canvas pre-seeded with content for the virtual meeting, and during the virtual meeting, the content is stored to collect, curate, and discuss work in an asynchronous manner that is more targeted than a communication channel. That is, a virtual meeting or collaborative document 500 is created around a specific object to focus on content that is important to the virtual meeting (e.g., files, videos, websites, etc.). These exchanges are shared in association with the collaborative document 500 for preservation, recording, and access at a later time.

[0135] Figure 6 An exemplary user interface is shown illustrating a collaborative document 600 generated in response to a virtual meeting being scheduled. Figure 6 The collaborative document 600 in may be similar to the above description of Figure 4 The collaborative document 400 discussed above and / or Figure 5 The collaborative document 500 discussed. However, Figure 6 , the collaborative document 600 is shown to include, for example, canvases of different styles.

[0136] For example, the first area 602 of the collaborative document 600 may include a first indication 604 of files that have been added to the communication channel, or a first indication of files related to the object used to create the collaborative document 600. As shown, the first indication 604 may include four files that have been added (e.g., uploaded) to the communication channel. These files may have been added by any user in the communication channel, and the first indication 604 may be displayed to allow users of the collaborative document 600 to quickly access and view the files (compared to closing the collaborative document and viewing the files). Users within the collaborative document 600 are allowed to open files, and in response, an affordance representation of the file may be displayed within the second area 606 of the collaborative document 600. The first indication 604 is shown as including four files that can be selected by the user, however, more than four files may be presented, and the user may be allowed to scroll or switch back and forth between the files in the first indication 604.

[0137] The second indication 608 is associated with the shared screen. For example, in order to view the content being shared (or presented) via one of the users, the second indication 608 can be selected. In some examples, when the second indication 608 is selected, the second area 606 can be updated to display the shared screen. The second indication 608 may include a preview of the content being shared by the user (e.g., user F). At the same time, the third indication 610 may be associated with a file that is published, uploaded, or included in the communication channel. For example, a link may point to a third-party website, a third-party document, etc. In some examples, a user is allowed to add additional files and links in addition to those files and links included (or collected) from the communication channel. For example, as described above with respect to Figure 5 As discussed, a user can add files and / or publish links. In such examples, the first indication 604 and the third indication 610 can be updated to indicate files and links, respectively. Moreover, in some examples, files and / or links can be added via thread 612.

[0138] The second area 606 is shown as displaying icons of users associated with the collaborative document 600. In some examples, the icons may represent live video streams of the users captured from their respective cameras, and / or pictures of the users (e.g., profile pictures). The user may have the ability to customize or individually select the content being displayed in the second area 606. For example, if the user chooses to view one of the files within the second indication 608, the second area 606 may be updated to display the file. In such examples, the user's icon may be displayed in the first area 602. However, in some examples, the second area 606 may display icons of the user and the file. In such examples, a separate window, screen, etc. may be displayed in the second area 606, and the user may have the option of selecting the content displayed in the second area 606.

[0139] Links, files, and other content (e.g., shared screens) presented within collaborative document 600 are archived for later use. For example, within a virtual meeting, users can share their respective screens, upload links, and otherwise share content. Content is stored within collaborative document 600 for use and / or viewing at a later time. In other words, the communications and content presented within collaborative document 600 are recorded, and collaborative document 600 can be accessed at a later time. When accessed at a later time, collaborative document 600 provides a quick and convenient reference to communications that occurred previously. In other words, by archiving collaborative document 600, the content of the virtual meeting is saved for use at a later time.

[0140] Figure 7 An exemplary user interface showing a collaborative document 700 generated in response to a virtual meeting being scheduled is shown. In some examples, Figure 7 The content is shown in the second area 512. Figure 5 Collaborative document 500. For example, according to Figure 5 In the collaborative document 500 shown, one of the users can share their screen. In response, the second area 512 is updated to display the first window 702 and the second window 704. In some examples, the first window 702 and the second window 704 can be presented from a single user or between different users. In the latter example, the user can switch back and forth between viewing the first window 702 and the second window 704, regardless of which content the presenter is currently sharing. The first area 502 is also shown to include icons representing users within the collaborative document 700. In some examples, the second area 512 represents a portion of the collaborative document 700 that includes an application cluster with which users can interact and collaborate.

[0141] As further shown, thread 520 allows users to post messages. For example, users (e.g., user A and user B) can post messages within thread 520, such as first message 706 and second message 708. First message 706 and second message 708 can be populated within collaborative document 700 and recorded to create a record of first message 706 and second message 708. For example, upon exiting collaborative document 700, first message 706 and second message 708 can be populated within the communication channel in association with the object around which collaborative document 700 was created.

[0142] In some examples, the collaborative document 700 can be associated with permissions that define which users of the communication platform can view and / or edit the collaborative document 700. In some examples, the collaborative document 700 can be associated with a communication channel, and at least some members of the communication channel can view and / or edit the collaborative document 700. In some examples, the collaborative document 700 can be shareable, such that data associated with the collaborative document 700 is accessible and / or interactable by users of multiple communication channels, workspaces, organizations, etc.

[0143] Figure 8 An exemplary user interface 142 is shown showing a collaborative document 800 generated in response to a virtual meeting being scheduled. In some examples, Figure 8 The content is shown in the second area 512. Figure 5 Collaborative document 500. For example, according to Figure 5 As shown in the collaborative document 500, one of the users may share their screen. In response, the second area 512 is updated to display the second area 512.

[0144] In some examples, the second area 512 is associated with a shared screen or content being presented by a first user (such as user F). The collaborative document 800 can show the position of a first cursor of the first user via a first indication 802. As shown, the first indication 802 is displayed in conjunction with the position of the first cursor within the content. The second area 512 also includes a second indication 804 associated with the position of a second cursor of the second user, and a third indication 806 associated with the position of a third cursor of a third user. As shown, the second indication 804 and the third indication 806 are displayed in conjunction with the positions of the first cursor and the second cursor within the content.

[0145] In some examples, displaying the first indication 802, the second indication 804, and / or the third indication 806 allows users of the collaborative document 800 to understand specific portions of the content that are being referenced or discussed by each other. For example, where the first user is referencing a specific segment or portion of the content, the second and third users can locate the first indication 802 for understanding the portion of the content that the first user is referencing. The same is true for the second and third users, as the first user is able to understand which portions of the content the second and third users are referencing.

[0146] Although the second area 512 is shown as displaying a single window, other windows, files, links, etc. may be displayed in the second area 512, and the first indication 802, the second indication 804, and / or the third indication 806 may be displayed across various windows, files, links, etc. For example, the first user may be presenting content within the second area 512, and the first indication 802 may reference the position of the cursor within the second area 512, while the second user may be viewing a file. Here, the file may be presented within the second area 512 (e.g., a portion thereof), and the second indication 804 may indicate the position of the cursor within the file. In some examples, the user may initially have to opt-in or give permission for their cursor to be tracked separately.

[0147] In some examples, a collaborative document 800 can be generated for a real-time virtual meeting that allows users to share files and screens that come alive with cursor tracking, drawing, and telepresence. Collaborative documents 800 also allow users to turn on / off video when needed (or when useful). When the virtual meeting ends, collaborative documents 800 persist so that users do not lose the shared discussions, files, or links. However, although this article discusses synchronous meetings, the technology herein can be extended to asynchronous meetings that are held within a defined time period and where users do not necessarily communicate in real time.

[0148] Fig. 9 An exemplary user interface 142 is shown showing a collaborative document 900 generated in response to a virtual meeting being scheduled. In some examples, Fig. 9 The content is shown in the second area 512. Figure 5 Collaborative documents.

[0149] The second area 512 is shown to include different content, such as first content 902, second content 904, and third content 906. In some examples, each of the first content 902, second content 904, and third content 906 is presented in a separate window within the second area 512. In addition, in some examples, each of the first content 902, second content 904, and third content 906 can be associated with different documents, files, links included in the collaborative document 900. In other examples, the first content 902, second content 904, and third content 906 can be associated with documents, files, links, etc. that the user is viewing. In this sense, those documents, files, links, etc. that the user is currently viewing can be populated in the second area 512. When the user switches to viewing other content, the second area 512 can be updated to indicate this. In other examples, content can be presented from a single user, and other users can have the opportunity to move between content and view different content.

[0150] The first content 902 is shown as being displayed in conjunction with the first mark 908. In some examples, the first mark 908 may highlight, outline, or otherwise represent the first content 902 among other windows. The first mark 908 may be used to indicate content (such as the first content 902) that a user (e.g., user A) is presenting. As further shown, in the first area 502, the icon 910 of the user (e.g., user A) may include a second mark 912 that matches or is otherwise associated with the first mark 908. In this sense, the first mark 908 and the second mark 912 may be the same. For example, if the first mark 908 includes a blue highlight border around the first content 902, the second mark 912 may include a blue highlight border around the icon 910. As described above, the user's icon 910 may include an image or video stream of the user. By associating the first mark 908 and the second mark 912, other users within the collaborative document 900 can visually identify the content that the user is presenting, sharing, or otherwise referencing. The first mark 908 and the second mark 912 may be customizable by the user. In addition, in examples where multiple users are presenting content, different pairs of markers may be used to represent the content being presented by the users, respectively. For example, if another user is additionally presenting content, another set of markers (e.g., a pink outline with a dashed line) may be represented around the content in the second area 512.

[0151] In some examples, an indication of the content that the user is viewing may also be indicated. For example, a first indication 914 of a second user is shown as being presented in conjunction with the second content 904. The first indication 914 may include a representation of the second user and indicate to other users within the collaborative document 900 that the second user is viewing the second content 904. In addition, a second indication 916 is shown as being presented in association with the third content 906 to indicate to other users within the collaborative document 900 that the third user is viewing the third content 906. Of course, in examples in which the collaborative document 900 includes additional users, additional indications may be presented. In some examples, the first indication 914 and / or the second indication 916 may each include a face pile of the user.

[0152] In some examples, the content within the second area 512 can be reordered and / or otherwise rearranged by the user, respectively. In such examples, the second area 512 or the content displayed in the second area 512 can be modified so that the user can customize and / or personalize the collaborative document 900 to serve their individual needs. Although the collaborative document 900 is shown as including certain content, the collaborative document 900 can support the integration of other applications (via an API), other forms of collaboration, including drawing, cursor tracking, jamboards (e.g., digital whiteboards), etc.

[0153] Fig.10 An exemplary user interface 142 is shown showing a collaborative document 1000 generated in response to a virtual meeting being scheduled. In some examples, Fig.10 The collaborative document 1000 may be similar to Figure 6 600 collaborative documents.

[0154] The first area 602 is shown to include a first content 1002 being presented by a first user (e.g., user A) and a second content 1004 being presented by a second user (e.g., user B). The first content 1002 and the second content 1004 may include a first tag 1006 and a second tag 1008, respectively, to associate the first content 1002 and the second content 1004 with the first user and the second user. For example, within the first area 602, the first content 1002 includes a first tag 1006, which is similar to the third tag 1010 around the first icon 1012 of the first user in the second area 606. Similarly, within the first area 602, the second content 1004 includes a second tag 1008, which is similar to the fourth tag 1014 around the second icon 1016 of the second user in the second area 606.

[0155] according to Fig.10In the view shown, users can select content they wish to view, or content that is already presented within the second region 606 of the collaborative document 1000. For example, if a third user (e.g., user F) desires to view the first content 1002, the third user can select the first content 1002 (or its affordance) within the first region 602. In response, the second region 606 of the collaborative document 1000 can be updated to display the second content 1004 to the third user.

[0156] The multiple shared screens shown in the collaborative document 1000 provide an archive of links and conversations that are tracked and recorded. For example, within a virtual meeting, users can share their respective screens, upload links, and otherwise share content. The content is stored within the collaborative document 1000 for use and / or viewing at a later time. In other words, the communications and content presented within the collaborative document 1000 are recorded, and the collaborative document can be accessed at a later time.

[0157] Fig.11 An exemplary user interface 142 is shown after terminating or closing a collaborative document. As shown, a communication channel is shown. However, the communication channel can be updated based on the communication occurring within the collaborative document. For example, with the previous three replies (such as Figure 2 In contrast to the instructions shown in FIG. 214 , the instructions 214 are shown to include five replies. That is, temporarily returning to Figure 7 A collaborative document, for example, in which a user posts messages to a collaborative document, can indicate those messages within a communication channel and in association with the object around which the collaborative document was created. In other words, because the collaborative document was created around the messages, the communications within the thread (or more generally, the collaborative document) can be embedded back into the communication channel and associated with the messages. This archives the communications within the collaborative document. By grouping replies, discussions associated with a virtual meeting and / or collaborative document can be maintained in association with an object (e.g., a message in a communication channel) so that users can easily follow discussions related to the virtual meeting and can access content to understand the discussions associated with the virtual meeting (e.g., without being distracted by other events in the communication channel).

[0158] Additionally, in some examples, an indication of the virtual meeting and / or collaborative document can be presented in the communication channel to indicate that the virtual meeting occurred. In some examples, the user can select on indication 214 to open the thread and / or view the collaborative document. For example, in at least one example, a message representing the virtual meeting can be posted to the communication channel.

[0159] As further shown, the affordance 148 is not displayed in conjunction with the message. However, if the user's cursor hovers over a particular area of ​​the message (e.g., the upper right corner), the affordance 148 may be displayed. Additionally, affordance 210 within fifth subsection 208 is shown as being switched off to indicate that a virtual meeting is not currently occurring. However, if the user hovers over affordance 214, a virtual meeting pop-up window may be displayed that allows the user to open a collaborative document.

[0160] Fig.12 and Fig.13 A process for generating a collaborative document in association with a virtual meeting is shown. The process described herein is shown as a collection of boxes in a logical flow chart, which represents a series of operations, some or all of which can be implemented in hardware, software, or a combination thereof. In the context of software, a box can represent computer-executable instructions stored on one or more computer-readable media, which, when executed by one or more processors, program the processors to perform the described operations. Generally speaking, computer-executable instructions include routines, programs, objects, components, data structures, etc. that perform specific functions or implement specific data types. Unless otherwise specified, the order in which these boxes are described should not be construed as limiting. Any number of boxes can be combined in any order and / or in parallel to implement a process or an alternative process, and all boxes need not be executed. For the purposes of discussion, reference is made to the environment, architecture, and system described in the examples herein (such as with respect to Figures 1 to 11 These processes are described in the context of those environments, architectures, and systems described herein, but can be implemented in a variety of other environments, architectures, and systems.

[0161] At 1202, process 1200 may include receiving a request to generate a virtual meeting associated with an object. In an example, an object may include a text document, an image, a video, a message, or any other file or data item. For example, a first user may request a virtual meeting in association with a message within a communication channel in which the first user and one or more additional users are communicating. In some examples, the request may be received independently of the communication channel and independently of the object. However, for the example, the first user may request a virtual meeting with one or more additional users to discuss the object or otherwise collaborate around the object.

[0162] At 1204, process 1200 may include determining data associated with the object. For example, within a communication channel, a user may have posted a link, uploaded a document, or communicated a message regarding the object. The data is used to determine or understand the context of the virtual meeting and to generate a collaborative document associated with the virtual meeting. For example, the data may be presented within the collaborative document to allow a user to engage with a file, link, document, etc.

[0163] At 1206, process 1200 may include generating a collaborative document in association with a virtual meeting including data. For example, the collaborative document implements messaging and sharing functionality that can be attributed to a virtual space. In some examples, the collaborative document may be a virtual space, board, canvas, page, etc. for collaborative communication and / or data organization within a communication platform. That is, the collaborative document may be viewed as a virtual space (such as a communication channel) and includes functionality associated with a virtual space (such as a communication channel). Thus, within a collaborative document, users may communicate, exchange messages, share content, etc. Using data, a collaborative document may be populated with or otherwise indicate communications previously exchanged within a communication channel and associated with an object. For example, links, documents, videos, content, etc. that occur in association with an object within a communication channel may be indicated within a collaborative document as a way to provide context for a virtual meeting. In doing so, within a collaborative document, users may participate in audio and / or video communications, as well as share links, documents, screens (i.e., screen sharing), etc.

[0164] In at least one example, collaborative documents may support editable text and / or objects that may be sorted, added, deleted, modified, etc. Collaborative documents may support a variety of elements such as, but not limited to, text, symbols, emoticons, images, video, audio, charts, tables, lists, calendar items, spreadsheets, drawings, etc.

[0165] At 1208, process 1200 may include causing a collaborative document to be displayed in association with the virtual meeting. For example, on a user interface, a collaborative document may be displayed such that a user may participate in audio and / or video communications, as well as share links, documents, chat, share screens (i.e., screen sharing), etc. In some examples, a collaborative document may include a thread that allows users to post messages to each other, upload links, share files, share screens, etc. Additionally, as described above, a collaborative document may be populated with or otherwise indicate files, documents, links, etc. associated with an object. A user may also have the ability to disable audio and / or video based on personal preferences.

[0166] At 1210, process 1200 can include determining one or more users associated with the virtual meeting and / or collaborative document. In some examples, the one or more users can be determined based at least in part on the context around which the collaborative document was created, such as those users who are members of a communication channel. In other examples, a user requesting a virtual meeting can manually enter a user name (or other identifier) ​​of a user to be invited to the virtual meeting.

[0167] At 1212, process 1200 may include sending an invitation to one or more users associated with the virtual meeting. For example, based on identifying the one or more users, the communication platform may send the invitation to these users. In some examples, the invitation may include data associated with the collaborative document to indicate the context of the virtual meeting to the user. As an example, if a virtual meeting is created in association with the object, the invitation may indicate that a virtual meeting is being scheduled to discuss the object.

[0168] At 1214, process 1200 may include receiving input via the collaborative document. The input may generally represent actions within the collaborative document, such as the time when content was shared, messages conveyed within the collaborative document, links posted to the collaborative document, applications accessed, people presenting / sharing content, etc. In other words, the collaborative document created in association with the virtual meeting may track and record what is happening within the virtual meeting. This, in part, allows a recording of the virtual meeting to be created and archived for later use and access. Thus, when a user engages in audio and / or video communications and shares links, documents, screens (i.e., screen sharing), etc., such input may be received and recorded.

[0169] Additionally, when a user is interacting with a collaborative document, the user may benefit from updates that indicate whether other users are also simultaneously interacting with the collaborative document. For example, in a collaborative context, a user may wish to be able to quickly determine which other users are currently interacting with the collaborative document. Additionally, a user may desire to know what content, files, links, etc. of the collaborative document others are interacting with. A collaborative document may include a presence indicator that indicates to a user when another user is interacting with the collaborative document.

[0170] At 1216, process 1200 can include updating the collaborative document based at least in part on the input. For example, links, files, and other content (e.g., a shared screen) presented within the collaborative document are archived for later use. Thus, when the virtual meeting ends, the collaborative document still persists so that the users do not lose the discussion, files, or links shared in the virtual meeting.

[0171] At 1218, process 1200 may include causing an affordance representation of the collaborative document to be displayed in association with the object. In this way, after the virtual meeting is terminated, the collaborative document is stored and archived for later use and / or reference. Through the use of affordance representations, the collaborative document is intended to serve as a collaborative space for sharing and discussing content in real time, and thereafter, the collaborative document may be reopened and edited by anyone with access. In some examples, the collaborative document may be used within synchronous or asynchronous work. For example, the collaborative document may be generated independent of the virtual meeting.

[0172] A collaborative document is configured to be accessed and / or edited by two or more users with appropriate permissions (e.g., permission to view, permission to edit, etc.). In some examples, a collaborative document may be associated with permissions that define which users of the communication platform may view and / or edit the collaborative document. In some examples, a collaborative document may be associated with a communication channel, and permissions may be based on channel membership, such that members of the communication channel may view and / or edit the document. In some examples, a collaborative document may be shareable (e.g., via a link or other address indication), such that data associated with the document is accessible and / or interactive to members of multiple communication channels, workspaces, organizations, etc. For example, a collaborative document may be associated with a user, channel, or other virtual space, and may be shared with users who are not members by sharing a link to the document.

[0173] In at least one example, in response to receiving an indication of a selection of an affordance, the communications platform can cause presentation of a collaborative document via (or within a portion of) a user interface.

[0174] As described above, collaborative documents may be created in association with certain permissions. For example, access permissions to collaborative documents may be granted to users of collaborative documents based in part on user or organizational preferences associated with the user who created the collaborative document. In such examples, permission settings associated with the collaborative document may be stored in association with user accounts of users or members of the collaborative document. In at least one example, permission settings may include full editing permissions associated with the collaborative document. In such examples, users of the collaborative document may be granted permissions to contribute to the collaborative document and / or to edit or otherwise modify the collaborative document. In other examples, permission settings may include limited editing permission settings, such as permissions to add content but not delete content, permissions to comment but not modify text in a collaborative document, read-only permissions, and the like.

[0175] Additionally or alternatively, in some examples, permission settings may include settings associated with sharing data within a collaborative document. In some examples, data may include content that is published or otherwise made available via other virtual spaces that are not associated with the collaborative document. That is, based on sharing permissions, users may be allowed or constrained to share data (e.g., messages, files, etc.) that are published or otherwise made available via an unrelated virtual space within a collaborative document. In some examples, data may be presented in a collaborative document as an object including an indicator of a virtual space, an identifier associated with a sending user, and other data. In various examples, data may be presented as a read-only object so that data may not be manipulated within a collaborative document. In some examples, data as an object (similar to other objects presented in association with a collaborative document) may be configured to be used as the root of a message thread. In such examples, although members of a collaborative document may not have permission to modify data, members may be able to discuss or otherwise comment on data in a messaging thread associated with the data.

[0176] In addition, in various examples, permission settings may include permission to share a collaborative document and / or a portion thereof with one or more additional users. In various examples, permission settings may include full sharing permission (e.g., sharing a collaborative document or a portion thereof with read and write capabilities), limited sharing permission (e.g., sharing a read-only copy of a collaborative document or a portion thereof), no sharing permission (e.g., not allowing a user to share a collaborative document with a non-member). In at least one example, permission settings associated with sharing a collaborative document may specify whether a particular user can add another user as a member of the collaborative document. In some examples, permission settings associated with sharing a collaborative document may be based on organizational affiliations with the requesting user and the additional user. For example, permission settings may enable members to share collaborative documents with other users of a first organization without sharing collaborative documents with users associated with other organizations. As another example, permission settings may enable members to share collaborative documents with members of a first organization with full editing permission, and to share a read-only copy of a collaborative document with members of a second organization. Therefore, a communication platform may enable data presented in a collaborative document to be shared, but not modified by members of a second organization, such as to maintain the integrity of the data. In some examples, permissions to share collaborative documents and / or add additional users thereto may be specified by the creating user, explicitly as a specified user preference and / or organizational preference associated with the creating user's organization, or as a default setting associated with the communication platform.

[0177] Fig.13An exemplary process 1300 for obtaining a previously generated collaborative document is shown. At 1302, process 1300 can include receiving a first request to join a first virtual meeting. For example, a user can request a virtual meeting to collaborate around an object and conduct a virtual meeting with other users within a communication channel (or on a communication platform). In some examples, the virtual meeting can include text-based, audio-based, and / or video-based communications.

[0178] At 1304, process 1300 may include generating a first collaborative document in association with the first virtual meeting. In some examples, the first collaborative document is generated based on a link, an uploaded document, or a message conveyed within a communication channel about an object. As discussed herein, collaborative documents enable messaging and sharing functionality that can be attributed to virtual spaces, boards, canvases, pages, etc. to enable collaborative communications and / or data organization within a communication platform. The collaborative document may be populated with or otherwise indicate communications previously exchanged within a communication channel and associated with an object. For example, links, documents, videos, content, etc. that occur within a communication channel in association with an object may be indicated within a collaborative document as a way to provide context for the virtual meeting.

[0179] At 1306, process 1300 may include receiving a second request to leave the first virtual meeting. For example, the user may close the collaborative document. At 1308, process 1300 may include causing an affordance representation of the collaborative document to be displayed in association. In an example, after the virtual meeting is terminated, the collaborative document is stored and archived for later use and / or reference. By using affordance representations, the collaborative document is intended to serve as a collaborative space for sharing and discussing content in real time, and the collaborative document may be reopened and edited by anyone with access thereto.

[0180] At 1310, process 1300 can include receiving a third request to join a second virtual meeting. For example, a user can request a virtual meeting to collaborate around an object and conduct a virtual meeting with other users within a communication channel (or on a communication platform). In some examples, the virtual meeting can include text-based, audio-based, and / or video-based communications.

[0181] At 1312, process 1300 may include determining whether the second virtual meeting is associated with the first virtual meeting. For example, whether the first virtual meeting and the second virtual meeting are associated may be based on whether users schedule meetings to discuss the same object, whether the users invited to the first virtual meeting and the second virtual meeting are the same, whether the third request includes an identifier that is similar (e.g., an identifier) ​​to the first virtual meeting and the second virtual meeting, etc. In other examples, the third request may be received in association with an affordance representation of the collaborative document. That is, by selecting the affordance representation of the collaborative document, the second virtual meeting may be a continuation or associated with the first virtual meeting.

[0182] If at 1312, process 1300 determines that the first virtual meeting and the second virtual meeting are associated, process 1300 can follow the "yes" route and proceed to 1314. At 1314, process 1300 can include obtaining a first collaborative document and causing the first collaborative document to be displayed. Thus, process 1300 illustrates a scenario in which collaborative documents are stored and archived for later use and / or reference after the virtual meeting is terminated. That is, when the virtual meeting ends, the collaborative document still persists so that the user does not lose the discussion, files, or links shared in the virtual meeting. At a later moment, another virtual meeting around the same object may occur, and in such an instance, the collaborative document is accessed.

[0183] If at 1312, process 1300 determines that the first virtual meeting and the second virtual meeting are not associated, the process can follow a "no" route and proceed to 1316 and generate a second collaborative document in association with the second virtual meeting.

[0184] Example clauses

[0185] A: A method implemented at least in part by one or more computing devices of a group-based communication platform, the method comprising: receiving a first request to create a virtual meeting, the virtual meeting being associated with a virtual space of a communication system and a first user account of a first user, the virtual meeting having at least one of audio capability or video capability; receiving a second request to create a document associated with the virtual meeting; identifying one or more objects in the virtual space, wherein the one or more objects are associated with one or more users of the virtual space; generating a document based at least in part on the second request and the one or more objects; causing the document to be displayed in a user interface of the communication system; detecting a selection of an object of the one or more objects in the user interface; and in response to detecting the selection of the object, causing the object to be displayed in the document.

[0186] B: The method of paragraph A, wherein causing the document to be displayed comprises: causing a first indication of an object to be displayed; and causing a second indication of a second object of the one or more objects to be displayed.

[0187] C: A method according to paragraph A or B, wherein causing a document to be displayed includes: causing one or more icons to be displayed within a first area of ​​the document, individual icons of the one or more icons being associated with individual objects of one or more objects; and causing content associated with the one or more objects to be displayed within a second area of ​​the document.

[0188] D: A method according to any of paragraphs A to C, wherein the document also includes a message thread populated with communications within the virtual space of the communication system.

[0189] E: The method according to any one of paragraphs A to D also includes: receiving a second request to associate the document with a second user account of a second user different from the first user; in response to receiving the second request, associating the document with the second user account; and in response to associating the document with the second user account, displaying an identifier associated with the virtual meeting in a second user interface associated with the second user account.

[0190] F: A method according to any of paragraphs A to E, wherein the virtual space includes a communication channel.

[0191] G: The method according to any one of paragraphs A to F also includes: receiving an interaction associated with the first user in the virtual space; and presenting an enable representation based on the interaction, wherein selection of the enable representation is associated with receiving a first request to create a virtual meeting.

[0192] H: The method of any of paragraphs A to G, further comprising determining one or more permissions associated with the document, the one or more permissions comprising at least one of editing capabilities of the document or disclosure of the document.

[0193] I: A method according to any of paragraphs A to H, wherein the object includes at least one of: a task; a work order; a document; a calendar event; or a message transmitted via a communication system and shared in association with a document.

[0194] J: A system implemented at least in part by one or more computing devices of a group-based communication platform, the system comprising: one or more processors; and one or more non-transitory computer-readable media storing instructions that, when executed, cause the system to perform operations comprising: receiving a first request to create a virtual meeting, the virtual meeting being associated with a virtual space of a communication system and a first user account of a first user, the virtual meeting having at least one of audio capability or video capability; receiving a second request to create a document associated with the virtual meeting; identifying one or more objects in the virtual space, wherein the one or more objects are associated with one or more users of the virtual space; generating a document based at least in part on the second request and the one or more objects; causing the document to be displayed in a user interface of the communication system; detecting a selection of an object of the one or more objects in the user interface; and in response to detecting a selection of the object, causing the object to be displayed in the document.

[0195] K: A system according to paragraph J, wherein causing display of the document comprises: causing display of a first indication of an object; and causing display of a second indication of a second object of the one or more objects.

[0196] L: A system according to paragraph J or K, wherein causing display of a document includes: causing one or more icons to be displayed within a first area of ​​the document, individual icons of the one or more icons being associated with individual objects of one or more objects; and causing content associated with the one or more objects to be displayed within a second area of ​​the document.

[0197] M: A system according to any of paragraphs J to L, wherein the document also includes a message thread populated with communications within the virtual space of the communication system.

[0198] N: In a system according to any of paragraphs J to M, the operations further include: receiving a second request to associate a document with a second user account of a second user different from the first user; in response to receiving the second request, associating the document with the second user account; and in response to associating the document with the second user account, displaying an identifier associated with the virtual meeting in a second user interface associated with the second user account.

[0199] P: In a system according to any one of paragraphs J to N, the operation further includes: receiving an interaction associated with a first user in a virtual space; and presenting an enabling representation based on the interaction, wherein selection of the enabling representation is associated with receiving a first request to create a virtual meeting.

[0200] Q: A system according to any of paragraphs J to P, wherein the operations further include determining one or more permissions associated with the document, the one or more permissions including at least one of editing capabilities of the document or disclosure of the document.

[0201] R: One or more non-transitory computer-readable media storing instructions that, when executed, cause one or more processors to perform operations, the operations comprising: receiving a first request to create a virtual meeting, the virtual meeting being associated with a virtual space of a communication system and a first user account of a first user, the virtual meeting having at least one of audio capability or video capability; receiving a second request to create a document associated with the virtual meeting; identifying one or more objects in the virtual space, wherein the one or more objects are associated with one or more users of the virtual space; generating a document based at least in part on the second request and the one or more objects; causing the document to be displayed in a user interface of the communication system; detecting a selection of an object of the one or more objects in the user interface; and in response to detecting a selection of the object, causing the object to be displayed in the document.

[0202] S: One or more non-transitory computer-readable media according to paragraph R, wherein the document further comprises a message thread populated with communications within the virtual space of the communication system.

[0203] T: According to one or more non-transitory computer-readable media of paragraphs R or S, the operations also include: receiving a second request to associate the document with a second user account of a second user different from the first user; in response to receiving the second request, associating the document with the second user account; and in response to associating the document with the second user account, displaying an identifier associated with the virtual meeting in a second user interface associated with the second user account.

[0204] Although the exemplary clauses described above are described with respect to a specific implementation, it should be understood that in the context of this document, the content of the exemplary clauses may also be implemented via a method, an apparatus, a system, a computer-readable medium, and / or another implementation. In addition, any of Examples A to T may be implemented alone or in combination with any other one or more of Examples A to T.

[0205] in conclusion

[0206]

[00136] While one or more examples of the techniques described herein have been described, various alterations, additions, permutations, and equivalents thereof are included within the scope of the techniques described herein.

[0207] In the description of the examples, reference is made to the accompanying drawings forming a part of the present invention, which illustrate specific examples of the claimed subject matter in an illustrative manner. It should be understood that other examples may be used, and changes or alterations, such as structural changes, may be made. Such examples, changes or alterations do not necessarily depart from the scope of the claimed subject matter relative to the intended protection. Although the steps herein may be presented in a particular order, in some cases, the ordering may be changed so that specific inputs are provided at different times or in different orders without changing the functions of the described systems and methods. The disclosed programs may also be executed in different orders. In addition, it is not necessary to perform the various calculations herein in the disclosed order, and other examples using alternative calculation ordering may be easily implemented. In addition to being reordered, calculations may also be decomposed into sub-calculations that achieve the same result.

Claims

1. A method implemented at least in part by one or more computing devices of a group-based communication platform, the method comprising: receiving a first request to create a virtual conference, the virtual conference being associated with a virtual space of the communication system and a first user account of a first user, the virtual conference having at least one of audio capability or video capability; receiving a second request to create a document associated with the virtual meeting; identifying one or more objects in the virtual space, wherein the one or more objects are associated with one or more users of the virtual space; generating the document based at least in part on the second request and the one or more objects; causing the document to be displayed in a user interface of the communication system; detecting a selection of an object of the one or more objects in the user interface; and In response to detecting the selection of the object, the object is caused to be displayed in the document.

2. The method of claim 1 , wherein causing the document to be displayed comprises: causing a first indication of the object to be displayed; and A second indication of a second object of the one or more objects is caused to be displayed.

3. The method of claim 1 or 2, wherein causing the document to be displayed comprises: causing one or more icons to be displayed within the first area of ​​the document, individual icons of the one or more icons being associated with individual objects of the one or more objects; and The content associated with the one or more objects is caused to be displayed in a second area of ​​the document.

4. The method according to any one of claims 1 to 3, wherein the document further comprises a message thread populated with communications within the virtual space of the communication system.

5. The method according to any one of claims 1 to 4, further comprising: receiving a second request to associate the document with a second user account of a second user different from the first user; in response to receiving the second request, associating the document with the second user account; and In response to associating the document with the second user account, an identifier associated with the virtual meeting is displayed in a second user interface associated with the second user account.

6. The method according to any one of claims 1 to 5, wherein the virtual space comprises a communication channel.

7. The method according to any one of claims 1 to 6, further comprising: receiving an interaction associated with the first user in the virtual space; and An affordance is presented based on the interaction, wherein selection of the affordance is associated with receiving the first request to create the virtual meeting.

8. The method according to any one of claims 1 to 7, further comprising determining one or more permissions associated with the document, the one or more permissions comprising at least one of editing capabilities of the document or publication of the document.

9. The method according to any one of claims 1 to 8, wherein the object comprises at least one of the following: Task; Work orders; document; Calendar events; or A message is transmitted via the communication system and shared in association with the document.

10. A computer program product comprising coded instructions for implementing the method according to any one of claims 1 to 9 when executed on a computer.

11. A system implemented at least in part by one or more computing devices of a group-based communication platform, the system comprising: one or more processors; and One or more non-transitory computer-readable media storing instructions that, when executed, cause the system to perform operations comprising: receiving a first request to create a virtual conference, the virtual conference being associated with a virtual space of the communication system and a first user account of a first user, the virtual conference having at least one of audio capability or video capability; receiving a second request to create a document associated with the virtual meeting; identifying one or more objects in the virtual space, wherein the one or more objects are associated with one or more users of the virtual space; generating the document based at least in part on the second request and the one or more objects; causing the document to be displayed in a user interface of the communication system; detecting a selection of an object of the one or more objects in the user interface; and In response to detecting the selection of the object, the object is caused to be displayed in the document.

12. The system of claim 11, wherein causing the document to be displayed comprises: causing a first indication of the object to be displayed; and A second indication of a second object of the one or more objects is caused to be displayed.

13. The system of claim 11 or 12, wherein causing the document to be displayed comprises: causing one or more icons to be displayed within the first area of ​​the document, individual icons of the one or more icons being associated with individual objects of the one or more objects; and The content associated with the one or more objects is caused to be displayed in a second area of ​​the document.

14. The system of any one of claims 11 to 13, wherein the document further comprises a message thread populated with communications within the virtual space of the communication system.

15. The system according to any one of claims 11 to 14, wherein the operations further comprise: receiving a second request to associate the document with a second user account of a second user different from the first user; in response to receiving the second request, associating the document with the second user account; and In response to associating the document with the second user account, an identifier associated with the virtual meeting is displayed in a second user interface associated with the second user account.

Images