Collaboration method, apparatus, and storage medium

Abstract

The application relates to a collaboration method, device and storage medium, the method comprising: in response to an operation of adding a first collaboration object to a target collaboration space, creating a belonging identifier for the first collaboration object, the belonging identifier being used to indicate that the first collaboration object belongs to the target collaboration space; based on the belonging identifier, displaying an access portal of the first collaboration object in an interface of the target collaboration space, and managing collaboration members of the first collaboration object and collaboration members of the target collaboration space. Thus, the portal aggregation of the collaboration object and the integrated management of the members are realized, and the technical problems of scattered operation paths and split context caused by the mutual independence of group chats and team spaces and the lack of unified control mechanism in the prior art are solved, so that the operation complexity and maintenance cost are reduced, and the collaboration efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of computers, and more particularly to a collaborative method, apparatus, and storage medium. Background Technology

[0002] In team collaboration scenarios, team space, as a lightweight collaboration tool, can aggregate and manage resources such as documents, tasks, and files to improve collaboration efficiency.

[0003] However, in existing technologies, instant messaging group chats exist only as independent sessions in the global message list of team collaboration platforms and cannot be effectively integrated into the team space management system. If users need to associate group chats with other resources within the team space, they still need to frequently switch between the global message interface and the team space interface, resulting in fragmented operation paths and disconnected context. Summary of the Invention

[0004] This application provides a collaboration method, apparatus, and storage medium to solve the technical problem in the prior art where group chat and team space are independent of each other and lack a unified management mechanism, resulting in users having to frequently switch between the global message interface and team space interface of the team collaboration platform, scattered operation paths, and fragmented contexts, which cannot meet the needs of integrated and centralized team collaboration.

[0005] In a first aspect, this application provides a collaborative method, the method comprising: In response to the operation of adding a first collaboration object to a target collaboration space, an ownership identifier is created for the first collaboration object, the ownership identifier being used to indicate that the first collaboration object belongs to the target collaboration space; Based on the affiliation identifier, the access entry of the first collaborative object is displayed in the interface of the target collaborative space, and the collaborative members of the first collaborative object and the collaborative members of the target collaborative space are managed.

[0006] In one possible implementation, the method further includes: Based on the attribution identifier, the access entry of the first collaborative object is hidden in the access interface of the first collaborative object; wherein, the access interface of the first collaborative object is independent of the interface of the target collaborative space.

[0007] In one possible implementation, the method further includes: In response to the generation of a new message from the first collaborating object, a message notification for the new message is displayed in the interface of the target collaborating space based on the attribution identifier.

[0008] In one possible implementation, the method further includes: The access entry corresponding to the target collaboration space is displayed in the access interface of the first collaboration object; In response to the generation of a new message by the first collaborating object in the target collaboration space, a message notification of the new message is displayed at the space access entry point according to the ownership identifier; In response to triggering the space access entry, the system jumps to the interface of the target collaborative space and locates the interaction window of the first collaborative object.

[0009] In one possible implementation, when the first collaborative object belongs to multiple target collaborative spaces, the space access entrances corresponding to each of the multiple target collaborative spaces are displayed side by side in the access interface, and each space access entrance independently displays the unread message reminder of the first collaborative object in the corresponding target collaborative space; Alternatively, an aggregated space access entry can be displayed in the access interface, showing the total number of unread messages in the multiple target collaboration spaces; in response to triggering the aggregated space access entry, a list of the multiple target collaboration spaces can be displayed for the user to select.

[0010] In one possible implementation, the method further includes: In the interface of the target collaboration space, multiple collaboration objects belonging to the target collaboration space are grouped and displayed according to preset classification dimensions based on the attribute information associated with the affiliation identifier.

[0011] In one possible implementation, the method further includes: In the interface of the target collaboration space, based on the ownership identifier, the collaboration objects that have belonged to the target collaboration space and have not yet been joined by the current account are displayed; In response to the current account's joining operation of the collaboration object that has not yet been joined, the current account is added to the member set of the collaboration object and the current account's session interface in the joined collaboration object is displayed.

[0012] In one possible implementation, the method further includes: In response to detecting that the first collaborative object has not generated any new messages within a preset time period, the first collaborative object is marked as archived in the interface of the target collaborative space; If the first collaborating object generates a new message, the archiving state is lifted.

[0013] In one possible implementation, the method further includes: In response to receiving an access request to the first collaborative object in the access interface of the first collaborative object, a redirection prompt message is output to guide the user to access the first collaborative object through the target collaborative space; wherein the access interface is independent of the interface of the target collaborative space.

[0014] In one possible implementation, the method further includes: In response to receiving an access request to the first collaborative object via an external link, the access request is redirected to the interface of the target collaborative space based on the attribution identifier, and the interactive window of the first collaborative object is located in the interface of the target collaborative space.

[0015] In one possible implementation, the method further includes: In response to the operation of removing the first collaborative object from the target collaborative space, the ownership identifier of the first collaborative object is cleared, and the access entry of the first collaborative object in the access interface is restored.

[0016] In one possible implementation, the method further includes: In response to receiving a search request for the first collaborative object in the search interface, and displaying the first collaborative object in the search results, the identification information of the target collaborative space is displayed in the search results in association with the attribution identifier.

[0017] Secondly, this application provides a collaborative device, the device comprising: The attribution identifier module is used to create an attribution identifier for the first collaborative object in response to the operation of adding the first collaborative object to the target collaborative space. The attribution identifier is used to indicate that the first collaborative object belongs to the target collaborative space. An entry display module is used to display the access entry of the first collaborative object in the interface of the target collaborative space based on the ownership identifier; The member management module is used to manage the collaborative members of the first collaborative object and the collaborative members of the target collaborative space.

[0018] In one possible implementation, the device further includes: An entry hiding module is used to hide the access entry of the first collaborative object in the access interface of the first collaborative object based on the ownership identifier; wherein the access interface of the first collaborative object is independent of the interface of the target collaborative space.

[0019] In one possible implementation, the device further includes: The new message notification module is used to respond to the generation of a new message from the first collaborating object and, based on the attribution identifier, display a message notification of the new message in the interface of the target collaborating space.

[0020] In one possible implementation, the device further includes: The access entry setting module is used to display the space access entry corresponding to the target collaboration space in the access interface of the first collaboration object; The new message notification module is used to respond to the generation of a new message by the first collaborating object in the target collaboration space, and display a message notification of the new message at the space access entry according to the ownership identifier; The jump module is used to respond to the triggering of the space access entry, jump to the interface of the target collaborative space, and locate the interaction window of the first collaborative object.

[0021] In one possible implementation, when the first collaborative object belongs to multiple target collaborative spaces, the space access entrances corresponding to each of the multiple target collaborative spaces are displayed side by side in the access interface, and each space access entrance independently displays the unread message reminder of the first collaborative object in the corresponding target collaborative space; Alternatively, an aggregated space access entry can be displayed in the access interface, showing the total number of unread messages in the multiple target collaboration spaces; in response to triggering the aggregated space access entry, a list of the multiple target collaboration spaces can be displayed for the user to select.

[0022] In one possible implementation, the device further includes: The group display module is used to group and display multiple collaborative objects belonging to the target collaborative space according to a preset classification dimension in the interface of the target collaborative space based on the attribute information associated with the affiliation identifier.

[0023] In one possible implementation, the device further includes: The collaboration joining module is used to display, in the interface of the target collaboration space, collaboration objects that have belonged to the target collaboration space but have not yet been joined by the current account, based on the ownership identifier. In response to the current account's joining operation of the collaboration object that has not yet been joined, the current account is added to the member set of the collaboration object and the current account's session interface in the joined collaboration object is displayed.

[0024] In one possible implementation, the device further includes: The archiving module is used to mark the first collaborative object as archived in the interface of the target collaborative space in response to detecting that the first collaborative object has not generated a new message within a preset time period. The archive release module is used to release the archive state when the first collaborating object generates a new message.

