Document permission processing method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention relates to a document permission processing method and device, electronic equipment and a storage medium, and the method comprises the steps: responding to a performance triggering operation executed for a document, and determining a first object indicated by the performance triggering operation, the operation triggering operation is used for at least one second device to cooperatively process the document in the process of synchronously operating the document with the first device; and determining the operation permission of the first object for the document, so that the first object operates the document under the operation permission. Therefore, in the process that at least one second device and the first device perform synchronous operation and collaboratively process the document, it can be ensured that the first object performs the document under the operation permission, and therefore it can be ensured that document operation and collaboration are performed under the corresponding operation permission by controlling the operation permission of the first object; therefore, the efficiency of document playing and collaboration is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular, to a method, apparatus, electronic device, and storage medium for processing document permissions. Background Art

[0002] In the related art, there are many inconveniences in reporting, discussing, and communicating among multiple people. For example, in the scenario where multiple people look at the same computer, although the communication efficiency is high, it is not very convenient when there are many people or the distance is too close. For another example, in the screen projection scenario, although the presentation document can be followed to maintain a communication environment, a specific large screen environment is required and it is inconvenient to take turns presenting the document. For another example, in the online method, although multiple people can be supported to present the document, there is a sense of distance among people, and one or more corresponding software are required, or multiple devices need to be used. For the multiple software and multiple devices involved, the document is transferred and presented, resulting in low efficiency of document operation and collaboration.

[0003] It can be seen that how to improve the efficiency of document operation and collaboration is a technical problem worthy of attention. Summary of the Invention

[0004] In view of this, to solve the above-mentioned partial or all technical problems, embodiments of this application provide a method, apparatus, electronic device, and storage medium for processing document permissions.

[0005] In a first aspect, embodiments of this application provide a method for processing document permissions, and the method includes:

[0006] In response to an operation trigger operation performed on a document, determine a first object indicated by the operation trigger operation, where the operation trigger operation is used for at least one second device to collaborate in processing the document during the process of synchronously operating the document with a first device;

[0007] Determine the operation permission of the first object for the document, so that the first object operates the document under the operation permission.

[0008] In a possible implementation manner, determining the operation permission of the first object for the document includes:

[0009] In the case where the first object is not the target object of the document, generate a prompt message, where the prompt message is used to prompt the first object to apply for permission for the document to obtain permission;

[0010] Determine the permission obtained by the first object's application as the operation permission of the first object for the document.

[0011] In a possible implementation manner, determining the operation permission of the first object for the document includes:

[0012] Determine whether the first object has the operation permission for the above-mentioned document during the target period to obtain the first discrimination information, where the target period is before the operation trigger operation is detected;

[0013] Based on the above first discrimination information, determine the operation permission of the first object for the above-mentioned document.

[0014] In a possible implementation manner, the above determining the operation permission of the first object for the above-mentioned document based on the above first discrimination information includes:

[0015] When the first discrimination information indicates that the first object has the operation permission for the above-mentioned document during the target period, determine the operation permission that the first object has during the target period as the operation permission of the first object for the above-mentioned document during the operation period;

[0016] When the first discrimination information indicates that the first object does not have the operation permission for the above-mentioned document during the target period, determine the preset permission as the operation permission of the first object for the above-mentioned document during the operation period.

[0017] In a possible implementation manner, the above determining the operation permission of the first object for the above-mentioned document includes:

[0018] In response to the permission assignment operation for the first object, determine the operation permission of the first object as the operation permission after the permission assignment operation, where the permission assignment operation includes at least one of the following: permission assignment for the same above-mentioned document, permission assignment for different above-mentioned documents, permission assignment for the document content of the above-mentioned document, and permission assignment for different objects.

[0019] In a possible implementation manner, the above permission assignment operation is executed during the operation process of the above-mentioned document, and the permission assignment operation belongs to the first type and / or the second type. The first type indicates that the permission assignment operation is used to determine the number of times of permission use, and the second type indicates that the permission assignment operation is used to determine the time period of permission use.

[0020] In a possible implementation manner, the above determining the operation permission of the first object for the above-mentioned document includes:

[0021] In response to the operation trigger operation executed on the document, determine whether the above-mentioned document is a collaborative document to obtain the third discrimination information;

[0022] Based on the above third discrimination information, determine the operation permission of the first object for the above-mentioned document.

[0023] In a possible implementation manner, determining the operation permission of the first object for the document includes:

[0024] Determining whether the first object is the initiator of the operation trigger operation;

[0025] When the first object is the initiator and the first object allocates permissions to non-initiators, in response to a close operation of the operation indicated by the operation trigger operation, determining whether to retain the operation permission of the non-initiator for the document, where the non-initiator is the first object other than the initiator among the first objects.

[0026] In a possible implementation manner, determining the operation permission of the first object for the document includes:

[0027] Determining whether the first object is the role of the operation demonstration indicated by the operation trigger operation, to obtain fourth discrimination information;

[0028] Based on the fourth discrimination information, determining the operation permission of the first object for the document.

[0029] In a possible implementation manner, after determining the first object of the operation indicated by the operation trigger operation, the method further includes:

[0030] In response to a removal operation on the first object, determining whether the first object is the initiator of the operation trigger operation, to obtain second discrimination information; based on the second discrimination information, determining whether the operation indicated by the operation trigger operation ends; and / or

[0031] In response to a removal operation on the first object, determining the document permission of the document; based on the document permission, determining the operation permission of the first object for the document.

[0032] In a second aspect, an embodiment of the present application provides a device for processing document permissions, where the device includes:

[0033] A first determination unit, configured to determine the first object indicated by the operation trigger operation in response to an operation trigger operation performed on a document, where the operation trigger operation is used for at least one second device to cooperate in processing the document during the synchronous operation of the document with a first device;

[0034] A second determination unit, configured to determine the operation permission of the first object for the document, so that the first object operates the document under the operation permission.

[0035] In a possible implementation, determining the operation permission of the first object for the document includes:

[0036] When the first object is not the target object of the document, generate a prompt message, where the prompt message is used to prompt the first object to apply for permission for the document to obtain the permission;

[0037] Determine the permission obtained by the first object's application as the operation permission of the first object for the document.

[0038] In a possible implementation, determining the operation permission of the first object for the document includes:

[0039] Determine whether the first object has the operation permission for the document during the target period to obtain the first discrimination information, where the target period is before the operation trigger operation is detected;

[0040] Based on the first discrimination information, determine the operation permission of the first object for the document.

[0041] In a possible implementation, based on the first discrimination information, determining the operation permission of the first object for the document includes:

[0042] When the first discrimination information indicates that the first object has the operation permission for the document during the target period, determine the operation permission that the first object has during the target period as the operation permission of the first object for the document during the operation period;

[0043] When the first discrimination information indicates that the first object does not have the operation permission for the document during the target period, determine the preset permission as the operation permission of the first object for the document during the operation period.

[0044] In a possible implementation, determining the operation permission of the first object for the document includes:

[0045] In response to the permission allocation operation for the first object, determine the operation permission of the first object as the operation permission after the permission allocation operation, where the permission allocation operation includes at least one of the following: permission allocation for the same document, permission allocation for different documents, permission allocation for the document content of the document, and permission allocation for different objects.

