Document management method, system and device

Abstract

The invention relates to a document management method, system and device. The method comprises the steps of obtaining a user identifier of a collaborative user in response to an editing operation of the collaborative user for a target document; in the permission control data corresponding to the target document, determining target permission control data corresponding to the collaborative user according to the user identifier; sending the target authority control data to a first client of the collaborative user; the first client is used for displaying target editing content corresponding to the target authority control data on a client interface of the collaborative user based on the target authority control data. By adopting the method, the security of multi-person editing in the target document can be improved.

Description

Technical Field

[0001] The present application relates to the field of information management technology, and in particular to a document management method, system and device. Background Art

[0002] With the development of text editors, rich text editors are increasingly used on the Web (web pages). A rich text editor is a tool that allows users to edit text in a more intuitive and easier to understand way.

[0003] In traditional technology, the application server implements rich text editor and real-time collaboration functions through the front-end rendering engine, such as JavaScript (a web scripting language). First, the application server determines the user's user role based on the user's selection, and each user role corresponds to different document editing permissions. Then, the front-end rendering engine captures the editing operations performed by users with different user roles and sends each operation to the application server in real time. The application server receives and executes the editing operation, broadcasts the document content modified by the editing operation to all connected users, and completes multi-person document editing.

[0004] However, in current traditional technologies, since the document editing permission corresponds to the entire document, the granularity of the document editing permission is large and the permission control is single, which in turn leads to poor security of document editing collaboration. Summary of the invention

[0005] Based on this, it is necessary to provide a document management method, system, apparatus, computer device, computer-readable storage medium and computer program product to address the above technical issues.

[0006] In a first aspect, the present application provides a document management method, applied to a server, comprising:

[0007] In response to an editing operation of a collaborative user on a target document, obtaining a user identifier of the collaborative user;

[0008] In the authority control data corresponding to the target document, determining the target authority control data corresponding to the collaborative user according to the user identifier;

[0009] The target permission control data is sent to the first client of the collaborative user; the first client is used to display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data.

[0010] In one embodiment, before obtaining the user identification of the collaborative user in response to the editing operation of the collaborative user on the target document, the method further includes:

[0011] Receiving permission configuration parameters set by the primary user for a target document and a document identifier of the target document from a second client of the primary user;

[0012] The authority control data corresponding to the target document is constructed and stored according to the authority control engine, the document identifier and the authority configuration parameters.

[0013] In one embodiment, constructing and storing the permission control data corresponding to the target document according to the permission control engine, the document identifier and the permission configuration parameter includes:

[0014] Matching the target document in existing documents according to the authority control engine and the document identifier to obtain a document matching result;

[0015] If the document matching result is that the target document corresponding to the document identifier exists in the existing document, permission control data corresponding to the target document is constructed and stored based on the permission configuration parameters.

[0016] In one of the embodiments, the target permission configuration parameters include the user identification, function permission configuration and editing scope permission configuration of the collaborative user.

[0017] In one embodiment, the method further comprises:

[0018] Receiving update permission configuration parameters sent by the second client of the primary user;

[0019] Matching the target document in existing documents according to the authority control engine and the document identifier, and determining original authority control data corresponding to the target document based on the matching result;

[0020] The original authority control data is updated based on the update authority configuration parameters to obtain and store update target authority control data;

[0021] If the collaborative user is performing an editing operation on the target document, the update target authority control data is sent to the first client of the collaborative user.

[0022] In one embodiment, if the collaborative user is performing an editing operation on the target document, sending the update target permission control data to the first client of the collaborative user includes:

[0023] If the collaborative user is performing an editing operation on the target document, a permission update instruction carrying the updated target permission control data is sent to the first client of the collaborative user; the permission update instruction is used to instruct the first client to update the target editing content according to the updated target permission control data, and display the updated target editing content on the client interface of the collaborative user.

[0024] In one embodiment, sending the target permission control data to the first client of the collaborative user includes:

[0025] Sending an authorization control instruction carrying the target authorization control data to the first client of the collaborative user; the authorization control instruction is used to instruct the first client to display the target editing content corresponding to the target authorization control data on the client interface of the collaborative user based on the target authorization control data.

[0026] In a second aspect, the present application further provides a document management device, which is applied to a server and includes:

[0027] An acquisition module, configured to acquire a user ID of a collaborative user in response to an editing operation of the collaborative user on a target document;

[0028] A determination module, which determines, in the authority control data corresponding to the target document, target authority control data corresponding to the collaborative user according to the user identifier;

[0029] The first sending module is used to send the target authority control data to the first client of the collaborative user; the first client is used to display the target editing content corresponding to the target authority control data on the client interface of the collaborative user based on the target authority control data.