[0025] In one possible implementation, the device further includes: A guidance module is used to respond to receiving an access request to the first collaborative object in the access interface of the first collaborative object, and output a jump prompt message to guide the user to access the first collaborative object through the target collaborative space; wherein the access interface is independent of the interface of the target collaborative space.

[0026] In one possible implementation, the device further includes: The redirection module is used to respond to an access request to the first collaboration object received via an external link, redirect the access request to the interface of the target collaboration space according to the attribution identifier, and locate the interactive window of the first collaboration object in the interface of the target collaboration space.

[0027] In one possible implementation, the device further includes: The attribution removal module is used to, in response to the operation of removing the first collaborative object from the target collaborative space, clear the attribution identifier of the first collaborative object and restore the access entry of the first collaborative object in the access interface.

[0028] In one possible implementation, the device further includes: The identifier display module is used to respond to receiving a search request for the first collaborative object in the search interface and displaying the first collaborative object in the search results, and to display the identifier information of the target collaborative space in the search results according to the attribution identifier.

[0029] Thirdly, this application provides an electronic device, including: a processor and a memory, wherein the processor is configured to execute a cooperative program stored in the memory to implement the cooperative method described in any one of the first aspects.

[0030] Fourthly, this application provides a storage medium storing one or more programs that can be executed by one or more processors to implement the collaborative method described in any of the first aspects.

[0031] Compared with the prior art, the technical solution provided in this application has the following advantages: The method provided in this application, in response to the operation of adding a first collaborative object to the target collaborative space, creates an ownership identifier for the first collaborative object to indicate that it belongs to the target collaborative space, and displays the access entry of the first collaborative object in the interface of the target collaborative space based on the ownership identifier. This allows users to directly access the first collaborative object in the collaborative space without frequently switching between the interface of the collaborative space and other interfaces of the collaborative platform (the native interface of the first collaborative object). This aggregates the originally scattered entry points of the first collaborative object to the space interface, allowing users to simultaneously obtain other collaborative resources in the collaborative space in the same interface. This effectively improves the context fragmentation problem caused by interface switching and improves collaboration efficiency. At the same time, by managing the collaborative members of the first collaborative object and the collaborative members of the target collaborative space, the problem of duplicate maintenance and inconsistency of member information in two independent sets is avoided, reducing the management complexity of collaboration. Therefore, this application realizes the aggregation of entry points for collaborative objects and the integrated management of members, solving the technical problems of scattered operation paths and fragmented contexts caused by the independence of collaborative objects such as group chats and team spaces and the lack of a unified management mechanism in the existing technology. It improves collaboration efficiency while reducing operational complexity and maintenance costs. Attached Figure Description

[0032] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0033] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0034] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0035] Figure 1 A flowchart illustrating an embodiment of a collaborative method provided in this application; Figure 2 This is a schematic diagram illustrating an application scenario involved in an embodiment of this application; Figure 3 A flowchart illustrating an embodiment of another collaborative method provided in this application; Figure 4A block diagram illustrating an embodiment of a collaborative device provided in this application; Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0036] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0037] The following disclosure provides numerous different embodiments or examples for implementing various structures of this application. To simplify the disclosure, specific examples of components and arrangements are described below. These are merely examples and are not intended to limit the scope of this application. Furthermore, reference numerals and / or letters may be repeated in different examples. Such repetition is for simplification and clarity and does not in itself indicate a relationship between the various embodiments and / or arrangements discussed.

[0038] To address the technical problems in existing technologies where group chats and team spaces are independent and lack a unified management mechanism, leading to users frequently switching between the global message interface and the team space interface of the team collaboration platform, resulting in fragmented operation paths and contextual separation, and failing to meet the needs of integrated and centralized team collaboration, this application provides a collaboration method, device, and storage medium. This method enables the aggregation of entry points for collaboration objects and integrated management of members, solving the technical problems of fragmented operation paths and contextual separation caused by the independence of collaboration objects such as group chats from team spaces and the lack of a unified management mechanism in existing technologies. It improves collaboration efficiency while reducing operational complexity and maintenance costs.

[0039] Figure 1 This is a flowchart illustrating an embodiment of a collaborative method provided in this application. Figure 1 As shown, the method includes the following steps: Step 101: In response to the operation of adding the first collaboration object to the target collaboration space, create an ownership identifier for the first collaboration object. The ownership identifier is used to indicate that the first collaboration object belongs to the target collaboration space.

[0040] Step 102: Based on the affiliation identifier, display the access entry of the first collaborative object in the interface of the target collaborative space, and manage the collaborative members of the first collaborative object and the collaborative members of the target collaborative space.

[0041] For ease of understanding, steps 101 and 102 are explained uniformly below: First, the collaboration space is an aggregated collaboration container used to organize, host, and uniformly manage various types of collaborative resources. In existing technologies, collaboration spaces can only manage static resources such as documents, tasks, and files, while instant messaging group chats, as dynamic communication tools, remain independent of the collaboration space. Users must frequently switch between the global message interface of the collaboration platform and the collaboration space interface, making it impossible to complete communication and business operations within the same context. This application overcomes these limitations by incorporating instant messaging group chats into the management scope of the collaboration space. Specifically, in the technical solution provided in this application's embodiments, the collaboration space supports dynamically adding, removing, and associating various collaborative resources, and possesses an independent member system, permission control system, and unified access entry. It can centrally display, allocate permissions, manage members, and control the lifecycle of all collaborative resources within the space (including instant messaging group chats), achieving contextual association and integrated collaboration across resource types.

[0042] In one exemplary application scenario of this application, the first collaborative object refers to an instant messaging group chat. As the most frequent communication medium in team collaboration, group chats are characterized by having an independent set of members and an access point (i.e., a session entry point in the global message list). In the technical solution of this application, when a group chat is added to the collaboration space, an ownership identifier is created for it, establishing an ownership relationship between the group chat and the collaboration space. This allows the access point of the group chat to converge from the global message list to the collaboration space interface, enabling unified management of its members with other space members. This breaks down the barriers between communication and business operations, allowing users to complete a complete workflow from message communication to document collaboration and task processing within the collaboration space.

[0043] Furthermore, building upon the aforementioned collaborative space, this application also provides a mechanism for managing the association between resources and group chats. This not only categorizes group chats within the collaborative space but also establishes connections between group chats and specific resources within that space. For example, when a user adds a group chat to a collaborative space, they can associate it with resources such as documents, tasks, and schedules within the space. This allows users to quickly access resources related to the group chat while communicating within it; conversely, users can quickly locate associated group chat sessions when viewing documents or tasks. Through this association management, group chats are no longer isolated communication tools but form an organic whole with various resources within the space, thereby further strengthening the contextual association capabilities of the collaborative space and improving user collaboration efficiency within the space.

[0044] Building upon this foundation, the technical solution of this application can extend the first collaborative object to other types of collaborative entities, such as document entities (online documents, spreadsheets, presentations, PDFs, mind maps, etc., used for content creation and collaborative editing), task management entities (to-do items, task lists, project milestones, Kanban cards, etc., used for work progress tracking), schedule entities (calendar events, meeting appointments, reminders, etc., used for time scheduling and notifications), file entities (cloud files, folders, knowledge base entries, etc., used for data storage and sharing), data table entities (database tables, forms, multidimensional tables, etc., used for structured data collection and management), and application entities (third-party integrated applications, mini-programs, plugin instances, etc., used to expand space functionality). The common core characteristic of these various collaborative entities is that they each possess an independent set of collaborative members and access points, and belong to the same application system (such as a collaborative platform) as the collaborative space. Therefore, they can all be seamlessly integrated into the collaborative space for unified management through the same attribution identification mechanism.

[0045] Taking document-type entities as an example, suppose the first collaborative object is an online document (such as a project requirements document). In existing technologies, this online document is similar to a group chat, with an independent access point (such as a document list in a document management interface) and an independent set of members (such as document viewers, commenters, and editors). When users need to discuss the document, they usually need to switch between the document interface and the group chat interface, and the communication content is disconnected from the document content, making it difficult to form a contextual association.