[0046] In a possible implementation, the above permission allocation operation is performed during the operation process of the above document. The above permission allocation operation belongs to the first type and / or the second type. The first type indicates that the above permission allocation operation is used to determine the number of times of permission usage, and the second type indicates that the above permission allocation operation is used to determine the usage period of permission.

[0047] In a possible implementation, determining the operation permission of the first object for the above document includes:

[0048] In response to an operation trigger operation performed on the document, determining whether the above document is a collaborative document to obtain third discrimination information;

[0049] Based on the above third discrimination information, determining the operation permission of the first object for the above document.

[0050] In a possible implementation, determining the operation permission of the first object for the above document includes:

[0051] Determining whether the first object is the initiator of the above operation trigger operation;

[0052] When the first object is the initiator and the first object allocates permissions to non-initiators, in response to a close operation of the operation indicated by the above operation trigger operation, determining whether to retain the operation permission of the non-initiator for the above document, where the non-initiator is the first object other than the initiator among the first objects.

[0053] In a possible implementation, determining the operation permission of the first object for the above document includes:

[0054] Determining whether the first object is the role of the operation demonstration indicated by the above operation trigger operation to obtain fourth discrimination information;

[0055] Based on the above fourth discrimination information, determining the operation permission of the first object for the above document.

[0056] In a possible implementation, after determining the first object of the operation indicated by the above operation trigger operation, the device further includes:

[0057] A third determination unit, configured to, in response to a removal operation on the first object, determine whether the first object is the initiator of the above operation trigger operation to obtain second discrimination information; based on the second discrimination information, determine whether the operation indicated by the above operation trigger operation ends; and / or

[0058] A fourth determination unit, configured to determine the document permission of the above-mentioned document in response to a removal operation on the above-mentioned first object; and determine the operation permission of the above-mentioned first object for the above-mentioned document based on the above-mentioned document permission.

[0059] In a third aspect, an embodiment of the present application provides an electronic device, including:

[0060] A memory, configured to store a computer program;

[0061] A processor, configured to execute the computer program stored in the memory, and when the computer program is executed, implement the method of any one of the embodiments of the document permission processing method in the first aspect of the present application.

[0062] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, implement the method of any one of the embodiments of the document permission processing method in the first aspect as described above.

[0063] In a fifth aspect, an embodiment of the present application provides a computer program, the computer program includes computer-readable code, and when the computer-readable code runs on a device, the processor in the device is caused to implement the method of any one of the embodiments of the document permission processing method in the first aspect as described above.

[0064] The document permission processing method provided by the embodiments of the present application can determine a first object indicated by the operation trigger operation in response to an operation trigger operation performed on a document, where the operation trigger operation is used for at least one second device to cooperate in processing the document during the process of synchronously operating the document with a first device. After that, determine the operation permission of the first object for the document, so that the first object operates the document under the operation permission. Thus, during the process of at least one second device synchronously operating and cooperating with the first device to process the document, it can be ensured that the first object operates the document under the operation permission, so that the operation and cooperation of the document can be controlled by controlling the operation permission of the first object, thereby improving the efficiency of document operation and cooperation. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] The accompanying drawings here are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present invention and used together with the specification to explain the principles of the present invention.

[0066] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the accompanying drawings required for the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0067] One or more embodiments are exemplarily illustrated by the pictures in the corresponding accompanying drawings. These exemplary illustrations do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings are represented as similar elements, unless otherwise stated, and the drawings in the accompanying drawings do not constitute a scale limitation.

[0068] Figure 1A It is a schematic flowchart of a method for processing document permissions provided by an embodiment of the present application;

[0069] Figure 1B and 1C It is a schematic diagram of an application scenario of a method for processing document permissions provided by an embodiment of the present application;

[0070] Figure 1D It is a schematic diagram of an application scenario of another method for processing document permissions provided by an embodiment of the present application;

[0071] Figure 2 It is a schematic flowchart of another method for processing document permissions provided by an embodiment of the present application;

[0072] Figure 3A It is a schematic flowchart of yet another method for processing document permissions provided by an embodiment of the present application;

[0073] Figures 3B - 3C For Figure 3A the application scenario diagram;

[0074] Figure 4 It is a schematic structural diagram of a device for processing document permissions provided by an embodiment of the present application;

[0075] Figure 5 It is a schematic structural diagram of a device for processing document permissions provided by an embodiment of the present application;

[0076] Figure 6 It is a schematic structural diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0077] Now, various exemplary embodiments of the present application will be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. It should be noted that: unless otherwise specifically stated, the relative arrangements of components and steps, numerical expressions, and numerical values described in these embodiments do not limit the scope of the present application.

[0078] Those skilled in the art can understand that terms such as "first" and "second" in the embodiments of the present application are only used to distinguish different steps, devices, or modules, etc., without representing any specific technical meaning and without indicating the logical order between them.

[0079] It should also be understood that in this embodiment, "a plurality of" may refer to two or more, and "at least one" may refer to one, two or more.

[0080] It should also be understood that for any component, data or structure mentioned in the embodiments of the present application, without clear limitation or contrary indication in the context, it can generally be understood as one or more.

[0081] In addition, the term "and / or" in the present application is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in the present application generally indicates that the associated objects before and after are in an "or" relationship.

[0082] It should also be understood that the description of each embodiment of the present application emphasizes the differences between the embodiments, and their similarities or similarities can be referred to each other. For the sake of brevity, they will not be elaborated one by one.

[0083] The following description of at least one exemplary embodiment is actually merely illustrative and in no way constitutes a limitation on the present application or its application or use.

[0084] Techniques, methods and devices known to those of ordinary skill in the relevant art may not be discussed in detail, but where appropriate, the above techniques, methods and devices should be regarded as part of the specification.

[0085] It should be noted that like reference numerals and letters in the following figures represent similar items, so once an item is defined in one figure, it does not need to be further discussed in subsequent figures.

[0086] It should be noted that, without conflict, the embodiments in the present application and the features in the embodiments can be combined with each other. For the convenience of understanding the embodiments of the present application, the present application will be described in detail below with reference to the drawings and in combination with the embodiments. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts shall fall within the scope of protection of the present application.

[0087] In addition, it should be noted that the users described in this application (such as the users represented by the participants, the users represented by the first object, the users represented by the initiator, the users represented by the target object) can be distinguished by user identifiers. For example, the user identifier can be a login account. In this scenario, if different people log in with the same account, it can be considered that the above different people are the same user; if the same person logs in with different accounts respectively, it can be considered that the same person logging in with different accounts is a different user. For another example, in the state where the device is not logged in, user identifiers can also be assigned based on the device identifier of the device. In this scenario, if different people operate devices with the same device identifier, it can be considered that the above different people are the same user; if the same person operates devices with different device identifiers, it can be considered that the above same person is a different user.

[0088] To solve the technical problem of how to improve the efficiency of document operation and collaboration in the prior art, this application provides a method for processing document permissions, which can improve the efficiency of document operation and collaboration.

[0089] Figure 1A It is a schematic flowchart of a method for processing document permissions provided by an embodiment of this application. This method can be applied to one or more electronic devices such as smartphones, laptops, desktop computers, portable computers, servers, etc. In addition, the execution subject of this method can be hardware or software. When the above execution subject is hardware, the execution subject can be one or more of the above electronic devices. For example, a single electronic device can execute this method, or multiple electronic devices can cooperate with each other to execute this method. When the above execution subject is software, this method can be implemented as multiple software or software modules, or can also be implemented as a single software or software module. No specific limitation is made here.