[0030] In one embodiment, the device further comprises:

[0031] A first receiving module, configured to receive permission configuration parameters set by the primary user for a target document and a document identifier of the target document, which are sent by the second client of the primary user;

[0032] A construction module is used to construct and store the permission control data corresponding to the target document according to the permission control engine, the document identifier and the permission configuration parameters.

[0033] In one of the embodiments, the construction module is specifically used to match the target document in the existing documents according to the authority control engine and the document identifier to obtain a document matching result;

[0034] If the document matching result is that the target document corresponding to the document identifier exists in the existing document, permission control data corresponding to the target document is constructed and stored based on the permission configuration parameters.

[0035] In one of the embodiments, the target permission configuration parameters include the user identification, function permission configuration and editing scope permission configuration of the collaborative user.

[0036] In one embodiment, the device further comprises:

[0037] A second receiving module, used to receive the update permission configuration parameters sent by the second client of the primary user;

[0038] A matching module, used to match the target document in existing documents according to the authority control engine and the document identifier, and determine the original authority control data corresponding to the target document based on the matching result;

[0039] A first updating module, configured to update the original permission control data based on the update permission configuration parameters, and obtain and store update target permission control data;

[0040] The third sending module is used to send the update target authority control data to the first client of the collaborative user if the collaborative user is performing an editing operation on the target document.

[0041] In one of the embodiments, the third sending module is specifically used to send a permission update instruction carrying the updated target permission control data to the first client of the collaborative user if the collaborative user is performing an editing operation on the target document; the permission update instruction is used to instruct the first client to update the target editing content according to the updated target permission control data, and display the updated target editing content on the client interface of the collaborative user.

[0042] In one of the embodiments, the first sending module is specifically used to send a permission control instruction carrying the target permission control data to the first client of the collaborative user; the permission control instruction is used to instruct the first client to display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data.

[0043] In a third aspect, the present application also provides a document management system, including:

[0044] The server is used to obtain the user identification of the collaborative user in response to the editing operation of the collaborative user on the target document; determine the target permission control data corresponding to the collaborative user according to the user identification in the permission control data corresponding to the target document; send the target permission control data to the first client of the collaborative user; the first client is used to display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data;

[0045] The first client is used to send the user identification of the collaborative user to the server in response to the editing operation on the target document; receive the target permission control data corresponding to the collaborative user, and display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data.

[0046] In a fourth aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0047] In response to an editing operation of a collaborative user on a target document, obtaining a user identifier of the collaborative user;

[0048] In the authority control data corresponding to the target document, determining the target authority control data corresponding to the collaborative user according to the user identifier;

[0049] The target permission control data is sent to the first client of the collaborative user; the first client is used to display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data.

[0050] In a fifth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0051] In response to an editing operation of a collaborative user on a target document, obtaining a user identifier of the collaborative user;

[0052] In the authority control data corresponding to the target document, determining the target authority control data corresponding to the collaborative user according to the user identifier;

[0053] The target permission control data is sent to the first client of the collaborative user; the first client is used to display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data.

[0054] In a sixth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0055] In response to an editing operation of a collaborative user on a target document, obtaining a user identifier of the collaborative user;

[0056] In the authority control data corresponding to the target document, determining the target authority control data corresponding to the collaborative user according to the user identifier;

[0057] The target permission control data is sent to the first client of the collaborative user; the first client is used to display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data.

[0058] The above-mentioned document management method, apparatus, computer equipment, computer-readable storage medium and computer program product determine the personalized target permission control data corresponding to the collaborative user according to the user identification of the collaborative user, and the target permission control data represents the editable content of the collaborative user, and then send the target permission control data to the first client of the collaborative user, so that the first client only displays the target editing content corresponding to the target permission control data, which can avoid the erroneous operation of the collaborative user to improve the quality of the final output content, and shield and control the sensitive information in the target document, and control the display object of the sensitive information; if the main user modifies the editing scope permission configuration of the collaborative user when the collaborative user is performing an editing operation on the target document, through the interaction between the permission control engine and the second client of the collaborative user, the original permission control data is updated in real time by using the update permission configuration parameters, and the update and adjustment of the target permission control data is realized, and then the target editing content of the collaborative user is updated in real time, and the function page that allows the collaborative user to allow editing is displayed in real time, so that the collaborative user can adjust the collaboration status in time. In the event of security problems or the need to adjust permissions, the real-time modification can immediately limit or grant access rights to the collaborative user, protect sensitive information from being accessed or modified by unauthorized collaborative users, prevent potential security risks, and improve the security of multi-person editing. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0060] FIG1 is an application environment diagram of a document management method in one embodiment;