[0046] In this embodiment, the online document can be added to the target collaboration space. After the online document is added, its access point is displayed in the target collaboration space's interface (e.g., in the directory tree or document list on the left side of the space). Simultaneously, the member set of the online document is managed uniformly with the member set of the collaboration space. Therefore, users can access the online document through the target collaboration space's interface. When a user opens the online document within the target collaboration space, they can simultaneously view other resources within the space, such as group chats, task lists, or schedules related to the document.

[0047] Through the above mechanism, the originally independent online documents are seamlessly integrated into the management system of the collaboration space. Their access point is aggregated with other resources in the space on the same interface, and their members are managed in an integrated manner with space members. Users do not need to frequently switch between the document interface and the space interface to complete collaborative activities such as document editing, communication and discussion, and task assignment in the same context, which significantly improves collaboration efficiency.

[0048] Therefore, in the technical solution provided in this application embodiment, the collaborative space can still dynamically accept and manage at least one type of collaborative entity after its creation, and converge the access entry of each collaborative entity belonging to the collaborative space into the space interface, while uniformly managing the collaborative members of the collaborative entity and the collaborative members of the space. The interface of the target collaborative space is independent of the native interface of the collaborative entity itself. Once a collaborative entity belongs to the collaborative space, the user can access, interact with, and manage the collaborative entity within that collaborative space.

[0049] In summary, the Collaboration Space is not merely a simple folder or tag categorization, but a comprehensive collaborative environment with ownership identification control, unified member management, adherence to permission rules, and the aggregation, display, and interaction of various types of collaborative entities. The Collaboration Space enables various collaborative entities that were originally scattered across different interfaces to coexist and operate collaboratively within a unified context, thereby significantly improving team collaboration efficiency.

[0050] Based on the above concepts, in the specific implementation of step 101, when it is detected that a user performs an operation to add the first collaborative object to the target collaborative space, an ownership identifier is created for the first collaborative object in response to this operation. The "add operation" mentioned here includes the user's behavior of introducing an existing collaborative entity into the collaborative space through methods such as adding via the space's add menu, dragging and dropping, or sharing via a link. The "ownership identifier" is a data field or label, which can be a space ID or a pointer to a space record, used to indicate which target collaborative space the first collaborative object specifically belongs to. "Belonging to" means that a logical subordinate relationship has been established between the first collaborative object and the target collaborative space, and subsequent behaviors such as the lifecycle, access rules, and member management of the first collaborative object will be partially controlled by the target collaborative space.

[0051] In the specific implementation of step 102, two related actions are performed based on the ownership identifier created in step 101: First, the access entry for the first collaboration object is displayed in the interface of the target collaboration space. Specifically, the ownership identifier of the first collaboration object is read to determine which collaboration space it belongs to, and then the access entry for that collaboration space is displayed. The access entry refers to the interface element that allows the user to enter and interact with the first collaboration object after clicking, such as a session list item, document card, or icon in the space interface. The interface of the target collaboration space is the main interface of the space or a dedicated area within the space, used to display the access entries for all collaboration objects belonging to that space. It is independent of the collaboration object's own access interface (its inherent interface for displaying and accessing the collaboration object before it is added to any collaboration space, such as the global message list). By rendering the access entry for the first collaboration object in the interface of the target collaboration space, users can directly click to enter the first collaboration object from within the target collaboration space.

[0052] Second, manage the collaborative members of the first collaborative object and the collaborative members of the target collaborative space. Collaborative members refer to individuals with access permissions who participate in collaboration. The first collaborative object has its own set of collaborative members (such as a group chat member list), and the target collaborative space also has its own set of collaborative members (such as a space member list). "Managing the collaborative members of the first collaborative object and the collaborative members of the target collaborative space" means treating these two sets of collaborative members as a logical whole and maintaining consistency. This includes operations such as adding members to each other when they join, removing members from each other when they leave, uniformly applying permission rules, and synchronizing member roles consistently. The purpose is to avoid inconsistencies in member data and reduce management complexity.

[0053] Therefore, step 102 achieves unification of collaborative objects in two dimensions: access path and personnel management. Specifically, "unified entry point" moves the access entry point from the access interface of the first collaborative object itself to the space interface, enabling users to access all collaborative objects belonging to that space from within the collaborative space. "Unified member management" links two originally independent sets of collaborative members, ensuring that member identities remain consistent across collaborative objects and collaborative spaces, and that permission rules can be applied across resources.

[0054] Furthermore, in one embodiment, a collaborative object can be added to one or more collaborative spaces. Specifically, when a collaborative object is added to a target collaborative space, an ownership identifier corresponding to the target collaborative space is created for the collaborative object to establish an ownership relationship between the two. If the same collaborative object is subsequently added to another collaborative space (e.g., a second collaborative space), an additional ownership identifier corresponding to the second collaborative space is created for the collaborative object. In other words, a collaborative object can have multiple ownership identifiers simultaneously, each pointing to a different collaborative space. Accordingly, the access entry for the collaborative object will be displayed in the interface of each collaborative space to which it belongs, and users can enter the collaborative object and interact from any of the collaborative spaces. By supporting multi-space ownership of collaborative objects, the embodiments of this application further enhance the flexibility of collaboration, enabling the same collaborative entity to be reused in different collaborative contexts, meeting the needs of complex collaborative scenarios such as cross-team and cross-project collaborations.

[0055] See Figure 2 This is a schematic diagram illustrating a collaborative object processing method provided in an embodiment of this application. Figure 2 As shown, V5.16 requirement communication is a group chat message, which was originally displayed in a separate access interface (i.e., the message list interface). Here, "separate" refers to its location relative to the collaboration space. By adding the collaboration object to the collaboration space... Figure 2 The operation of the team space in the system displays the access point of the group chat in the interface of the team space, thereby converging the access point of the collaborating object from its own access interface to the interface of the collaboration space. This realizes the context association between the group chat and other resources (such as documents, tasks, etc.) in the space, and provides a unified entry point for subsequent unified member management, message notification routing, and permission rule inheritance.

[0056] Based on the above embodiments, this application also provides an optional implementation method for role identification and permission visualization of members within a collaborative space. Specifically, in addition to unified management of collaborative objects, the target collaborative space also assigns identity tags to collaborative members within the space. Identity tags are used to characterize the role or permissions of collaborative members within the target collaborative space, such as "person in charge," "designer," "developer," "read-only member," etc. Identity tags can be set by collaborative members themselves within the scope set by the administrator, or they can be uniformly set or assigned by the administrator of the target collaborative space.

[0057] In the collaboration space interface, identity tags are displayed in association with corresponding collaborating members. Display locations include, but are not limited to: next to member entries in the space member list, in interactive windows of collaborating objects (such as next to member nicknames in group chats), near message input boxes, in document comment areas, and in task assignment interfaces. By displaying identity tags in multiple locations, other members can quickly understand a member's role in the space during communication and collaboration, helping to determine the authority of messages and clarify task responsibilities, thereby reducing communication costs in collaboration.

[0058] In scenarios involving task assignment or member mentions, intelligent recommendations can also be made based on member identity tags. For example, when a user triggers a task assignment in a space, members with corresponding role tags can be recommended to the user based on the degree of matching between the task content and identity tags (e.g., recommending a design task to a member tagged "designer"); when a user mentions a member in a group chat, the system can prompt whether the currently mentioned member has the corresponding responsibility to handle the topic based on their identity tags.

[0059] In addition, identity tags can be associated with specific permission granularities. The permissions associated with an identity tag include, but are not limited to, at least one of the following: resource access permissions, used to control a member's viewing or editing rights to specific resources within the space; operation permissions, used to control a member's ability to perform specific operations within the space, such as inviting new members, deleting collaborative resources, and modifying space settings; and notification permissions, used to control a member's permission to receive specific types of notifications within the space, for example, a member can choose whether to receive message notifications from certain types of collaborators. Members can adjust some permission settings according to their own work habits within the permission scope set by the administrator (such as disabling notifications for a non-priority group chat), while the administrator can uniformly configure the permission scope corresponding to each identity tag at a global level.