[0090] As Figure 1A shown, this method specifically includes:

[0091] Step 101, in response to an operation trigger operation performed on a document, determine a first object indicated by the operation trigger operation, where the operation trigger operation is used for at least one second device to collaboratively process the document during the synchronous operation of the document with a first device.

[0092] In this embodiment, when a user or other object (such as an AI) performs an operation trigger operation on any document through the electronic device they control, the execution subject of this method (such as the above first device or the second electronic device) can determine the first object indicated by the operation trigger operation.

[0093] Among them, the first object can represent the user or other object that performs the drill trigger operation. Here, the first object can be any party that joins the drill.

[0094] The above drill trigger operation is used for at least one second device to cooperate in processing the above document during the synchronization of the drill (i.e., operation and / or demonstration) of the above document with the first device.

[0095] The first device and the second device can represent different electronic devices. As an example, the first device can represent the electronic device used by the follower (such as the meeting keynote speaker) during the drill, and the above second device can represent the electronic device used by the follower (such as the participants other than the meeting keynote speaker) during the above drill.

[0096] In addition, a drill (such as a meeting) process can involve one or more first devices (corresponding to multiple followers), and each first device can correspond to one or more second devices (corresponding to multiple followers).

[0097] The above document can be any document. As an example, the document can include, but is not limited to, documents in the following formats: doc format, docx format, ppt format, pptx format, rtf (Rich Text Format), html (Hyper Text Markup Language) format, etc. In addition, the document can also be an offline document stored locally or an online document stored in the cloud.

[0098] Among them, after the drill trigger operation performed on the document, the drill process can be entered. After performing the drill end operation (such as clicking the button for ending the drill operation) or triggering the drill end condition, the drill process can be terminated.

[0099] As an example, please refer to Figure 1B and 1C , Figure 1B and 1C which are the schematic diagrams of the application scenarios of a method for processing the permissions of a document provided by the embodiments of this application.

[0100] As Figure 1BAs shown, when the first object represents the initiator, after the drill trigger operation is executed, the initiator can initiate a meeting, upload the local documents in the electronic device (such as the first device) used by the initiator to the cloud, and at the same time, can invite users as participants. Here, user invitation can be achieved by displaying a QR code, sending a link, clicking on an avatar, etc. After that, the devices of the initiator and the participants enter the demonstration state (i.e., the drill state). After the demonstration ends, the demonstration can be exited and ended. When the first object represents a participant, they can join the link to log in by displaying a QR code, sending a link, clicking on an avatar, etc. After logging in, they can follow the presenter (such as the initiator) into the demonstration process. After the demonstration ends, the demonstration can be exited and ended.

[0101] As Figure 1C shown, when the first device (such as the large-screen computer in the figure) drills document A, the first device can select the size of the interface for drilling from the above document (as shown by the box selection area), so as to determine the data to be synchronized to the second device. After that, the first device can send the above data to the second device (such as the small-screen mobile phone in the figure). Thus, the first device and the second device can cooperate to process the above document during the synchronous drilling of the above document.

[0102] Step 102, determine the operation permission of the first object for the above document, so that the first object operates the above document under the above operation permission.

[0103] In this embodiment, as an example, if the operation permission of the first object for document A is "only view", then, during the above operation process, the first object can only view the above document A and cannot perform operations such as editing on the document A.

[0104] Here, when the operation permission of the first object for the document is cancelled, or when the first object requests to access a new document for which it has no operation permission, it can be determined that the first object enters the no-permission page. The no-permission page is used to display the document for which the first object has no operation permission (such as the view permission).

[0105] When the first object enters the no-permission page, if the first object is not the creator of the document for which the page is used to display, then, the operation process can be performed in any of the following ways:

[0106] Way 1, the first object can exit the operation process.

[0107] In the second method, the electronic device used by the first object can display information for applying for permissions. If the first object applies for (e.g., applies to the document creator) the operation permission within the preset time period, the first object can continue to enter the operation process after the above page is refreshed. If the first object fails to apply for the operation permission within the preset time period, the first object can exit the operation process.

[0108] In some alternative implementation manners of this embodiment, the following method can be adopted to determine the operation permission of the first object for the above document:

[0109] In the first step, when the first object is not the target object of the above document, a prompt message is generated.

[0110] Wherein, the above prompt message is used to prompt the first object to apply for permissions for the above document to obtain permissions.

[0111] The above target object can be an object with a preset attribute (e.g., its account is an authorized login account), or an object that performs a preset operation on the document (e.g., the above operation trigger operation). The target object can represent the creator of the above document, the administrator of the above document, or the initiator of the operation (e.g., meeting), the administrator of the operation (e.g., meeting).

[0112] In some cases, the target user has the highest permission for the above document or the above operation process. For example, the target user can be the document creator or the operation initiator.

[0113] In the second step, the permission obtained by the first object's application is determined as the operation permission of the first object for the above document.

[0114] As an example, when the first object is not the target object of the above document, a prompt message can be generated to prompt the first object to apply for permissions for the above document to obtain permissions. Specifically, the first object can apply for permissions from the above target object or the permission management object. Thus, the permission obtained by the first object's application (e.g., edit permission) is determined as the operation permission of the first object for the above document.

[0115] Please continue to refer to Figure 1D , Figure 1D which is a schematic diagram of an application scenario of another method for processing document permissions provided by the embodiment of the present application.

[0116] As shown in Figure 1DAs shown, when the first object is a target object other than the above-mentioned document, a prompt message "Permission Application" is generated. After the first object clicks "Permission Application", the document permission setter can set the permissions of the first object. Thus, the permissions obtained by the first object through application can be determined as the operation permissions of the first object for the above-mentioned document.

[0117] It can be understood that in the above optional implementation, when the first object is a target object other than the document, it can apply for the operation permissions of the first object for the document. In this way, the operation permissions of the target object other than the document can be set separately, thereby improving the effectiveness of controlling the operation permissions of the first object.

[0118] In some optional implementation manners of this embodiment, the following method can be adopted to determine the operation permissions of the first object for the above-mentioned document:

[0119] In the case of a permission allocation operation for the above-mentioned first object, determine the operation permissions of the first object as the operation permissions after the permission allocation operation.

[0120] Among them, the above permission allocation operation can be used to add, delete or adjust the operation permissions of the first object. The above permission allocation operation includes at least one of the following: permission allocation for the same above-mentioned document, permission allocation for different above-mentioned documents, permission allocation for the document content of the above-mentioned document, and permission allocation for different objects (such as documents, users, AI).

[0121] In practice, during the process of at least one second device synchronously operating and collaborating with the first device to process the document, one or more documents can be synchronously operated and collaboratively processed. Thus, the above permission allocation operation can perform permission allocation for the same document. For example, the permission allocation operation can be used to add the viewing permission for document A and the sharing permission for document A for the first object. Or, the above permission allocation operation can perform permission allocation for the document content of the document. For example, the permission allocation operation can be used to add the viewing permission for the document content A in document A, the editing permission for the document content B in document A, and the sharing permission for the document content C in document B for the first object. Or, the above permission allocation operation can perform permission allocation for different objects. For example, the permission allocation operation can be used to add the viewing permission for document A for object A and the viewing permission for document B for object B.

[0122] It can be understood that in the above optional implementation, the corresponding operation permissions can be allocated to the first object through the permission allocation operation. Thus, the efficiency of document operation and collaboration can be further improved through the allocation of the operation permissions of the first object.