[0061] Figure 2 A schematic diagram of a flow chart of a document management method applied to a server in one embodiment;

[0062] Figure 3 A schematic diagram of a process for constructing and storing target permission control data in one embodiment;

[0063] Figure 4 A schematic diagram of a display page for a main user to select a collaborative user in one embodiment;

[0064] Figure 5 A schematic diagram of a display page for a main user to specify a collaborative user in one embodiment;

[0065] Figure 6 A flowchart of specific steps for constructing and storing target permission control data in one embodiment;

[0066] Figure 7 A schematic diagram of a flow chart of the step of updating target authority control data in one embodiment;

[0067] Figure 8 is a schematic diagram of the interaction between a main user, a collaborative user and a server in one embodiment;

[0068] Fig. 9 A schematic diagram of a control toolbar menu in target editing content in one embodiment;

[0069] Fig.10 A schematic diagram of the structure of a document management system in one embodiment;

[0070] Fig.11 is a structural block diagram of a document management device applied to a server in one embodiment;

[0071] Fig.12 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0072] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0073] The document management method provided in the embodiment of the present application can be applied in the application environment shown in FIG. 1. The server 102 communicates with the first client 104 through the network. The data storage system can store the data that the server 102 needs to process. The data storage system can be integrated on the server 102, or it can be placed on the cloud or other network servers. The server 102 obtains the user identification of the collaborative user in response to the editing operation of the collaborative user on the target document; the server 102 determines the target permission control data corresponding to the collaborative user according to the user identification in the permission control data corresponding to the target document; the server 102 sends the target permission control data to the first client 104 of the collaborative user; the first client 104 is used to display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data. The first client 104 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers and portable wearable devices, and the portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The head-mounted device can be a virtual reality (VR) device, an augmented reality (AR) device, smart glasses, etc. The server 102 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud computing services.

[0074] In an exemplary embodiment, Figure 2 As shown, a document management method is provided, which is described by taking the method applied to the server in FIG. 1 as an example, and includes the following steps 202 to 206. Among them:

[0075] Step 202: In response to the editing operation of the collaborative user on the target document, the user identification of the collaborative user is obtained.

[0076] In the embodiment of the present application, the target document may be a document in a rich text editor, wherein the rich text editor is a tool that allows users to edit text in a more intuitive and easier to understand manner, and provides users with a variety of formatting options, such as font, color, size, alignment, list, link, and picture insertion, etc. The embodiment of the present application does not limit the form of the rich text editor. Rich text editors are usually used in websites, blog systems, forums, and other applications to facilitate users to edit articles or information.

[0077] The data storage system of the server includes multiple target documents and permission control data corresponding to each target document. When a collaborative user opens a target document on his first client, the first client sends the user ID of the current collaborative user and an edit request for the target document to the server. In response to the edit request of the collaborative user for the edit operation of the target document, the server receives and obtains the user ID of the collaborative user, wherein the user ID can be the user account, user name or user ID (Identity document, unique identity) corresponding to the user account of the collaborative user.

[0078] Step 204: Determine the target permission control data corresponding to the collaborative user according to the user identifier in the permission control data corresponding to the target document.

[0079] In the embodiment of the present application, in the target documents stored in the data storage system of the server, each target document contains permission control data for different collaborative users, and the permission control data represents the content that each collaborative user is allowed to edit or the functions that he is allowed to use in the target document.

[0080] After the server receives the editing request of the collaborative user and obtains the user ID of the collaborative user, the server matches the multiple permission control data corresponding to the target document according to the user ID to obtain the target permission control data corresponding to the collaborative user. Specifically, the server includes a permission control engine for controlling the editing permissions of the collaborative user. After receiving the user ID, the server transmits the user ID to the permission control engine. The permission control engine retrieves all the permission control data corresponding to the target document in the database, determines the target permission control data that matches the user ID in the permission control data, and then converts the target permission control data into an adaptive transmission format to prepare for the subsequent transmission steps.

[0081] Step 206: Send the target authority control data to the first client of the collaborative user.

[0082] The first client is used to display the target editing content corresponding to the target authority control data on the client interface of the collaborative user based on the target authority control data.

[0083] In an embodiment of the present application, the server can send the target permission control data corresponding to the current collaborative user to the first client of the collaborative user through the permission control engine. The first client can determine the target editing content corresponding to the collaborative user through the target permission control data, including the visible document content, available functions and editable content of the current collaborative user.