[0060] Through the aforementioned identity tagging mechanism, this application, on the basis of realizing spatial affiliation management of collaborative objects, further provides a visual auxiliary means for member management and permission control within the space, which together with the affiliation identifier constitutes the management link of collaborative space permissions.

[0061] The technical solution provided in this application, in response to the operation of adding a first collaborative object to a target collaborative space, creates an ownership identifier for the first collaborative object to indicate that it belongs to the target collaborative space, and displays the access entry of the first collaborative object in the interface of the target collaborative space based on the ownership identifier. This allows users to directly access the first collaborative object within the collaborative space without frequently switching between the interface of the collaborative space and other interfaces of the collaborative platform (the native interface of the first collaborative object). This aggregates the originally scattered entry points of the first collaborative object into the space interface, allowing users to simultaneously access other collaborative resources within the collaborative space from the same interface, effectively improving the context fragmentation problem caused by interface switching and increasing collaboration efficiency. Simultaneously, by managing the collaborative members of the first collaborative object and the collaborative members of the target collaborative space, the duplicate maintenance and inconsistency of member information in two independent sets are avoided, reducing the management complexity of collaboration. Therefore, this application achieves the aggregation of collaborative object entry points and integrated member management, solving the technical problems of scattered operation paths and context fragmentation caused by the independence of collaborative objects such as group chats and team spaces and the lack of a unified management mechanism in the prior art. This improves collaboration efficiency while reducing operational complexity and maintenance costs.

[0062] In one embodiment, before creating an ownership identifier for the first collaborative object, the method further includes: obtaining the permission information of the user initiating the operation in the first collaborative object; if the permission information indicates that the user has management permissions for the first collaborative object, performing the step of creating an ownership identifier for the first collaborative object; if the permission information indicates that the user does not have management permissions for the first collaborative object, sending an add request to the administrator of the first collaborative object, and after receiving the administrator's confirmation instruction, performing the step of creating an ownership identifier for the first collaborative object.

[0063] To ensure the legitimacy of adding the first collaboration object to the target collaboration space and prevent unauthorized users from arbitrarily introducing the first collaboration object, a permission verification process is performed before creating an ownership identifier for the first collaboration object. Specifically, when a user triggers an add operation, the user's permission information within the first collaboration object is first retrieved. This permission information is used to determine whether the user is the administrator of the first collaboration object. For example, in a group chat scenario, the administrator is the group owner; in a document scenario, the administrator is the document owner or a collaborator granted management permissions.

[0064] If the obtained permission information indicates that the user has management permissions for the first collaborative object, then the user has the right to determine the ownership of the first collaborative object, and the subsequent ownership identification creation steps will be executed directly to formally add the first collaborative object to the target collaboration space. Conversely, if the permission information indicates that the user does not have management permissions (for example, the user is only a regular member of the group chat or a read-only viewer of the document), the addition operation will not be executed directly. Instead, an addition request will be sent to the actual administrator of the first collaborative object. This request may include the applicant's identity information, the desired target collaboration space information, and the reason for adding the object.

[0065] After receiving a request, the administrator can choose to approve or reject it. Only after the administrator issues a confirmation (approval) will the process continue to create an ownership identifier for the first collaborative object, completing the addition operation. If the administrator rejects the request or fails to respond within the timeout period, the addition operation will terminate, and the first collaborative object will not be added to the target collaboration space.

[0066] Through the aforementioned permission verification mechanism, this embodiment achieves flexible addition of collaborative objects while ensuring the control of the administrator of the collaborative object. This not only prevents data chaos that may be caused by unauthorized operations, but also provides a standardized application channel for non-administrators, thus balancing security and collaboration efficiency.

[0067] In one embodiment, managing the collaborative members of the first collaborative object and the collaborative members of the target collaborative space includes: assigning the collaborative members of the first collaborative object to the target collaborative space, and determining the access rights of the collaborative members of the first collaborative object to resources within the target collaborative space according to the permission rules of the target collaborative space.

[0068] In this context, incorporating the collaborating members of the first collaborating object into the target collaborating space means integrating the original set of members of the first collaborating object into the member system of the target collaborating space. This allows these members to automatically acquire the identity of collaborating members within the space, eliminating the need for duplicate additions within the collaborating space. Furthermore, instead of setting a new set of permissions for these members, the existing permission rules of the target collaborating space are directly adopted, achieving a unified and reusable permission system.

[0069] For example, the roles and permission groups of members assigned to the target collaboration space are determined according to preset default rules: When a member of the first collaboration object is automatically assigned to the target collaboration space, if the member does not yet belong to the target collaboration space, a default member role (such as a regular member) is assigned to them; if the first collaboration object includes management members (such as group owners or document owners), these management members can be automatically matched to the administrator or co-administrator roles of the target collaboration space according to mapping rules, thus achieving automatic correspondence between member identity and space role. After automatic assignment is completed, the administrator of the target collaboration space can manually adjust the space roles, permission groups, or fine-grained permissions of the assigned members according to actual collaboration needs, including modifying member roles, adding or removing permissions, removing members from the space, or adjusting the access scope of specific resources within the space, thereby supporting flexible custom permission configuration on the basis of automatic unified management.

[0070] For example, multiple member roles (such as administrator, regular member, visitor, etc.) can be preset in the target collaboration space, and corresponding resource access permissions (such as viewing, editing, managing, deleting, sharing, etc.) can be configured for different roles. Fine-grained permission policies can also be set for different collaborative resources such as documents, folders, group chats, and tasks. When the members of the first collaboration object are assigned to the target collaboration space, their space roles and permissions are automatically determined according to the above default rules. Administrators can subsequently manually modify member roles, individually grant or restrict a member's access to specific collaborative resources, balancing the efficiency of permission configuration with the flexibility of collaboration scenarios.

[0071] By automatically assigning members to new accounts, granting permissions according to default rules, and then allowing for manual adjustments, this embodiment achieves seamless integration of member identity and permission management. This avoids the tedious process of configuring permissions for each newly added member, while meeting the flexible management needs of diverse collaboration scenarios. It also ensures that sensitive resources within the space are not accidentally exposed due to the addition of new members, thereby improving management efficiency while protecting data security.

[0072] In one embodiment, managing the collaborative members of the first collaborative object and the collaborative members of the target collaborative space includes: in response to a user joining the collaborative member set of the first collaborative object, adding the user to the collaborative member set of the target collaborative space; or, in response to a user leaving the collaborative member set of the target collaborative space, removing the user from the collaborative member set of the first collaborative object.

[0073] The above steps enable bidirectional, interconnected updates between the two sets of collaborative members. Specifically, when a user joins the first collaborative object (e.g., invited to a group chat or granted document access), the system automatically checks if the user is already a member of the target collaborative space. If the user is not yet a member of the target collaborative space, they are automatically added to the space's member set, ensuring that users who can access the collaborative object can simultaneously gain access to other collaborative resources within the space, eliminating the need for manual addition and maintenance by the space administrator. On the other hand, when a user actively leaves the target collaborative space (e.g., leaves the team or project), the user is automatically removed from the first collaborative object's member set, preventing users who have left the space from continuing to access collaborative objects, receive messages, or retain operational permissions, thus ensuring clear permission boundaries and data security.

[0074] In one embodiment, when a user leaves the first collaboration object, they are not automatically removed from the target collaboration space. For example, a user may only wish to leave a group chat or revoke permissions for a specific document, but still retain normal access and operation permissions for other collaborative resources such as documents, tasks, and files within the space. By distinguishing between the two different operations of "leaving the collaboration object" and "leaving the collaboration space," fine-grained control over member management is achieved.

[0075] Through the aforementioned two-way linkage and differentiated exit rules, this embodiment can maintain the consistency of data between collaborative objects and members of the collaborative space, reduce manual maintenance costs, and meet users' permission control needs in different collaborative scenarios, taking into account both management convenience and usage flexibility.