[0123] In some application scenarios of the above optional implementation manners, the above permission allocation operation is performed during the drill process of the above document. The above permission allocation operation belongs to the first type and / or the second type. The first type indicates that the above permission allocation operation is used to determine the number of times of permission usage. The second type indicates that the above permission allocation operation is used to determine the time period of permission usage.

[0124] Here, the permission allocation operation can be used to determine the number of times of permission usage. For example, the permission allocation operation can be expressed as allocating the drill permission for Document A to the first object as "having one sharing permission". In this case, the first object can only share Document A once. The permission allocation operation can also be used to determine the time period of permission usage. For example, the permission allocation operation can be expressed as allocating the drill permission for Document A to the first object as "having the sharing permission from 9 to 10 o'clock". In this case, the first object can only share Document A from 9 to 10 o'clock. In addition, the permission allocation operation can also be used to determine the time period and the number of times of permission usage. For example, the permission allocation operation can be expressed as allocating the drill permission for Document A to the first object as "having one sharing permission from 9 to 10 o'clock". In this case, the first object can only share Document A once from 9 to 10 o'clock.

[0125] It can be understood that in the above application scenarios, the number of times of usage and / or the time period of the drill permission of the first object can be determined through the permission allocation operation. In this way, the fineness of the drill permission allocation can be improved.

[0126] In some optional implementation manners of this embodiment, the following method can be adopted to determine the drill permission of the first object for the above document:

[0127] In the first step, determine whether the first object is the role of the drill demonstration indicated by the above drill trigger operation, and obtain the fourth discrimination information.

[0128] Among them, the fourth discrimination information can indicate whether the first object is the role of the drill demonstration indicated by the above drill trigger operation (that is, the object that performs the drill trigger operation, such as the meeting keynote speaker).

[0129] In the second step, based on the above fourth discrimination information, determine the drill permission of the first object for the above document.

[0130] As an example, if the first object is the role of the drill demonstration indicated by the above drill trigger operation, then it can be determined that the drill permission of the first object for the above document is the first permission. If the first object is not the role of the drill demonstration indicated by the above drill trigger operation, then it can be determined that the drill permission of the first object for the above document is the second permission.

[0131] Among them, the scope of authority of the first authority can be greater than that of the second authority. For example, the first authority can include: viewing authority and editing authority, and the second authority can only include viewing authority.

[0132] It can be understood that in the above optional implementation manners, the operation authority of the first object for the above document can be determined based on whether the first object is the role of the operation demonstration triggered by the above operation trigger operation, so that different operation authorities can be assigned to different roles, thereby improving the refinement degree of operation authority assignment.

[0133] In some optional implementation manners of this embodiment, after determining the first object of the operation triggered by the above operation trigger operation, the following steps can also be performed:

[0134] First step, in the case of performing a removal operation on the above first object, determine whether the above first object is the initiator of the above operation trigger operation, and obtain a second discrimination message.

[0135] Among them, the second discrimination message can indicate whether the first object is the initiator of the above operation trigger operation.

[0136] Second step, based on the above second discrimination message, determine whether the operation triggered by the above operation trigger operation ends.

[0137] As an example, if the first object is the initiator of the above operation trigger operation, then it can be determined that the operation triggered by the above operation trigger operation ends. If the first object is not the initiator of the above operation trigger operation, then it can be determined that the operation triggered by the above operation trigger operation does not end, and the above operation process can continue.

[0138] It can be understood that in the above optional implementation manners, in the case of removing the first object, it can be determined whether to end the operation based on whether the first object is the initiator of the operation trigger operation, so that the convenience of operation process control can be improved.

[0139] In some optional implementation manners of this embodiment, after determining the first object of the operation triggered by the above operation trigger operation, the following steps can also be performed:

[0140] First step, in the case of performing a removal operation on the above first object, determine the document authority of the above document.

[0141] Among them, the above document authority can indicate whether "everyone can view".

[0142] Second step, based on the above document authority, determine the operation authority of the above first object for the above document.

[0143] As an example, when the document permission is "viewable by all", removing the first object is regarded as adjusting its operation permission to "viewable". Specifically, since the document permission is "viewable by all", for any object, whether it participates in the operation or not, it can have the viewing permission for this document. Therefore, in this case, even if the first object is removed from the operation process, after it exits the operation process, it can still have the viewing permission for this document.

[0144] It can be understood that in the above optional implementation manner, when the first object is removed, the operation permission of the first object for the document can be determined based on the document permission of the document. In this way, the operation permission of the first object for the document can be adjusted in time after the first object is removed.

[0145] The method for processing the permission of a document provided by the embodiments of the present application can determine the first object indicated by the operation trigger operation in response to the operation trigger operation performed on the document, where the operation trigger operation is used for at least one second device to cooperate in processing the document during the process of synchronously operating the document with the first device. After that, the operation permission of the first object for the document is determined, so that the first object operates the document under the operation permission. Thus, during the process of at least one second device synchronously operating and cooperating in processing the document with the first device, it can be ensured that the first object operates the document under the operation permission. In this way, by controlling the operation permission of the first object, it can be ensured that the document operation and cooperation are carried out under the corresponding operation permission, thereby improving the efficiency of document operation and cooperation.

[0146] Figure 2 It is a schematic flowchart of another method for processing the permission of a document provided by the embodiments of the present application. As Figure 2 shown, the method specifically includes:

[0147] Step 201, in response to the operation trigger operation performed on the document, determine the first object indicated by the operation trigger operation, where the operation trigger operation is used for at least one second device to cooperate in processing the document during the process of synchronously operating the document with the first device.

[0148] In this embodiment, step 201 is basically the same as step 101 in the corresponding embodiment of FIG. 1, and will not be elaborated here.

[0149] Step 202, determine whether the first object has the operation permission for the document during the target time period, and obtain the first discrimination information, where the target time period is before the operation trigger operation is detected.

[0150] In this embodiment, it is possible to determine whether the first object has the operation permission for the above-mentioned document before detecting the above-mentioned drill trigger operation (i.e., before the drill starts, such as before the meeting starts).

[0151] The first discrimination information can indicate whether the first object has the operation permission for the above-mentioned document during the target period.

[0152] Step 203: Based on the above first discrimination information, determine the operation permission of the first object for the above-mentioned document, so that the first object can operate the above-mentioned document under the above operation permission.

[0153] In some optional implementation manners of this embodiment, the following method can be adopted to determine the operation permission of the first object for the above-mentioned document based on the above first discrimination information:

[0154] When the above first discrimination information indicates that the first object has the operation permission for the above-mentioned document during the above target period, determine the operation permission that the first object has during the above target period as the operation permission of the first object for the above-mentioned document during the above operation period.

[0155] Here, before detecting the above-mentioned drill trigger operation, if the first object has the operation permission for the above-mentioned document, then the first user can continue to use this operation permission during the operation process.

[0156] When the above first discrimination information indicates that the first object does not have the operation permission for the above-mentioned document during the above target period, determine the preset permission as the operation permission of the first object for the above-mentioned document during the above operation period.

[0157] Here, before detecting the above-mentioned drill trigger operation, if the first object does not have the operation permission for the above-mentioned document, then the first user can adopt the preset operation permission during the operation process, such as only viewing.