[0084] In an exemplary embodiment, during the process of editing the target document by the collaborative user, the first client can send the edited and modified content to the server in real time to perform persistent processing on the document content of the target document. The server receives the edited and modified content by the collaborative user through the permission control engine, and matches the modified content with the target permission control data according to the permission control engine. If the target edited content corresponding to the target permission control data does not match the modified content, the server blocks the illegal content through the permission control engine and sends a warning message to the first client of the collaborative user; if the modified content matches the target edited content, the modified content is updated to the target document through the permission control engine, and the collaborative user completes the editing of the target document.

[0085] In the above-mentioned document management method, the personalized target permission control data corresponding to the collaborative user is determined based on the user identifier of the collaborative user, and the target permission control data represents the editable content of the collaborative user. The target permission control data is then sent to the first client of the collaborative user, so that the first client only displays the target editing content corresponding to the target permission control data. This can avoid the collaborative user's erroneous operation to improve the quality of the final output content, and shield and control sensitive information in the target document, control the display object of sensitive information, and improve the security of multiple people editing in the target document.

[0086] In an exemplary embodiment, before the collaborative users participate in the editing operation of the target document, the main user needs to select the collaborative users of the target document and set the scope of the editing authority of each collaborative user, so that the server pre-stores the authority control data corresponding to the target document, such as Figure 3 As shown, step 202 includes steps 302 to 304. Among them:

[0087] Step 302: receiving the permission configuration parameters set by the primary user for the target document and the document identifier of the target document sent by the second client of the primary user.