[0076] Furthermore, in practical applications, to further enhance operational transparency and user experience, a member change notification mechanism can be set up. For example, when a user is automatically added to a collaboration space, they can receive a real-time addition notification; when they are removed from a collaboration space or associated collaboration objects, they can receive a corresponding removal notification. Simultaneously, member change reminders can be displayed in the collaboration space interface, such as "So-and-so added member X to this space" or "So-and-so removed member X from this space," enabling administrators and relevant members to clearly understand member changes and improving the traceability and transparency of collaboration management.

[0077] In one embodiment, the method provided in this application further includes: in response to the operation of deleting the target collaboration space, obtaining a preset collaboration object processing strategy; and determining a disposal operation for the first collaboration object according to the collaboration object processing strategy. The disposal operation includes at least one of the following: disbanding the first collaboration object and terminating the ownership relationship between the first collaboration object and the target collaboration space; retaining the first collaboration object and clearing its ownership identifier; and updating the ownership identifier of the first collaboration object to point to another collaboration space.

[0078] This embodiment provides a unified handling mechanism for collaborative objects in the scenario of deleting a collaborative space. Specifically, in response to a user-triggered operation to delete a target collaborative space, a pre-configured collaborative object handling strategy is first obtained, and then the corresponding handling operation for the first collaborative object is automatically executed according to the strategy, thereby realizing the linkage management and control of the collaborative space lifecycle and the internal collaborative object lifecycle.

[0079] The handling operations for the first collaborative object include at least one of the following: First, disband the first collaborative object and simultaneously terminate the established affiliation relationship between the collaborative object and the target collaborative space, and thoroughly clean up the associated data after the space is deleted; Second, retain the first collaborative object, only remove its affiliation identifier, so that the collaborative object is restored to an independent state and no longer belongs to any collaborative space; Third, update the affiliation identifier of the first collaborative object to point to another designated collaborative space, so as to realize the migration and acceptance of the collaborative object between different collaborative spaces.

[0080] The configurable handling strategies described above can adapt to various business scenarios after space deletion, ensuring both the standardization and security of data processing, while also meeting users' flexible management needs for retaining, migrating, or cleaning up collaborative objects, thereby improving the controllability and applicability of the entire collaboration system.

[0081] Furthermore, as an optional implementation, the aforementioned collaborative object handling strategy can be actively selected by the user. After triggering the operation to delete the target collaborative space, various collaborative object handling strategies are displayed to the user through interactive methods such as pop-ups, drop-down selections, or configuration panels, allowing the user to select the target strategy based on actual business needs. Based on the user-selected strategy, the corresponding collaborative object disposal operation is executed, further improving the controllability and flexibility of the space deletion process.

[0082] Figure 3 A flowchart illustrating an embodiment of another collaborative method provided in this application. Figure 3 The process shown is in Figure 1 Based on the illustrated process, the following steps are included: Step 301: In response to the operation of adding the first collaboration object to the target collaboration space, create an ownership identifier for the first collaboration object. The ownership identifier is used to indicate that the first collaboration object belongs to the target collaboration space.

[0083] Step 302: Based on the affiliation identifier, display the access entry of the first collaborative object in the interface of the target collaborative space, and manage the collaborative members of the first collaborative object and the collaborative members of the target collaborative space.

[0084] For a detailed description of steps 301 and 302, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0085] Step 303: Based on the ownership identifier, hide the access entry of the first collaborative object in the access interface of the first collaborative object.

[0086] The access interface of the first collaborative object refers to the global-level, independent access interface of the first collaborative object when it does not belong to any collaborative space, such as the global message list, global recent document list, global file list, and global task list of instant messaging. This access interface is independent and isolated from the exclusive interface of the target collaborative space.

[0087] After the first collaborative object belongs to the target collaborative space, based on the ownership identifier it carries, it is identified that the collaborative object has been included in the unified management of the collaborative space. Then, the access entry of the collaborative object in the above-mentioned access interface is hidden, so that it is no longer displayed, clickable, or searchable.

[0088] By hiding the access entry point of the first collaborative object in the access interface of the first collaborative object, the access path of the first collaborative object can be uniquely converged to the target collaborative space interface. This avoids access confusion, context fragmentation and data management chaos caused by the same collaborative object appearing repeatedly in multiple paths and multiple interfaces. It ensures that users can only enter and use the collaborative object through the target collaborative space, realizing the unification, clarity and controllability of the access link, and improving the continuity of team collaboration and management efficiency.

[0089] Based on step 303, this application also provides the following embodiments: In one embodiment, the method provided in this application further includes: in response to the generation of a new message from a first collaborating object, displaying a message notification of the new message in the interface of the target collaborating space according to the attribution identifier.

[0090] Building upon step 303, which hides the access entry point of the first collaborative object in its access interface, this embodiment further implements unified management of new message notifications. Specifically, in response to the generation of a new message from the first collaborative object, the target collaborative space to which the first collaborative object belongs is determined based on its ownership identifier, and the message notification corresponding to the new message is displayed in the interface of the target collaborative space, rather than in the access interface of the first collaborative object.

[0091] Message notifications can be presented using visual cues such as red dots, underline numbers, and unread counts.

[0092] By unifying new message notifications to the target collaboration space interface, it ensures that users only receive and view unread notifications for that collaboration object within the space interface. This avoids message notifications appearing repeatedly in the global native interface and the space interface, and prevents the source from being scattered. It further ensures the consistency of access paths and message notifications, allowing users to process messages within a unified collaboration space context, thus improving usability and operational efficiency.

[0093] Furthermore, in one embodiment, the method provided in this application further includes: in response to receiving an access request pointing to the first collaborative object in the access interface of the first collaborative object, outputting a jump prompt message to guide the user to access the first collaborative object through the target collaborative space.

[0094] Building upon step 303, which hides the access entry point for the first collaborative object in its own access interface, this embodiment further provides an access guidance mechanism. Specifically, in response to receiving an access request pointing to the first collaborative object in the access interface of the first collaborative object, a redirection prompt is output to guide the user to switch to the target collaborative space to access the first collaborative object. Specifically, when a user attempts to access a first collaborative object belonging to the target collaborative space through history, search results, shortcuts, etc., from the access interface where the access entry point is hidden, the access source will be determined to be invalid based on the ownership identifier. A redirection prompt will then be output in the form of a pop-up window, text prompt, or page guidance to inform the user that the collaborative object has been included in the management of the target collaborative space and needs to be accessed within the corresponding collaborative space. This avoids access failures and path confusion, ensures the integrity of the unified access link, and improves the user experience and clarity of operation guidance.

[0095] In a further embodiment, the method provided in this application further includes: in response to receiving an access request to a first collaborative object via an external link, redirecting the access request to the interface of the target collaborative space according to the attribution identifier, and locating the interactive window of the first collaborative object in the interface of the target collaborative space.

[0096] External links include, but are not limited to, external access points such as QR code links, email links, shareable links, and message card links. When a user accesses the first collaborative object (such as a group chat, document, or task) belonging to the target collaboration space through external methods such as scanning a QR code, clicking an email link, or opening a shareable link, the target collaboration space to which the collaborative object belongs is identified based on the ownership identifier carried by the collaborative object. Instead of directly opening the isolated native page of the collaborative object, the access request is automatically redirected to the interface of the target collaboration space, and the interactive window of the first collaborative object is directly located and opened within that space interface.

[0097] For example, when a user accesses a group chat by scanning a QR code or email link, they are automatically redirected to the collaboration space interface to which the group chat belongs and directly enter the group chat window.

[0098] Through the aforementioned unified external access redirection mechanism, regardless of the external entry point from which a user initiates access, they are ultimately guided to a unified collaboration space interface, ensuring a consistent user experience and reducing user operational and cognitive costs. Furthermore, users do not enter isolated collaboration object windows, but rather a unified interface with a complete spatial context. Resources such as documents, tasks, files, and schedules within the collaboration space are directly accessible, effectively strengthening the contextual association between collaboration objects and spatial resources, and improving the efficiency of information retrieval and collaborative operations.

[0099] Step 304: Display the space access entry corresponding to the target collaboration space in the access interface of the first collaboration object.