[0158] It can be understood that in the above optional implementation manner, the first object can preferentially continue to use the operation permission it had before the operation. And when the first object does not have any operation permission before the operation, once the operation starts, it can have the preset operation permission for the document. In this way, the efficiency of setting the operation permission can be improved.

[0159] It should be noted that in addition to the content recorded above, this embodiment may also include the corresponding technical features described in the embodiment corresponding to FIG. 1, so as to achieve the technical effects of the method for processing the permissions of the document shown in FIG. 1. For specific details, please refer to the relevant description in FIG. 1. For the sake of brief description, it will not be elaborated here.

[0160] The method for processing the permissions of a document provided by an embodiment of the present application can determine different operation permissions for a first object with different operation permissions before the drill. Thus, the determination of the operation permissions can be more matched with the first object.

[0161] Figure 3A It is a schematic flowchart of another method for processing the permissions of a document provided by an embodiment of the present application. As Figure 3A shown, the method specifically includes:

[0162] Step 301, in response to an operation trigger operation performed on the document, determine the first object indicated by the operation trigger operation, where the operation trigger operation is used for at least one second device to cooperate in processing the document during the synchronous operation of the document with the first device.

[0163] In this embodiment, step 301 is basically the same as step 101 in the corresponding embodiment of FIG. 1, and will not be elaborated here.

[0164] Step 302, in response to an operation trigger operation performed on the document, determine whether the document is a collaborative document, and obtain third discrimination information.

[0165] In this embodiment, in the case of an operation trigger operation performed on the document, it can be determined whether the document is a collaborative document, and third discrimination information is obtained.

[0166] Among them, a collaborative document can be processed collaboratively by at least two users through the electronic devices they use. The collaborators of the collaborative document have permissions for the collaborative document, for example, permissions such as only viewing, editing, sharing, etc.

[0167] The third discrimination information can indicate whether the document is a collaborative document.

[0168] Step 303, based on the third discrimination information, determine the operation permissions of the first object for the document, so that the first object operates the document under the operation permissions.

[0169] In this embodiment, if the third discrimination information indicates that the document is a collaborative document, then the operation permissions of the first object for the document can be determined as the third permission. If the third discrimination information indicates that the document is not a collaborative document, then the operation permissions of the first object for the document can be determined as the fourth permission.

[0170] As an example, the above-mentioned third permission may be the operation permission of the first object for the collaborative document. That is, for the collaborative document, the first object can continue to use its permission for the collaborative document during the operation process. The above-mentioned fourth permission may be a preset operation permission (such as only viewing). In addition, the fourth permission can also be determined based on the identity of the first object, the document permission of the document, etc.

[0171] As an example, please refer to Figure 3B and 3C , Figures 3B - 3C is a schematic diagram of the application scenario for Figure 3A .

[0172] As Figure 3B shown, in the case where the above-mentioned document is a collaborative document (that is, an operation trigger operation is performed on the collaborative document), if the first object is the initiator, and before joining the face-to-face (that is, before the operation trigger operation), the first object already has the permission for the above-mentioned collaborative document (such as having permission A), then, during the face-to-face (that is, during the operation process), the first object can maintain the original permission, that is, determine that the operation permission of the first object for the collaborative document is the above-mentioned permission A.

[0173] During the face-to-face process, if the first object is removed (such as the document creator removes the initiator permission), then, the face-to-face ends (that is, the operation ends), and all members (such as the initiator and the participants) end the face-to-face, and have no document permission.

[0174] During the face-to-face process, if the permission of the first object is adjusted (such as the document creator adjusts the permission of the first object as the initiator), then, after the face-to-face ends (that is, the operation ends), the first object can retain the adjusted permission.

[0175] During the face-to-face process, if the collaboration (operation) is closed, then, the face-to-face ends (that is, the operation ends), and all members (such as the initiator and the participants) end the face-to-face, and have no document permission.

[0176] During the face-to-face process, if the first object as the initiator closes the collaboration, then, a pop-up window can be used to confirm whether to exit. If it is confirmed to exit, then the face-to-face ends (that is, the operation ends), and all members (such as the initiator and the participants) end the face-to-face, and the participants other than the initiator have no document permission.

[0177] In the case where the above document is a collaborative document (i.e., an operation trigger operation is performed on the collaborative document), if the first object is a participant other than the initiator, and the first object already has permissions for the above collaborative document (such as having permission B) before joining the face-to-face session (i.e., before the operation trigger operation), then, during the face-to-face session (i.e., during the operation process), the first object can maintain the original permissions and determine that the operation permissions of the first object for the collaborative document are the above permission B.

[0178] During the face-to-face session, if the first object is removed, then the first object immediately exits and has no document operation permissions.

[0179] During the face-to-face session, if the permissions of the first object are adjusted, then after the face-to-face session ends (i.e., after the operation ends), the first object can retain the adjusted permissions.

[0180] Here, when the document permissions are viewable by all, removing a collaborator (the first object) is regarded as adjusting their permissions to viewable.

[0181] During the face-to-face session, if the permissions of the first object are not adjusted and the collaboration (operation) is closed, then after the face-to-face session ends (i.e., after the operation ends), the original permissions of the first object are retained.

[0182] In the case where the above document is a collaborative document (i.e., an operation trigger operation is performed on the collaborative document), if the first object is a participant other than the initiator, and the first object does not have permissions for the above collaborative document before joining the face-to-face session (i.e., before the operation trigger operation), then, during the face-to-face session (i.e., during the operation process), the first object can have temporary permissions, such as only view. After the face-to-face session ends, the first object no longer has the above temporary permissions.

[0183] During the face-to-face session, if the first object is removed, then the first object immediately exits and has no document operation permissions.

[0184] During the face-to-face session, if the permissions of the first object are adjusted, then after the face-to-face session ends (i.e., after the operation ends), the first object can retain the adjusted permissions.

[0185] During the face-to-face session, if the permissions of the first object are not adjusted and the collaboration (operation) is closed, then after the face-to-face session ends (i.e., after the operation ends), the original permissions of the first object are retained.

[0186] Such as Figure 3CAs shown, in the case where the above document is not a collaborative document (i.e., the drill trigger operation is performed on a non-collaborative document), if the first object is the initiator, and the first object already has permissions for the above document (such as permission C) before joining the face-to-face session (i.e., before the drill trigger operation), then, during the face-to-face session (i.e., during the drill), the first object can maintain the original permissions, that is, determine that the drill permissions of the first object for the document are the above permission C.

[0187] During the face-to-face session, if the collaboration (drill) is closed by an object other than the first object, then the face-to-face session ends (i.e., the drill ends), and all participants (such as the initiator and the attendees) end the face-to-face session and have no document permissions.

[0188] During the face-to-face session, if the collaboration (drill) is closed by the first object, then a confirmation dialog box can be popped up to confirm whether to exit the collaboration (drill). If it is confirmed to exit, then the face-to-face session ends (i.e., the drill ends), and the attendees other than the initiator have no document permissions.

[0189] During the face-to-face session, if the permissions of objects other than the first object have not been adjusted, then after the face-to-face session ends (i.e., the drill ends), the permissions of each object can be restored to the state before the drill is started, and the permissions are automatically withdrawn.

[0190] During the face-to-face session, if the permissions of objects other than the first object have been adjusted, then when the face-to-face session ends (i.e., the drill ends), a confirmation dialog box pops up to confirm whether to retain the permissions. If it is confirmed to retain, then the adjusted permissions are retained.