[0088] In the embodiment of the present application, after the primary user of the target document (the owner of the target document) completes the creation of the target document on the second client, the primary user can first construct the content framework of the target document and edit and set permissions for some of the content, for example, Figure 5 As shown, the main user specifies the collaborative users of the target document according to the content and function according to specific needs, such as Figure 4 As shown, Figure 4 The main user selects the collaborative user display page. After completing the selection of collaborative users for the target document, the main user can also set more specific editing content for the selected collaborative users. The main user can select a collaborative user or a collaborative user group (such as Figure 5The collaborative user shown in the figure selects operable permissions and functions, constitutes the permission configuration parameters corresponding to the collaborative user in the target document and stores them in the local cache, wherein the permission configuration parameters include the editing content permissions and functional permissions corresponding to the collaborative user, which respectively correspond to the functional permission configuration and editing scope permission configuration included in the subsequent permission configuration parameters of the collaborative user under the target document.

[0089] After the main user completes the editing permissions for the collaborative users and the corresponding collaborative users for the target document, the second client sends the permission configuration parameters in the local cache and the document identifier of the target document to the server through the front-end rendering engine. In turn, the server receives the permission configuration parameters and the document identifier of the target document sent by the second client through the permission control engine as a storage basis.

[0090] Step 304: construct and store target permission control data corresponding to the target document according to the permission control engine, the document identifier and the permission configuration parameters.

[0091] In an embodiment of the present application, first, the server parses the permission settings contained in the permission configuration parameters through the permission control engine, and determines the target document from the documents stored on the server through the permission control engine and the document identifier, and then constructs the permission control data of the target document according to the permission configuration parameters. The permission control data includes the target permission control data corresponding to each collaborative user of the target document, as a target data structure stored in the database. Finally, the server stores the constructed target data structure of the permission control data in a database or other persistent storage medium.

[0092] In this embodiment, by constructing and storing the permission control data of the target document based on the permission configuration parameters set by the main user and the document identifier, the server can accurately apply and maintain the permission control settings of the target document. When the collaborative user edits the target document, the target permission control data corresponding to each collaborative user can be accurately determined, the editing permissions of the collaborative users can be strictly controlled, and the security of the target document in a multi-person collaborative environment can be ensured.

[0093] In an exemplary embodiment, Figure 6 As shown, step 304 includes steps 602 to 604. Among them:

[0094] Step 602: Match the target document in the existing documents according to the authority control engine and the document identifier to obtain a document matching result.

[0095] In an embodiment of the present application, each existing document in the server has its corresponding document identifier. The server searches for a document identifier corresponding to the document identifier of the target document in the existing documents through the permission control engine. If the document identifier of the target document exists in the existing document, the document matching result is determined as a successful match, that is, the target document corresponding to the document identifier exists in the existing document; if the document identifier of the target document does not exist in the existing document, the document matching result is determined as a failed match, that is, the target document corresponding to the document identifier does not exist in the existing document.

[0096] Step 604: If the document matching result is that the target document corresponding to the document identifier exists in the existing document, permission control data corresponding to the target document is constructed and stored based on the permission configuration parameters.

[0097] In an embodiment of the present application, if the document matching result is that a target document corresponding to the document identifier exists in an existing document, that is, the matching result is a successful match, the server constructs the permission control data according to the same principle as step 304, and the permission control engine uses the constructed permission control parameters to update the existing original permission control data.

[0098] If the document matching result is that the target document corresponding to the document identifier does not exist in the existing document, that is, the matching result is a matching failure, it means that the current target document is the first time to build the target permission control data. The server first saves the target document and persistently stores the document content of the target document, and then stores the permission control data of the target document according to the same principle as step 304.

[0099] In this embodiment, confirming the existence of the target document in the server through document identification helps to improve the operating efficiency of the server. Storing the permission control data in the database can maintain the consistency of the permission settings of the target document, ensure the long-term effectiveness of the permission settings of the target document in the server, and improve the stability of document management.

[0100] In an exemplary embodiment, the target permission configuration parameters include a user ID of a collaborative user, a function permission configuration, and an edit scope permission configuration.

[0101] The editing scope permission configuration also includes permission configuration for controlling the content visible to collaborative users.

[0102] In this embodiment, by specifying the user ID of the collaborative user, the server can accurately identify and locate each collaborative user, and then, the permission setting can be performed for a specific user, thereby realizing personalized document permission management. By setting different functional permission configurations and editing scope permission configurations for each collaborative user, the permissions, visible content, and editing content of each collaborative user for specific functional operations of the target document can be controlled, and more fine-grained permission settings can be used to ensure that different collaborative users can only perform authorized operations, reducing the risk of unnecessary interference with the document or misoperation. Furthermore, by configuring the editing scope permission, it is clear that the collaborative user can edit specific parts of the document (such as specific chapters or paragraphs), which helps to avoid editing conflicts and inconsistencies of the same document by different collaborative users, and can ensure that each collaborative user can collaborate effectively within the scope of his or her authority without affecting the work area of ​​other collaborative users. In addition, function permission configuration and editing scope configuration can protect sensitive information in the target document. For example, some parts of the target document may contain sensitive data. By setting different function permission configurations and editing scope permission configurations for different collaborative users, only certain specific collaborative users are allowed to access or edit, and sensitive information parts are only visible to some collaborative users, thereby reducing the risk of data leakage, ensuring the content classification and confidentiality of the target document in collaborative editing, and improving the security of multiple people editing the target document.

[0103] In an exemplary embodiment, when the primary user updates the permission control data of the target document, the server needs to update the stored original permission control data in real time and update the target editing content in the client interface of the collaborative user in real time, such as Figure 7 As shown, the method further includes steps 702 to 708. Among them:

[0104] Step 702: receiving the update authority configuration parameters sent by the second client of the primary user.

[0105] In the embodiment of the present application, the main user can modify and adjust the editing permissions or visible content of the collaborative user in real time. After the front-end rendering engine of the second client determines that the main user has updated the permission configuration parameters of the collaborative user, such as Figure 8 As shown, the second client sends the update authority configuration parameters in the cache to the server, and then the server receives the update authority configuration parameters sent by the second client of the primary user.

[0106] Step 704: Match the target document in the existing documents according to the authority control engine and the document identifier, and determine the original authority control data corresponding to the target document based on the matching result.

[0107] In an embodiment of the present application, the server retrieves the document identifier of the target document in the existing documents according to the permission control engine, takes the existing document corresponding to the document identifier of the target document as the matching result, and obtains the original permission control data corresponding to the existing target document according to the matching result. The original permission control data represents the original editing permission of the collaborative user whose current editing permission has been modified for the target document, and serves as the basis for updating the permission configuration parameters.

[0108] Step 706: Update the original permission control data based on the updated permission configuration parameters, and obtain and store updated target permission control data.

[0109] In the embodiment of the present application, the server can directly overwrite the original permission control data with the updated permission configuration parameters to obtain the updated target permission control data, and store the updated target permission control data as the new target permission control data corresponding to the target document. Alternatively, the server can first determine the modification content of the updated permission configuration parameters relative to the original permission control data, and update the original permission control data according to the modified content to obtain the updated target permission control data, and store the updated target permission control data as the new target permission control data corresponding to the target document.

[0110] Step 708: If the collaborative user is performing an editing operation on the target document, the updated target permission control data is sent to the first client of the collaborative user.

[0111] In the embodiment of the present application, the edits of the target document by the collaborative user and the main user can be saved to the server in real time. Therefore, the server can determine the status of the collaborative user in real time according to the communication status between the collaborative user and the server, so as to determine whether the collaborative user is offline or performing an edit operation on the target document according to the status of the collaborative user. Figure 8 As shown, the server sends the update target permission control data to the first client of the collaborative user in real time, instructing the first client to instantly update the target editing content of the collaborative user.

[0112] In this embodiment, through the interaction between the permission control engine and the second client, the original permission control data is updated in real time by updating the permission configuration parameters, so that the target permission control data can be updated and adjusted, and then the target editing content of the collaborative user is updated in real time when the collaborative user is performing an editing operation on the target document. The real-time modification allows all collaborative users to immediately see the results of the permission update, so that the collaborative users can make timely adjustments, avoiding delays in collaboration caused by permission issues. In the event of security issues or the need to adjust permissions, real-time modifications can immediately limit or grant access rights, protect sensitive information from being accessed or modified by unauthorized collaborative users, prevent potential security risks, and improve the security of multi-person editing.

[0113] In an exemplary embodiment, after the main user updates the target permission control data of the collaborative user in real time, the first client also needs to update the target editing content of the client page of the collaborative user, and step 708 includes step 7081. Among them:

[0114] Step 7081: If the collaborative user is performing an editing operation on the target document, a permission update instruction carrying updated target permission control data is sent to the first client of the collaborative user.

[0115] The permission update instruction is used to instruct the first client to update the target editing content according to the update target permission control data, and display the updated target editing content on the client interface of the collaborative user.

[0116] In an embodiment of the present application, if a collaborative user is performing an editing operation on a target document, in order to adjust the editing permissions of the display page of the collaborative user's first client in real time, the server will send a permission update instruction carrying updated target permission control data to the collaborative user's first client.

[0117] The first client receives the permission update instruction sent by the server in real time, and after the first client receives the updated target permission control data in the permission update instruction, the first client can clearly see that the current collaborative user's editing permissions for the target document have changed. For example, the main user may have opened up more functional permissions or visible content to the current collaborative user, or the main user may have limited the current collaborative user's more functional permissions or visible content. At this time, the first client needs to respond to the main user's permission update behavior, that is, update and adjust the target permission configuration parameters according to the updated permission configuration parameters.

[0118] After the front-end rendering engine of the first client detects that the target permission control data of the target document is updated, the first client first saves the functional permission configuration in the updated target permission control data and the editing range permission configuration corresponding to the visible content to the local cache through the front-end rendering engine, and then updates the target editing content in real time according to the functional permission configuration and the editing range permission configuration, and displays the updated target editing content on the client display page of the collaborative user, thereby completing the real-time adjustment of the target editing content of the collaborative user.

[0119] In this embodiment, by sending a permission update instruction to the first client to update and adjust the target permission control data of the collaborative user, the target editing content of the collaborative user is updated in real time while the collaborative user is performing an editing operation on the target document. The real-time modification allows all collaborative users to immediately see the result of the permission update, so that the collaborative users can make timely adjustments and avoid delays caused by permission issues. In the event of security issues or the need to adjust permissions, real-time modifications can immediately restrict or grant access rights, protect sensitive information from being accessed or modified by unauthorized collaborative users, prevent potential security risks, and improve the security of multi-person editing.

[0120] In an exemplary embodiment, step 206 includes step 2061. In which:

[0121] Step 2061: Send the permission control instruction carrying the target permission control data to the first client of the collaborative user.

[0122] The permission control instruction is used to instruct the first client to display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data.

[0123] In the embodiment of the present application, in response to the editing operation on the target document, the first client sends the user ID of the collaborative user and the editing request of the collaborative user for the editing operation on the target document to the server, notifying the server to respond to the editing request, and then the server sends the permission control instruction carrying the target permission control data to the first client of the collaborative user, and instructs the first client to display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data through the permission control instruction. Optionally, the second client can also send the document ID of the target document to the server together with the user ID.

[0124] After the first client receives the permission control instruction, it parses the permission control instruction to obtain the target permission control data corresponding to the collaborative user, and based on the target permission control data, displays the target editing content corresponding to the target permission control data on the client interface of the collaborative user. Specifically, after the first client of the collaborative user receives the permission control instruction through the front-end rendering engine and completes the parsing, it obtains the target permission control data corresponding to the collaborative user, and then matches the properties of the target document content and the control toolbar menu according to the target permission control data pre-set by the main user, and then displays the target document content to the client interface of the collaborative user based on the matching result, so that the collaborative user can only edit the target editing content for which he has permission to operate. Among them, the control toolbar menu in the target editing content is as follows: Fig. 9 As shown, the properties of the target document that the collaborative users edit or the available status of each tool in the control toolbar are displayed.

[0125] In this embodiment, the server sends the permission control instruction to the first client of the collaborative user, so that the first client only displays the target editing content corresponding to the target permission control data through the target permission control data, thereby avoiding erroneous operations of the collaborative user to improve the quality of the final output content, and shielding and controlling sensitive information in the target document, controlling the display object of sensitive information, and improving the security of multiple people editing in the target document.

[0126] In an exemplary embodiment, Fig.10 As shown, a document management system 1000 is provided, including a server 1001 and a first client 1002, wherein:

[0127] Server 1001 is used to obtain the user ID of the collaborative user in response to the editing operation of the collaborative user on the target document; determine the target permission control data corresponding to the collaborative user according to the user ID in the permission control data corresponding to the target document; send the target permission control data to the first client of the collaborative user; the first client is used to display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data;

[0128] The first client 1002 is used to send the user identification of the collaborative user to the server in response to the editing operation on the target document; receive the target permission control data corresponding to the collaborative user, and display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data.

[0129] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0130] Based on the same inventive concept, the embodiment of the present application also provides a document management device for implementing the document management method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in one or more document management device embodiments provided below can refer to the limitations on the document management method above, and will not be repeated here.