[0100] In step 304, a space access entry corresponding to the target collaboration space is displayed on the access interface of the first collaboration object itself, guiding the user to enter the target collaboration space from this access interface. The purpose of establishing this space access entry is to ensure that the user can still perceive that the first collaboration object has been included in a collaboration space within the first collaboration object's access interface, and can quickly enter the collaboration space through this space access entry to view and process the content of the collaboration object within the collaboration space context. Thus, even if the original access entry of the first collaboration object in its own access interface is hidden, the user can still conveniently enter the target collaboration space through this space access entry, view and process the content of the first collaboration object within the complete space context, avoiding access path interruption caused by the hidden entry, while maintaining the user's clear perception of the ownership relationship between the first collaboration object and the target collaboration space.

[0101] Furthermore, since the first collaborative object may belong to multiple collaborative spaces simultaneously, this involves handling the situation where multiple space access points coexist. Therefore, this application provides two optional implementation methods: As an optional implementation, the space access entrances corresponding to multiple target collaboration spaces are displayed side by side in the native interface, and each space access entrance independently displays the unread message reminder of the first collaboration object in the corresponding target collaboration space.

[0102] In this implementation, when a first collaborative object belongs to multiple collaborative spaces, an independent access entry is generated for each collaborative space in the first collaborative object's access interface, with multiple entries displayed side-by-side. Each entry independently displays the identifier of its corresponding collaborative space (such as the space name or icon) and independently displays the unread message notifications for the first collaborative object within that collaborative space (such as the number of unread messages). Users can intuitively see in this access interface which collaborative spaces the first collaborative object has been added to, and how many unread messages the collaborative object has in each space. Clicking on any space access entry will directly jump to the corresponding collaborative space interface and locate the first collaborative object's interaction window.

[0103] The advantage of this implementation is that users can clearly see the unread status of multiple spaces, selectively enter the space that needs to be processed, and the operation path is direct and clear. It is suitable for scenarios where users participate in multiple spaces at the same time and need to distinguish and process messages from different spaces.

[0104] As another optional implementation, an aggregated space access portal is displayed in the original interface. This aggregated space access portal displays the total number of unread messages for multiple target collaboration spaces. In response to triggering the aggregated space access portal, a list of multiple target collaboration spaces is displayed for the user to select.

[0105] In this implementation, when a first collaborative object belongs to multiple collaborative spaces, only one aggregated space access entry is displayed on the first collaborative object's access interface. This aggregated entry does not display individual information for each space, but instead uniformly displays the total number of unread messages for the first collaborative object across all its affiliated collaborative spaces. After the user clicks this aggregated entry, they are not directly redirected to a specific collaborative space. Instead, a list containing multiple collaborative spaces is first displayed, with each entry in the list corresponding to a collaborative space and displaying the space's name and the number of unread messages for the first collaborative object within that space. After the user selects a collaborative space from the list, they are redirected to that collaborative space's interface and then directed to the first collaborative object's interaction window.

[0106] The advantages of this implementation method are: the interface is simpler, avoiding visual clutter caused by multiple entrances appearing at the same time, which is suitable for scenarios with more user participation space or limited interface space; at the same time, by allowing users to make choices through the intermediate list, it avoids the trouble of "going to the wrong space" that may be caused by direct jumping.

[0107] Furthermore, based on step 304, this application also provides the following embodiments: In one embodiment, the method provided in this application further includes: in response to the generation of a new message by the first collaborating object in the target collaborating space, displaying a message reminder of the new message at the space access entry point according to the ownership identifier.

[0108] Building upon the established space access entry point, this embodiment further provides logic for displaying message notifications at the space access entry point. Specifically, when a first collaborating object generates a new message in a target collaborating space, the system determines which target collaborating space the new message belongs to based on the first collaborating object's ownership identifier, and displays a message notification for the new message at the space access entry point corresponding to that target collaborating space. Here, "message notification" can take the form of an unread count badge, a red dot, a message summary, etc.

[0109] Since the first collaborative object may belong to multiple collaborative spaces, each space access entry independently displays the unread message reminder of the first collaborative object in its corresponding collaborative space, so that users can know the unread status of the collaborative object in each space without entering each collaborative space in the access interface of the first collaborative object.

[0110] This embodiment enables refined presentation of message notifications at the space access entry level, further improving the user's perception efficiency of unread messages in multi-space ownership scenarios.

[0111] In one embodiment, the method provided in this application further includes: in response to triggering the space access entry, jumping to the interface of the target collaborative space and locating the interaction window of the first collaborative object.

[0112] Building upon the above embodiments, this embodiment further provides response logic after a user triggers a space access entry. Specifically, when a user triggers (e.g., clicks, touches, etc.) a space access entry corresponding to the target collaboration space within the access interface of the first collaboration object, in response to this triggering operation, the user is redirected from the current interface to the interface of the target collaboration space, and automatically located in the interaction window of the first collaboration object within that space interface. Here, "location" refers to automatically selecting or highlighting the first collaboration object in the space interface, allowing the user to directly enter the session or content interface of the first collaboration object without manually searching in the collaboration object directory or list within the space.

[0113] This implementation ensures a seamless transition for users from the space access portal to the collaborative space, eliminating the need for users to manually search for target collaborative objects after entering the space, and significantly improving the efficiency and experience of cross-interface access.

[0114] Figure 3 The illustrated embodiment is in Figure 1Building upon the illustrated embodiment, the original access entry point of the first collaborative object is further hidden in its access interface, and a spatial access entry point corresponding to the target collaborative space is set. This ensures that the access path of the first collaborative object is uniformly converged to the collaborative space interface. Simultaneously, users can still perceive and enter the target collaborative space through the spatial access entry point in the first collaborative object's own access interface, eliminating the access interruption problem that might occur due to the complete hiding of the entry point. The synergistic cooperation of these two entry point control methods (hiding the original entry point and adding a spatial entry point) ensures the consistency of the path with the collaborative space as the sole access entry point, reduces the cognitive cost for users regarding changes in the ownership of collaborative objects, and improves the flexibility and fault tolerance of cross-interface access.

[0115] Finally, this application also provides the following embodiments: In one embodiment, in response to receiving a search request for a first collaborative object in the search interface and displaying the first collaborative object in the search results, the identification information of the target collaborative space is displayed in the search results in association with the affiliation identifier.

[0116] The method provided in the above embodiments includes a collaborative object association display mechanism in search scenarios. Specifically, in response to receiving a search request for a first collaborative object in the global search interface or the in-application search interface, when the first collaborative object is matched and presented in the search results, the name, icon, or other space identification information of the target collaborative space to which the first collaborative object belongs will be read and displayed in the search results entry according to the ownership identifier carried by the first collaborative object.

[0117] By displaying the identifier of the target collaboration space in the search results, users can be intuitively informed of which collaboration space the collaboration object belongs to, guiding them to enter and access it from the target collaboration space. This further strengthens the unified access path, avoids path confusion caused by the search entry point, maintains the coherence of the collaboration context, and improves the readability and operational accuracy of search results.

[0118] In one embodiment, in the interface of the target collaboration space, collaboration objects that belong to the target collaboration space but have not yet been joined by the current account are displayed according to the ownership identifier; in response to the current account's joining of collaboration objects that have not yet been joined, the current account is added to the member set of the collaboration objects and the current account's session interface in the joined collaboration objects is displayed.

[0119] Within the target collaboration space interface, collaboration objects belonging to that space but not yet joined by the current user are displayed based on their affiliation identifier. The affiliation identifier determines the relationship between a collaboration object and the target collaboration space. By identifying this identifier, all collaboration objects belonging to that space but not yet joined by the current user can be filtered and displayed within the space interface. These collaboration objects can be displayed in a list format, card format, or marked with specific icons in a directory tree to distinguish them from already joined collaboration objects. Users do not need to actively search or obtain information about which collaboration objects exist within the space; they can intuitively see all collaboration objects belonging to that space but not yet joined directly within the space interface, thus achieving transparent display of collaboration objects within the space.