[0191] In the case where the above document is a non-collaborative document (i.e., the drill trigger operation is performed on a non-collaborative document), if the first object is an attendee other than the initiator, and the first object does not have permissions for the above document before joining the face-to-face session (i.e., before the drill trigger operation), then during the face-to-face session (i.e., during the drill), the first object can have temporary permissions, such as only viewing.

[0192] During the face-to-face session, if the first object is removed, then the first object immediately exits and has no document operation permissions.

[0193] During the face-to-face session, if the permissions of the first object have been adjusted, then after the face-to-face session ends (i.e., the drill ends), the first object can retain the adjusted permissions.

[0194] During the face-to-face session, if the permissions of the first object have not been adjusted and the collaboration (drill) is closed, then the permissions of the first object are automatically withdrawn after the face-to-face session ends (i.e., the drill ends).

[0195] It should be noted that, in addition to the content described above, this embodiment may further include the corresponding technical features described in the above embodiments, so as to achieve the technical effects of the document permission processing methods shown in the above embodiments. For specific details, please refer to the above description. For the sake of concise description, it will not be elaborated here.

[0196] The document permission processing method provided by the embodiments of this application can determine the operation permissions of the first object for collaborative documents and non - collaborative documents in different ways, so that operation permission settings based on document types can be achieved.

[0197] Figure 4 It is a schematic flowchart of another document permission processing method provided by the embodiments of this application. As Figure 4 shown, this method specifically includes:

[0198] Step 601, in response to an operation trigger operation performed on a document, determine the first object indicated by the operation trigger operation, where the operation trigger operation is used for at least one second device to collaborate in processing the document during the synchronous operation of the document with the first device.

[0199] In this embodiment, step 601 is basically the same as step 101 in the corresponding embodiment of FIG. 1, and will not be elaborated here.

[0200] Step 602, determine whether the first object is the initiator of the operation trigger operation.

[0201] In this embodiment, the initiator of the operation trigger operation can be the object that performs the operation trigger operation, such as a user, an electronic device, an AI, etc.

[0202] In this embodiment, there may be multiple first objects. For each first object, it can belong to the initiator or the non - initiator. And the above - mentioned first object (i.e., the first object mentioned in step 601) can be one of the many first objects.

[0203] Step 603, when the first object is the initiator and the first object assigns permissions to non - initiators, in response to a close operation of the operation indicated by the operation trigger operation, determine whether to retain the operation permissions of the non - initiators for the document, so that the first object can operate the document under the operation permissions, where the non - initiator is the first object other than the initiator among the first objects.

[0204] In this embodiment, in the case of closing the operation, it can be determined whether to retain the operation of the non - initiator for the document, that is, whether to allow the non - initiator to still retain the operation permissions after the operation interpretation.

[0205] AsFigure 3B As shown, in the case where the above document is a collaborative document (i.e., an operation trigger operation is performed on the collaborative document), if a first object is the initiator, and the first object already has permissions for the above collaborative document (such as having permission A) before joining the face-to-face session (i.e., before the operation trigger operation), then during the face-to-face session (i.e., during the operation process), the first object can maintain the original permissions, that is, determine that the operation permissions of the first object for the collaborative document are the above permission A.

[0206] During the face-to-face session, if the first object is removed (such as the document creator removes the first object who is the initiator), then the face-to-face session ends (i.e., the operation ends), and all members (such as the initiator and non-initiators) end the face-to-face session and have no document permissions.

[0207] During the face-to-face session, if the permissions of the first object are adjusted (such as the document creator adjusts the permissions of the first object who is the initiator), then after the face-to-face session ends (i.e., the operation ends), the first object can retain the adjusted permissions.

[0208] During the face-to-face session, if the collaboration (operation) is closed, then the face-to-face session ends (i.e., the operation ends), and all members (such as the initiator and non-initiators) end the face-to-face session and have no document permissions.

[0209] During the face-to-face session, if the first object who is the initiator closes the collaboration, then a confirmation dialog box can be popped up to confirm whether to exit. If confirmed to exit, then the face-to-face session ends (i.e., the operation ends), and all members (such as the initiator and participants) end the face-to-face session, and non-initiators have no document permissions.

[0210] In the case where the above document is a collaborative document (i.e., an operation trigger operation is performed on the collaborative document), if a first object is a non-initiator, and the first object already has permissions for the above collaborative document (such as having permission B) before joining the face-to-face session (i.e., before the operation trigger operation), then during the face-to-face session (i.e., during the operation process), the first object can maintain the original permissions, and determine that the operation permissions of the first object for the collaborative document are the above permission B.

[0211] During the face-to-face session, if the first object is removed, then the first object immediately exits and has no document operation permissions (i.e., operation permissions).

[0212] During the face-to-face session, if the permissions of the first object are adjusted, then after the face-to-face session ends (i.e., the operation ends), the first object can retain the adjusted permissions.

[0213] Here, when the document permission is set to be viewable by all, removing a collaborator (the first object) is regarded as adjusting their permission to view only.

[0214] During the face-to-face session, if the permission of the first object has not been adjusted and the collaboration (drill) is closed, then after the face-to-face session ends (i.e., the drill ends), the original permission of the first object is retained.

[0215] In the case where the above document is a collaborative document (i.e., the drill trigger operation is performed on the collaborative document), if a first object is not the initiator and does not have permission for the above collaborative document before joining the face-to-face session (i.e., before the drill trigger operation), then during the face-to-face session (i.e., during the drill), the first object can have temporary permission, such as view only. After the face-to-face session ends, the first object no longer has the above temporary permission (i.e., the above drill permission).

[0216] During the face-to-face session, if the first object is removed, then the first object immediately exits and has no document operation permission.

[0217] During the face-to-face session, if the permission of the first object has been adjusted, then after the face-to-face session ends (i.e., the drill ends), the first object can retain the adjusted permission (i.e., the above drill permission).

[0218] During the face-to-face session, if the permission of the first object has not been adjusted and the collaboration (drill) is closed, then after the face-to-face session ends (i.e., the drill ends), the original permission of the first object is retained (i.e., the above drill permission).

[0219] As Figure 3C shown, in the case where the above document is not a collaborative document (i.e., the drill trigger operation is performed on a non-collaborative document), if a first object is the initiator and has permission for the above document before joining the face-to-face session (i.e., before the drill trigger operation) (for example, has permission C), then during the face-to-face session (i.e., during the drill), the first object can maintain the original permission, that is, it is determined that the drill permission of the first object for the document is the above permission C.

[0220] During the face-to-face session, if the collaboration (drill) is closed by an object other than the first object, then the face-to-face session ends (i.e., the drill ends), and all participants (such as the initiator and non-initiators) end the face-to-face session and have no document permission.

[0221] During the face-to-face session, if the collaboration (drill) is closed by the first object, then a confirmation dialog box can be popped up to confirm whether to exit the collaboration (drill). If confirmed to exit, then the face-to-face session ends (i.e., the drill ends), and the non-initiator has no document permission.

[0222] During the face-to-face process, if the permissions of other objects except the first object have not been adjusted, then after the face-to-face ends (i.e., the operation ends), the permissions of each object can be restored to the state before the operation starts, and the permissions are automatically withdrawn.