[0131] In an exemplary embodiment, Fig.11 As shown, a document management device 1100 is provided, which is applied to a server and includes: an acquisition module 1101, a determination module 1102 and a first sending module 1103, wherein:

[0132] An acquisition module 1101 is used to acquire a user ID of a collaborative user in response to an editing operation of the collaborative user on a target document;

[0133] A determination module 1102 determines, in the authority control data corresponding to the target document, target authority control data corresponding to the collaborative user according to the user identifier;

[0134] The first sending module 1103 is used to send the target authority control data to the first client of the collaborative user; the first client is used to display the target editing content corresponding to the target authority control data on the client interface of the collaborative user based on the target authority control data.

[0135] In one embodiment, the apparatus 1100 further includes:

[0136] A first receiving module is used to receive the permission configuration parameters set by the primary user for the target document and the document identifier of the target document sent by the second client of the primary user;

[0137] The construction module is used to construct and store the permission control data corresponding to the target document according to the permission control engine, document identification and permission configuration parameters.

[0138] In one embodiment, the construction module is specifically used to match the target document in the existing documents according to the authority control engine and the document identifier to obtain a document matching result;

[0139] If the document matching result is that a target document corresponding to the document identifier exists in an existing document, permission control data corresponding to the target document is constructed and stored based on the permission configuration parameters.