[0120] Based on this, in response to the current account's trigger action to join a collaboration object that has not yet been joined (such as clicking the "Request to Join" button or double-clicking the entry for that collaboration object), the current account is added to the member set of that collaboration object. If the collaboration object requires administrator approval, a join request is sent to the administrator of that collaboration object, and the current account is added to the member set of the collaboration object only after receiving confirmation from the administrator. After joining is complete, the current account's conversation interface in the joined collaboration object (such as a group chat window or document comment section) is displayed, allowing the user to immediately participate in communication and collaboration within that collaboration object.

[0121] Through the above mechanism, even if a user was not initially added to certain collaboration partners in the collaboration space, they can still discover and actively apply to join through the collaboration space interface. In this way, project-related group chats will not be missed, and important information will not be missed because the user is unaware that a certain group exists.

[0122] In one embodiment, in the interface of the target collaboration space, multiple collaboration objects belonging to the target collaboration space are grouped and displayed according to a preset classification dimension based on the attribute information associated with the affiliation identifier.

[0123] To facilitate users' efficient search and management of a large number of collaborative objects within a collaborative space, this application provides a mechanism for grouping and displaying collaborative objects based on attribute information associated with their affiliation identifiers. When multiple collaborative objects belong to the same target collaborative space, these collaborative objects are grouped according to preset classification dimensions based on the attribute information associated with each collaborative object's affiliation identifier, and the grouping results are displayed in the space interface.

[0124] The attribution identifier not only indicates the attribution relationship between a collaboration object and the collaboration space, but can also associate or carry the attribute information of the collaboration object, such as version identifier (e.g., v5.20, v5.19), requirement type (e.g., functional requirement, defect fix), stage status (e.g., in progress, archived, pending review), creation time (e.g., by week, by month), and custom tags (e.g., "urgent," "pending confirmation"). This attribute information is read, and collaboration objects are automatically categorized into corresponding groups based on preset classification dimensions. Preset classification dimensions can be directly determined based on attribute information; for example, all collaboration objects can be categorized into the corresponding version group according to the version identifier, and all collaboration objects can be categorized into groups such as "in progress" and "archived" according to the stage status. Each group can be expanded and displayed in the space interface in the form of a group title + member list. Users can manage the density of information presented on the interface by collapsing or expanding groups.

[0125] This grouping and display mechanism transforms collaborative objects within the collaboration space from simple, flat lists into organized entities based on user interests or business processes. Users no longer need to manually create folders or tags to organize objects, nor do they need to view each object individually to understand its version or status. They can quickly locate objects for specific versions, requirements, or stages from the interface. This implementation effectively solves the problem of inefficient resource management within the space caused by a large number and diverse types of collaborative objects. It is particularly suitable for large project teams with frequent version iterations and diverse requirements, significantly reducing the cognitive cost and operational time required for users to find and manage collaborative objects within the space.

[0126] In one embodiment, in response to detecting that the first collaborative object has not generated a new message within a preset time period, the first collaborative object is marked as archived in the interface of the target collaborative space; if the first collaborative object generates a new message, the archived state is de-archived.

[0127] In real-world team collaboration scenarios, certain collaboration objects (such as specific versions of group chats or group chats related to phased tasks) experience a significant decrease in usage frequency or even become inactive after a period of activity, as the corresponding phase ends. However, these collaboration objects may contain important historical discussion records or decision-making basis, which need to be retained for future review or auditing and should not be directly deleted. If these inactive collaboration objects are kept in the space's regular list, the number of collaboration objects in the space will continue to expand over time. Users will then need to sift through a large number of inactive collaboration objects to find currently active ones, severely reducing the efficiency of finding resources within the space.

[0128] To address this, this application provides an automatic archiving mechanism for collaborative objects. The activity status of each collaborative object belonging to the target collaborative space is detected. When a first collaborative object is found to have not generated any new messages within a preset time period (e.g., 30 or 60 days), it is determined that the first collaborative object has entered an inactive state and is automatically marked as archived in the target collaborative space interface. Collaborative objects in the archived state can be displayed in the space interface through methods such as collapsing groups, reducing display priority, and adding archive tags, so that they no longer occupy a prominent position in the regular list, thereby reducing interference with the user's daily operations. At the same time, they are still retained in the space, and users can expand the archived groups for review when needed.

[0129] Building upon this, when the first collaborating object generates a new message (e.g., a member speaks in the group chat), in response to this new message event, the collaborating object's archived status is automatically lifted, restoring it to the regular list and displaying it according to the normal sorting rules. Since the generation of a new message signifies that the collaborating object has re-entered an active state, automatic unarchiving ensures that users are promptly aware of the collaborating object's activity and can restore its normal display without manual intervention.

[0130] Through the above mechanism, this embodiment realizes the automated management of the life cycle of collaborative objects. They are displayed normally when active, automatically archived when inactive, and automatically restored when they become active again. While ensuring the traceability of historical data, it effectively controls the size of the regular list in the space and reduces the visual burden and information filtering cost for users.

[0131] In one embodiment, in response to the operation of removing the first collaborative object from the target collaborative space, the ownership identifier of the first collaborative object is cleared, and the access entry of the first collaborative object in the original access interface is restored.

[0132] During collaboration, users may need to remove a collaborative object from the target collaboration space, for example, if the object's relevance to the current project weakens, or if the object needs to be reassigned to another space. To address this scenario, this application provides a state restoration mechanism when a collaborative object is removed from a space.

[0133] Specifically, in response to a user's action of removing the first collaborative object from the target collaborative space, the ownership identifier of the first collaborative object is first cleared, severing its ownership relationship with the target collaborative space. After the ownership identifier is cleared, the first collaborative object is no longer subject to the target collaborative space's member management, permission rules, message notification routing, and other controls. Simultaneously, the access entry point for the first collaborative object in its original access interface is restored. Previously, because the first collaborative object was added to the target collaborative space, its access entry point in the original access interface had been hidden (see the aforementioned embodiment) to avoid multiple parallel entry points on the original access interface and the space interface, which could lead to user path confusion.

[0134] When the first collaborative object is removed from the space, its ownership relationship ceases to exist. Continuing to hide its entry point in the original access interface will prevent users from accessing the collaborative object from any location. Therefore, the access entry point for the first collaborative object in the original access interface is restored synchronously, allowing users to find and access the first collaborative object again from its original access interface.

[0135] This embodiment establishes a linkage control between the spatial ownership of collaborative objects and their original access entry points: when an object is added to a space, its original entry point is hidden, and access is uniformly controlled through the space's entry point; when an object is removed from a space, its original entry point is restored, ensuring that the access path is not lost. This bidirectional and reversible entry management mechanism guarantees path consistency during the collaboration process and allows users to flexibly adjust collaboration relationships according to actual needs, enhancing the system's fault tolerance and user experience.

[0136] Figure 4 This is a block diagram illustrating an embodiment of a collaborative device provided in this application. Figure 4 As shown, the device includes: The attribution identification module 41 is used to create an attribution identification for the first collaborative object in response to the operation of adding the first collaborative object to the target collaborative space. The attribution identification is used to indicate that the first collaborative object belongs to the target collaborative space. The entry display module 42 is used to display the access entry of the first collaborative object in the interface of the target collaborative space based on the ownership identifier; The member management module 43 is used to manage the collaborative members of the first collaborative object and the collaborative members of the target collaborative space.

[0137] In one possible implementation, the device further includes: An entry hiding module is used to hide the access entry of the first collaborative object in the access interface of the first collaborative object based on the ownership identifier; wherein the access interface of the first collaborative object is independent of the interface of the target collaborative space.

[0138] In one possible implementation, the device further includes: The new message notification module is used to respond to the generation of a new message from the first collaborating object and, based on the attribution identifier, display a message notification of the new message in the interface of the target collaborating space.

[0139] In one possible implementation, the device further includes: The access entry setting module is used to set the space access entry corresponding to the target collaboration space in the access interface of the first collaboration object; The new message notification module is used to respond to the generation of a new message by the first collaborating object in the target collaboration space, and display a message notification of the new message at the space access entry according to the ownership identifier; The jump module is used to respond to the triggering of the space access entry, jump to the interface of the target collaborative space, and locate the interaction window of the first collaborative object.