[0223] During the face-to-face process, if the permissions of other objects except the first object have been adjusted, then when the face-to-face ends (i.e., the operation ends), a pop-up window will confirm whether to retain the permissions. If it is confirmed to retain, the adjusted permissions will be retained.

[0224] In the case where the above document is a non-collaborative document (i.e., the operation trigger operation is performed on a non-collaborative document), if a first object is not the initiator, and the first object does not have permissions for the above document before joining the face-to-face (i.e., before the operation trigger operation), then during the face-to-face (i.e., during the operation), the first object can have temporary permissions, such as only viewing.

[0225] During the face-to-face process, if the first object is removed, then the first object immediately exits and has no document operation permissions.

[0226] During the face-to-face process, if the permissions of the first object have been adjusted, then after the face-to-face ends (i.e., the operation ends), the first object can retain the adjusted permissions.

[0227] During the face-to-face process, if the permissions of the first object have not been adjusted and the collaboration (operation) is closed, then after the face-to-face ends (i.e., the operation ends), the permissions of the first object are automatically withdrawn.

[0228] In practice, it can be determined by the initiator whether to retain the operation permissions of the non-initiator for the document; it can also be determined whether to retain the operation permissions of the non-initiator for the document based on whether the non-initiator has permissions for the document before the operation and whether it is a collaborative document.

[0229] It should be noted that in addition to the above-mentioned content, this embodiment can also include the corresponding technical features described in the above embodiments, so as to achieve the technical effects of the document permission processing methods shown in the above embodiments. For specific details, please refer to the above description. For the sake of brevity, it will not be elaborated here.

[0230] The document permission processing method provided by the embodiment of the present application can determine whether to retain the operation permissions of the non-initiator for the above document when closing the operation, thereby reducing or even avoiding misoperations of the non-initiator on the document after the operation ends.

[0231] Figure 5 It is a schematic structural diagram of a document permission processing device provided by an embodiment of the present application. Specifically, it includes:

[0232] A first determination unit 601, configured to determine a first object indicated by the drill trigger operation in response to a drill trigger operation performed on a document, where the drill trigger operation is used for at least one second device to collaboratively process the document during the process of synchronously drilling the document with a first device;

[0233] A second determination unit 602, configured to determine an operation permission of the first object for the document, so that the first object operates the document under the operation permission.

[0234] In a possible implementation manner, determining the operation permission of the first object for the document includes:

[0235] When the first object is not the target object of the document, generating a prompt message, where the prompt message is used to prompt the first object to apply for permission for the document to obtain permission;

[0236] Determining the permission obtained by the first object's application as the operation permission of the first object for the document.

[0237] In a possible implementation manner, determining the operation permission of the first object for the document includes:

[0238] Determining whether the first object has an operation permission for the document during a target period to obtain first discrimination information, where the target period is before the drill trigger operation is detected;

[0239] Based on the first discrimination information, determining the operation permission of the first object for the document.

[0240] In a possible implementation manner, based on the first discrimination information, determining the operation permission of the first object for the document includes:

[0241] When the first discrimination information indicates that the first object has an operation permission for the document during the target period, determining the operation permission that the first object has during the target period as the operation permission of the first object for the document during the drill period;

[0242] When the first discrimination information indicates that the first object does not have an operation permission for the document during the target period, determining a preset permission as the operation permission of the first object for the document during the drill period.

[0243] In a possible implementation manner, determining the operation permission of the first object for the document includes:

[0244] In response to a permission assignment operation for the above-mentioned first object, determine that the operation permission of the above-mentioned first object is the operation permission after the above-mentioned permission assignment operation, where the above-mentioned permission assignment operation includes at least one of the following: performing permission assignment for the same above-mentioned document, performing permission assignment for different above-mentioned documents, performing permission assignment for the document content of the above-mentioned document, and performing permission assignment for different objects.

[0245] In a possible implementation manner, the above-mentioned permission assignment operation is executed during the operation process of the above-mentioned document, and the above-mentioned permission assignment operation belongs to the first type and / or the second type. The first type indicates that the above-mentioned permission assignment operation is used to determine the number of times of permission usage, and the second type indicates that the above-mentioned permission assignment operation is used to determine the time period of permission usage.

[0246] In a possible implementation manner, the above-mentioned determination of the operation permission of the above-mentioned first object for the above-mentioned document includes:

[0247] In response to an operation trigger operation performed on the document, determine whether the above-mentioned document is a collaborative document to obtain third discrimination information;

[0248] Based on the above-mentioned third discrimination information, determine the operation permission of the above-mentioned first object for the above-mentioned document.

[0249] In a possible implementation manner, the above-mentioned determination of the operation permission of the above-mentioned first object for the above-mentioned document includes:

[0250] Determine whether the above-mentioned first object is the initiator of the above-mentioned operation trigger operation;

[0251] When the above-mentioned first object is the above-mentioned initiator and the above-mentioned first object performs permission assignment to non-initiators, in response to a close operation of the operation indicated by the above-mentioned operation trigger operation, determine whether to retain the operation permission of the above-mentioned non-initiators for the above-mentioned document, where the above-mentioned non-initiators are the first objects other than the above-mentioned initiator among the above-mentioned first objects.

[0252] In a possible implementation manner, the above-mentioned determination of the operation permission of the above-mentioned first object for the above-mentioned document includes:

[0253] Determine whether the above-mentioned first object is the role of the operation demonstration indicated by the above-mentioned operation trigger operation to obtain fourth discrimination information;

[0254] Based on the above-mentioned fourth discrimination information, determine the operation permission of the above-mentioned first object for the above-mentioned document.

[0255] In a possible implementation manner, after determining the first object of the operation indicated by the above-mentioned operation trigger operation, the above-mentioned device further includes:

[0256] A third determination unit (not shown in the figure) is configured to, in response to a removal operation on the first object, determine whether the first object is the initiator of the exercise trigger operation, and obtain second discrimination information; based on the second discrimination information, determine whether the exercise indicated by the exercise trigger operation ends; and / or

[0257] A fourth determination unit (not shown in the figure) is configured to, in response to a removal operation on the first object, determine the document permission of the document; based on the document permission, determine the exercise permission of the first object for the document.

[0258] The document permission processing device provided in this embodiment may be the document permission processing device shown in Figure 5 The document permission processing device shown in the figure can execute all steps of the above-mentioned document permission processing methods, and further achieve the technical effects of the above-mentioned document permission processing methods. For specific details, please refer to the above relevant descriptions. For the sake of brevity, it will not be elaborated here.

[0259] Figure 6 FIG. is a schematic structural diagram of an electronic device provided in an embodiment of the present application. Figure 6 As shown, the electronic device 500 includes at least one processor 501, a memory 502, at least one network interface 504, and other user interfaces 503. Each component in the electronic device 500 is coupled together through a bus system 505. It can be understood that the bus system 505 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 505 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, in Figure 6 all buses are labeled as the bus system 505.

[0260] Among them, the user interface 503 may include a display, a keyboard, or a pointing device (for example, a mouse, a trackball, a touchpad, or a touch screen, etc.).

[0261] It can be understood that the memory 502 in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synch link dynamic random access memory (SLDRAM), and direct rambus random access memory (DRRAM). The memory 502 described herein is intended to include but not be limited to these and any other suitable types of memory.

[0262] In some embodiments, the memory 502 stores the following elements, executable units, or data structures, or subsets thereof, or extended sets thereof: an operating system 5021 and an application program 5022.