[0140] In one of the embodiments, the target permission configuration parameters include a user ID of the collaborative user, a function permission configuration, and an edit scope permission configuration.

[0141] In one embodiment, the apparatus 1100 further includes:

[0142] A second receiving module, used to receive the update permission configuration parameters sent by the second client of the primary user;

[0143] A matching module, used to match the target document in the existing documents according to the permission control engine and the document identifier, and determine the original permission control data corresponding to the target document based on the matching result;

[0144] A first updating module, used to update the original permission control data based on the update permission configuration parameters, and obtain and store the update target permission control data;

[0145] The third sending module is used to send the updated target permission control data to the first client of the collaborative user if the collaborative user is performing an editing operation on the target document.

[0146] In one of the embodiments, the third sending module is specifically used to send a permission update instruction carrying updated target permission control data to the first client of the collaborative user if the collaborative user is performing an editing operation on the target document; the permission update instruction is used to instruct the first client to update the target editing content according to the updated target permission control data, and display the updated target editing content on the client interface of the collaborative user.

[0147] In one of the embodiments, the first sending module 1103 is specifically used to send a permission control instruction carrying target permission control data to a first client of a collaborative user; the permission control instruction is used to instruct the first client to display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data.

[0148] Each module in the above document management device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module.

[0149] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Fig.12 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store target authority control data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a document management method is implemented.

[0150] Those skilled in the art will understand that Fig.12 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0151] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0152] In response to an editing operation of a collaborative user on a target document, obtaining a user identifier of the collaborative user;

[0153] In the authority control data corresponding to the target document, determine the target authority control data corresponding to the collaborative user according to the user identifier;

[0154] The target authority control data is sent to the first client of the collaborative user; the first client is used to display the target editing content corresponding to the target authority control data on the client interface of the collaborative user based on the target authority control data.

[0155] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0156] Receive the permission configuration parameters set by the primary user for the target document and the document identifier of the target document sent by the second client of the primary user;

[0157] The permission control data corresponding to the target document is constructed and stored according to the permission control engine, document identification and permission configuration parameters.

[0158] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0159] Match the target document in the existing documents according to the permission control engine and the document identifier to obtain a document matching result;

[0160] If the document matching result is that a target document corresponding to the document identifier exists in an existing document, permission control data corresponding to the target document is constructed and stored based on the permission configuration parameters.