[0140] In one possible implementation, when the first collaborative object belongs to multiple target collaborative spaces, the space access entrances corresponding to each of the multiple target collaborative spaces are displayed side by side in the access interface, and each space access entrance independently displays the unread message reminder of the first collaborative object in the corresponding target collaborative space; Alternatively, an aggregated space access entry can be displayed in the access interface, showing the total number of unread messages in the multiple target collaboration spaces; in response to triggering the aggregated space access entry, a list of the multiple target collaboration spaces can be displayed for the user to select.

[0141] In one possible implementation, the device further includes: The group display module is used to group and display multiple collaborative objects belonging to the target collaborative space according to a preset classification dimension in the interface of the target collaborative space based on the attribute information associated with the affiliation identifier.

[0142] In one possible implementation, the device further includes: The collaboration joining module is used to display, in the interface of the target collaboration space, collaboration objects that have belonged to the target collaboration space but have not yet been joined by the current account, based on the ownership identifier. In response to the current account's joining operation of the collaboration object that has not yet been joined, the current account is added to the member set of the collaboration object and the current account's session interface in the joined collaboration object is displayed.

[0143] In one possible implementation, the device further includes: The archiving module is used to mark the first collaborative object as archived in the interface of the target collaborative space in response to detecting that the first collaborative object has not generated a new message within a preset time period. The archive release module is used to release the archive state when the first collaborating object generates a new message.

[0144] In one possible implementation, the device further includes: A guidance module is used to respond to receiving an access request to the first collaborative object in the access interface of the first collaborative object, and output a jump prompt message to guide the user to access the first collaborative object through the target collaborative space; wherein the access interface is independent of the interface of the target collaborative space.

[0145] In one possible implementation, the device further includes: The redirection module is used to respond to an access request to the first collaboration object received via an external link, redirect the access request to the interface of the target collaboration space according to the attribution identifier, and locate the interactive window of the first collaboration object in the interface of the target collaboration space.

[0146] In one possible implementation, the device further includes: The attribution removal module is used to, in response to the operation of removing the first collaborative object from the target collaborative space, clear the attribution identifier of the first collaborative object and restore the access entry of the first collaborative object in the access interface.

[0147] In one possible implementation, the device further includes: The identifier display module is used to respond to receiving a search request for the first collaborative object in the search interface and displaying the first collaborative object in the search results, and to display the identifier information of the target collaborative space in the search results according to the attribution identifier.

[0148] like Figure 5 As shown in the figure, this application provides an electronic device, including a processor 111, a communication interface 112, a memory 113, and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114. Memory 113 is used to store computer programs; In one embodiment of this application, when the processor 111 executes a program stored in the memory 113, it implements the cooperative method provided in any of the foregoing method embodiments, including: In response to the operation of adding a first collaboration object to a target collaboration space, an ownership identifier is created for the first collaboration object, the ownership identifier being used to indicate that the first collaboration object belongs to the target collaboration space; Based on the attribution identifier, the access point of the first collaborative object is displayed in the interface of the target collaborative space; Manage the collaborative members of the first collaborative object and the collaborative members of the target collaborative space.

[0149] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the cooperative method provided in any of the foregoing method embodiments.

[0150] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0151] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented using software plus a general-purpose hardware platform, or of course, using hardware. Based on this understanding, the above technical solutions, in essence or the parts that contribute to the related technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0152] It should be understood that the terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “described” as used herein may also include the plural forms. The terms “comprising,” “including,” “containing,” and “having” are inclusive and therefore indicate the presence of the stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not construed as requiring them to be performed in a particular order described or illustrated unless the order of performance is explicitly indicated. It should also be understood that additional or alternative steps may be used.

[0153] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A collaborative method, characterized in that, The method includes: In response to the operation of adding a first collaboration object to a target collaboration space, an ownership identifier is created for the first collaboration object, the ownership identifier being used to indicate that the first collaboration object belongs to the target collaboration space; Based on the affiliation identifier, the access entry of the first collaborative object is displayed in the interface of the target collaborative space, and the collaborative members of the first collaborative object and the collaborative members of the target collaborative space are managed.

2. The method according to claim 1, characterized in that, The method further includes: Based on the attribution identifier, the access entry of the first collaborative object is hidden in the access interface of the first collaborative object; wherein, the access interface of the first collaborative object is independent of the interface of the target collaborative space.

3. The method according to claim 2, characterized in that, The method further includes: In response to the generation of a new message from the first collaborating object, a message notification for the new message is displayed in the interface of the target collaborating space based on the attribution identifier.

4. The method according to claim 2, characterized in that, The method further includes: The access interface of the first collaborative object displays the space access entry corresponding to the target collaborative space; In response to the generation of a new message by the first collaborating object in the target collaboration space, a message notification of the new message is displayed at the space access entry point according to the ownership identifier; In response to triggering the space access entry, the system jumps to the interface of the target collaborative space and locates the interaction window of the first collaborative object.

5. The method according to claim 4, characterized in that, When the first collaborative object belongs to multiple target collaborative spaces, the space access entrances corresponding to each of the multiple target collaborative spaces are displayed side by side in the access interface, and each space access entrance independently displays the unread message reminder of the first collaborative object in the corresponding target collaborative space; Alternatively, an aggregated space access entry can be displayed in the access interface, showing the total number of unread messages in the multiple target collaboration spaces; in response to triggering the aggregated space access entry, a list of the multiple target collaboration spaces can be displayed for the user to select.

6. The method according to claim 1, characterized in that, The method further includes: In the interface of the target collaboration space, multiple collaboration objects belonging to the target collaboration space are grouped and displayed according to preset classification dimensions based on the attribute information associated with the affiliation identifier.

7. The method according to claim 1, characterized in that, The method further includes: In the interface of the target collaboration space, based on the ownership identifier, the collaboration objects that have belonged to the target collaboration space and have not yet been joined by the current account are displayed; In response to the current account's joining operation of the collaboration object that has not yet been joined, the current account is added to the member set of the collaboration object and the current account's session interface in the joined collaboration object is displayed.

8. The method according to claim 1, characterized in that, The method further includes: In response to detecting that the first collaborative object has not generated any new messages within a preset time period, the first collaborative object is marked as archived in the interface of the target collaborative space; If the first collaborating object generates a new message, the archiving state is lifted.

9. The method according to claim 1, characterized in that, The method further includes: In response to receiving an access request to the first collaborative object in the access interface of the first collaborative object, a redirection prompt message is output to guide the user to access the first collaborative object through the target collaborative space; wherein the access interface is independent of the interface of the target collaborative space.

10. The method according to claim 1, characterized in that, The method further includes: In response to receiving an access request to the first collaborative object via an external link, the access request is redirected to the interface of the target collaborative space based on the attribution identifier, and the interactive window of the first collaborative object is located in the interface of the target collaborative space.

11. The method according to claim 2, characterized in that, The method further includes: In response to the operation of removing the first collaborative object from the target collaborative space, the ownership identifier of the first collaborative object is cleared, and the access entry of the first collaborative object in the access interface is restored.

12. The method according to claim 1, characterized in that, The method further includes: In response to receiving a search request for the first collaborative object in the search interface, and displaying the first collaborative object in the search results, the identification information of the target collaborative space is displayed in the search results in association with the attribution identifier.

13. A cooperative device, characterized in that, The device includes: The attribution identifier module is used to create an attribution identifier for the first collaborative object in response to the operation of adding the first collaborative object to the target collaborative space. The attribution identifier is used to indicate that the first collaborative object belongs to the target collaborative space. An entry display module is used to display the access entry of the first collaborative object in the interface of the target collaborative space based on the ownership identifier; The member management module is used to manage the collaborative members of the first collaborative object and the collaborative members of the target collaborative space.

14. A storage medium, characterized in that, The storage medium stores one or more programs, which can be executed by one or more processors to implement the collaborative method according to any one of claims 1-12.

Images