[0263] Among them, the operating system 5021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., and is used to implement various basic services and process hardware-based tasks. The application program 5022 includes various application programs, such as a media player and a browser, etc., and is used to implement various application services. The program for implementing the method of the embodiments of the present application can be included in the application program 5022.

[0264] In this embodiment, by invoking the program or instruction stored in the memory 502, specifically, the program or instruction stored in the application program 5022, the processor 501 is used to execute the method steps provided in each method embodiment, for example, including:

[0265] In response to an exercise trigger operation performed on a document, determine a first object indicated by the exercise trigger operation, where the exercise trigger operation is for at least one second device to cooperate in processing the document during the synchronization of the exercise of the document with a first device;

[0266] Determine the exercise permission of the first object for the document, so that the first object exercises the document under the exercise permission.

[0267] The method disclosed in the embodiments of the present application can be applied to or implemented by a processor 501. The processor 501 may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the above method can be completed by the integrated logic circuit in the hardware of the processor 501 or the instructions in the form of software. The above processor 501 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor or executed by a combination of hardware and software units in the decoding processor. The software unit may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory 502, and the processor 501 reads the information in the memory 502 and combines its hardware to complete the steps of the above method.

[0268] It will be appreciated that the embodiments described herein may be implemented using hardware, software, firmware, middleware, microcode, or any combination thereof. For hardware implementation, the processing unit may be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the above functions of the present application, or any combination thereof.

[0269] For software implementation, the above-described techniques herein may be implemented by units that execute the above functions herein. The software code may be stored in a memory and executed by a processor. The memory may be implemented within the processor or externally to the processor.

[0270] The electronic device provided in this embodiment may be an electronic device as shown in Figure 6 and can execute all steps of the permission processing method for each of the above-described documents, thereby achieving the technical effects of the permission processing methods for each of the above-described documents. For specific details, please refer to the above relevant descriptions. For the sake of brevity, it will not be elaborated herein.

[0271] The embodiments of the present application also provide a storage medium (computer-readable storage medium). The storage medium stores one or more programs herein. Among them, the storage medium may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as read-only memory, flash memory, hard disk, or solid-state drive; the memory may also include a combination of the above types of memory.

[0272] When one or more programs in the storage medium can be executed by one or more processors to implement the above-described document permission processing method executed on the electronic device side.

[0273] The above processor is used to execute the document permission processing program stored in the memory to implement the following steps of the document permission processing method executed on the electronic device side:

[0274] In response to an exercise trigger operation performed on a document, determine a first object indicated by the exercise trigger operation, where the exercise trigger operation is used for at least one second device to cooperate in processing the document during the synchronous exercise of the document with the first device;

[0275] Determine the operation permission of the above first object for the above document, so that the above first object operates the above document under the above operation permission.

[0276] Those skilled in the art should further realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of the examples have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Skilled artisans can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0277] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented by hardware, software modules executed by a processor, or a combination of the two. The software modules can be placed in a random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0278] It should be understood that the terms used herein are for the purpose of describing specific example embodiments only and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" as used herein may also include the plural forms. The terms "comprising", "including", "containing", and "having" are inclusive and thus specify the presence of the stated features, steps, operations, elements, and / or components, but do not preclude 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 to be construed as necessarily requiring them to be executed in the particular order described or illustrated, unless the execution order is explicitly stated. It should also be understood that additional or alternative steps may be used.

[0279] The above description is only a specific implementation manner of the present invention, enabling those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to these embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for processing the permissions of a document, characterized in that The method includes: In response to an operation trigger operation performed on a document, determining a first object indicated by the operation trigger operation, where the operation trigger operation is used for at least one second device to cooperate in processing the document during the process of synchronously operating the document with a first device; Determining the operation permission of the first object for the document, so that the first object operates the document under the operation permission.

2. The method according to claim 1, wherein The determining the operation permission of the first object for the document includes: In the case where the first object is not the target object of the document, generating a prompt message, where the prompt message is used to prompt the first object to apply for permission for the document to obtain permission; Determining the permission obtained by the first object's application as the operation permission of the first object for the document.

3. The method according to claim 1, characterized in that The determining the operation permission of the first object for the document includes: Determining whether the first object has the operation permission for the document during a target period to obtain first discrimination information, where the target period is before the operation trigger operation is detected; Based on the first discrimination information, determining the operation permission of the first object for the document.

4. The method according to claim 3, characterized in that, The determining the operation permission of the first object for the document based on the first discrimination information includes: In the case where the first discrimination information indicates that the first object has the operation permission for the document during the target period, determining the operation permission that the first object has during the target period as the operation permission of the first object for the document during the operation period; In the case where the first discrimination information indicates that the first object does not have the operation permission for the document during the target period, determining a preset permission as the operation permission of the first object for the document during the operation period.

5. The method according to claim 1, characterized in that The determining the operation permission of the first object for the document includes: In response to a permission allocation operation for the first object, determining the operation permission of the first object as the operation permission after the permission allocation operation is allocated, where the permission allocation operation includes at least one of the following: allocating permissions for the same document, allocating permissions for different documents, allocating permissions for the document content of the document, and allocating permissions for different objects.

6. The method according to claim 5, wherein The permission allocation operation is performed during the operation process of the document, and the permission allocation operation belongs to the first type and / or the second type. The first type indicates that the permission allocation operation is used to determine the number of times of permission use, and the second type indicates that the permission allocation operation is used to determine the time period of permission use.

7. The method according to claim 1, wherein The determining the operation permission of the first object for the document includes: In response to an operation trigger operation performed on a document, determining whether the document is a collaborative document to obtain third discrimination information; Based on the third discrimination information, determining the operation permission of the first object for the document.

8. The method according to claim 1, wherein The determining the operation permission of the first object for the document includes: Determining whether the first object is the initiator of the operation trigger operation; When the first object is the initiator and the first object assigns permissions to non-initiators, in response to a close operation of the drill triggered by the operation instruction, determine whether to retain the drill permissions of the non-initiator for the document, where the non-initiator is the first object other than the initiator among the first objects.

9. The method according to claim 1, wherein The determination of the drill permissions of the first object for the document includes: Determine whether the first object is the role of the drill demonstration triggered by the operation instruction to obtain fourth discrimination information; Based on the fourth discrimination information, determine the drill permissions of the first object for the document.

10. The method according to any one of claims 1-9, characterized in that, After determining the first object of the drill triggered by the operation instruction, the method further includes: In response to a removal operation on the first object, determine whether the first object is the initiator of the drill trigger operation to obtain second discrimination information; based on the second discrimination information, determine whether the drill triggered by the operation instruction ends; and / or In response to a removal operation on the first object, determine the document permissions of the document; based on the document permissions, determine the drill permissions of the first object for the document.

11. A permission management device for a document, characterized in that, The device includes: A first determination unit, configured to determine the first object indicated by the drill trigger operation in response to a drill trigger operation performed on a document, where the drill trigger operation is used for at least one second device to cooperate in processing the document during a synchronous drill of the document with the first device; A second determination unit, configured to determine the drill permissions of the first object for the document so that the first object drills the document under the drill permissions.

12. An electronic device, characterized in that, Includes: A memory, configured to store a computer program; A processor, configured to execute the computer program stored in the memory, and when the computer program is executed, implement the method according to any one of claims 1-10 above.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, implement the method according to any one of claims 1-10 above.

Images