[0161] In one embodiment, the target permission configuration parameters include the user identification of the collaborative user, the function permission configuration, and the editing scope permission configuration.

[0162] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0163] Receiving update permission configuration parameters sent by the second client of the primary user;

[0164] Matching the target document in the existing documents according to the permission control engine and the document identifier, and determining the original permission control data corresponding to the target document based on the matching result;

[0165] The original permission control data is updated based on the updated permission configuration parameters, and the updated target permission control data is obtained and stored;

[0166] If the collaborative user is performing an editing operation on the target document, the updated target permission control data is sent to the first client of the collaborative user.

[0167] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0168] If the collaborative user is performing an editing operation on the target document, a permission update instruction carrying the updated target permission control data is sent to the collaborative user's first client; the permission update instruction is used to instruct the first client to update the target editing content according to the updated target permission control data, and display the updated target editing content on the collaborative user's client interface.

[0169] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0170] The permission control instruction carrying the target permission control data is sent to the first client of the collaborative user; the permission control instruction is used to instruct the first client to display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data.

[0171] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0172] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0173] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0174] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0175] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0176] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A document management method, characterized in that: The method is applied to a server, and the method comprises: In response to an editing operation of a collaborative user on a target document, obtaining a user identifier of the collaborative user; In the authority control data corresponding to the target document, determining the target authority control data corresponding to the collaborative user according to the user identifier; The target permission control data is sent to the first client of the collaborative user; the first client is used to display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data.

2. The method according to claim 1, characterized in that Before obtaining the user identification of the collaborative user in response to the editing operation of the collaborative user on the target document, the method further includes: Receiving permission configuration parameters set by the primary user for a target document and a document identifier of the target document from a second client of the primary user; The authority control data corresponding to the target document is constructed and stored according to the authority control engine, the document identifier and the authority configuration parameters.

3. The method according to claim 2, characterized in that The step of constructing and storing the permission control data corresponding to the target document according to the permission control engine, the document identifier and the permission configuration parameter includes: Matching the target document in existing documents according to the authority control engine and the document identifier to obtain a document matching result; If the document matching result is that the target document corresponding to the document identifier exists in the existing document, permission control data corresponding to the target document is constructed and stored based on the permission configuration parameters.

4. The method according to claim 1, characterized in that: The target permission configuration parameters include the user identification of the collaborative user, the function permission configuration and the editing range permission configuration.

5. The method according to claim 1, characterized in that The method further comprises: Receiving update permission configuration parameters sent by the second client of the primary user; Matching the target document in existing documents according to the authority control engine and the document identifier, and determining original authority control data corresponding to the target document based on the matching result; The original authority control data is updated based on the update authority configuration parameters to obtain and store update target authority control data; If the collaborative user is performing an editing operation on the target document, the update target authority control data is sent to the first client of the collaborative user.

6. The method according to claim 5, characterized in that If the collaborative user is performing an editing operation on the target document, sending the update target permission control data to the first client of the collaborative user includes: If the collaborative user is performing an editing operation on the target document, a permission update instruction carrying the updated target permission control data is sent to the first client of the collaborative user; the permission update instruction is used to instruct the first client to update the target editing content according to the updated target permission control data, and display the updated target editing content on the client interface of the collaborative user.

7. The method according to claim 1, characterized in that The sending the target authority control data to the first client of the collaborative user includes: Sending an authorization control instruction carrying the target authorization control data to the first client of the collaborative user; the authorization control instruction is used to instruct the first client to display the target editing content corresponding to the target authorization control data on the client interface of the collaborative user based on the target authorization control data.

8. A document management system, characterized in that: The system comprises: The server is used to obtain the user identification of the collaborative user in response to the editing operation of the collaborative user on the target document; determine the target permission control data corresponding to the collaborative user according to the user identification in the permission control data corresponding to the target document; send the target permission control data to the first client of the collaborative user; the first client is used to display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data; The first client is used to send the user identification of the collaborative user to the server in response to the editing operation on the target document; receive the target permission control data corresponding to the collaborative user, and display the target editing content corresponding to the target permission control data on the client interface of the collaborative user based on the target permission control data.

9. A document management device, characterized in that: The device is applied to a server, and comprises: An acquisition module, configured to acquire a user ID of a collaborative user in response to an editing operation of the collaborative user on a target document; A determination module, which determines, in the authority control data corresponding to the target document, target authority control data corresponding to the collaborative user according to the user identifier; The first sending module is used to send the target authority control data to the first client of the collaborative user; the first client is used to display the target editing content corresponding to the target authority control data on the client interface of the collaborative user based on the target authority control data.

10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

Images