User authority management method and device, equipment and medium

Abstract

The invention provides a user authority management method, which can be used in an enterprise-level mobile office platform, and comprises the following steps: a server receives an authority setting request sent by a first terminal, the first terminal is one of subordinate terminals of the server, and the authority setting request comprises the authority of a user account in the server; the server sets the permission of a user account in the server according to the permission setting request; and the server sends a permission allocation result to at least one terminal subordinate to the server, wherein the permission of the user account in the server is recorded in the permission allocation result. The invention further provides a user authority management device, computer equipment and a medium, authority management of the user account is achieved by obtaining the authority setting request edited by the terminal, the group management capability is perfected, and the application efficiency in the aspect of enterprise management is improved.

Description

[0001] This application is a divisional application for the Chinese patent application with application number 201910749572.2, application date August 14, 2019, and invention name “A user authority management method, device, equipment and medium”. Technical Field

[0002] The present invention relates to the field of software technology, and more specifically, to a user authority management method, device, equipment and medium. Background Art

[0003] With the development of instant messaging technology, some enterprise-level mobile office platforms have been born. In addition to providing office communication, announcements and attendance within the enterprise, user accounts within the enterprise group chat can also initiate chats or add friend relationships with user accounts outside the enterprise group chat.

[0004] For the purpose of internal information security, the administrator of the enterprise group chat hopes to manage the behavior of internal user accounts in the enterprise group chat to maintain the company's information security. For example, in the scenario of external service, in order to prevent employees from taking away the company's customers, the company requires that group members cannot privately add relationships or have private chats in the external service group chat. However, in the prior art, no relevant technical solution has been provided to achieve the management of user-related permissions in the enterprise group chat.

[0005] Therefore, the above problems have yet to be solved. Summary of the invention

[0006] In view of this, in order to solve the above problems, the technical solution provided by the present invention is as follows:

[0007] A user rights management method, comprising:

[0008] The server receives a permission setting request sent by a first terminal, where the first terminal is one of the terminals under the server, and the permission setting request includes a first permission of a user account of a group in the server, where the first permission is used to limit the behavior permission of the user account of the group in the server to interact with other user accounts, including: prohibiting at least one of private chatting or prohibiting adding friends;

[0009] The server sets a first permission for a user account of a group in the server according to the permission setting request;

[0010] The server sends a permission allocation result to at least one terminal under the server, wherein the first permission is recorded in the permission allocation result.

[0011] A user rights management method, comprising:

[0012] The terminal displays a group conversation interface including interactive controls;

[0013] The terminal responds to the interactive operation on the interactive control in the group conversation interface and displays an information interface including a list of group members;

[0014] The terminal responds to a selection operation of at least one group member icon in the group member list by displaying a group member information management interface corresponding to the group member icon, wherein when the group member identifier corresponding to the group member icon is set to a first permission, a permission setting request is generated, and the first permission includes: prohibiting at least one of private chatting or prohibiting adding friends;

[0015] The terminal sends the permission setting request to the server.

[0016] A user rights management device, comprising:

[0017] a first receiving unit, the receiving unit being configured to receive a permission setting request sent by a first terminal, the first terminal being one of the terminals under the server, the permission setting request including a first permission of a user account in the server, the first permission being used to limit a behavior permission of the user account in the server;

[0018] a setting unit, the setting unit being configured to set a first permission of the user account in the server according to the permission setting request received by the receiving unit;

[0019] A sending unit, the sending unit is used to send the permission allocation result set by the setting unit to at least one subordinate terminal, and the first permission is recorded in the permission allocation result.

[0020] Optionally, the first permission includes:

[0021] Only temporary sessions are allowed between user accounts in the server, but no friends can be added to each other;

[0022] or,

[0023] Only allow user accounts in the server to add each other as friends but not initiate conversations;

[0024] or,

[0025] User accounts in the server are not allowed to add each other as friends or initiate temporary sessions.

[0026] Optionally, the device further includes: a second receiving unit, the second receiving unit being configured to receive a granularity request sent by a terminal, the granularity request including:

[0027] a first level of granularity, the first level of granularity comprising enforcing the first permission on all user accounts in the server;

[0028] or,

[0029] A second level of granularity, the second level of granularity includes executing the first permission on a specified user account.

[0030] Optionally, the second granularity level includes:

[0031] A first sub-granularity level, the first sub-granularity level comprising setting the first permission between a user account in the first group chat and a user account not in the first group chat;

[0032] or,

[0033] A second sub-granularity level, the second sub-granularity level includes setting the first permission between user accounts in the first group chat.

[0034] or,

[0035] The third sub-granularity level includes setting the first permission between a first user account and other user accounts, and the first user is a designated user account.

[0036] Optionally, when the granularity request includes multiple granularity levels, the priority of the second granularity level is greater than the priority of the first granularity level, and the priority of the third sub-granularity level is greater than the priority of the second sub-granularity level which is greater than the priority of the first sub-granularity level.

[0037] Optionally, the first terminal is a terminal with administrator privileges.

[0038] A user rights management device, comprising:

[0039] A display unit, the display unit is used to display a group conversation interface including interactive controls;

[0040] a first response unit, the first response unit being configured to respond to an interactive operation on an interactive control in the group conversation interface displayed by the display unit, and to display an information interface including a group member list;

[0041] a second response unit, the second response unit being used to respond to a selection operation of at least one group member icon in the group member list, and displaying a group member information management interface corresponding to the group member icon, wherein when the group member identifier corresponding to the group member icon is set to a first permission, a permission setting request is generated, and the first permission includes: prohibiting at least one of private chatting or prohibiting adding friends;

[0042] A sending unit, wherein the sending unit is used to send the permission setting request generated by the second response unit to a server.

[0043] A computer device, comprising: an interaction device, an input / output (I / O) interface, a processor and a memory, wherein program instructions are stored in the memory;

[0044] The interaction device is used to obtain an operation instruction input by a user;

[0045] The processor is used to execute program instructions stored in the memory to perform the above method.

[0046] A computer-readable storage medium includes instructions. When the instructions are executed on a computer device, the computer device executes the above method.

[0047] The user rights management method provided by the present application includes: a server receives a rights setting request sent by a first terminal, the first terminal is one of the terminals under the server, and the rights setting request includes the rights of the user account in the server; the server sets the rights of the user account in the server according to the rights setting request; the server sends a rights allocation result to at least one terminal under the server, and the rights allocation result records the rights of the user account in the server. In this embodiment, the server implements the rights management of the user account by obtaining the rights setting request edited by the terminal, improves the group management capability, and expands the application efficiency in enterprise management. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0049] Figure 1 This is the architecture diagram of the enterprise-level mobile office platform;

[0050] Figure 2 A flowchart of a user rights management method provided in an embodiment of the present application;

[0051] Figure 3 A schematic diagram of an embodiment of a user rights management method provided in an embodiment of the present application;

[0052] Figure 4 A schematic diagram of another embodiment of the user rights management method provided in the embodiment of the present application;

[0053] Figure 5 A schematic diagram of another embodiment of the user rights management method provided in the embodiment of the present application;

[0054] Figure 6 A schematic diagram of another embodiment of the user rights management method provided in the embodiment of the present application;

[0055] Figure 7 A schematic diagram of another embodiment of the user rights management method provided in the embodiment of the present application;

[0056] Figure 8 A schematic diagram of another embodiment of the user rights management method provided in the embodiment of the present application;

[0057] Fig. 9 A schematic diagram of another embodiment of the user rights management method provided in the embodiment of the present application;

[0058] Fig.10 A schematic diagram of the user rights management method provided in the embodiment of the present application displayed in an administrator terminal;

[0059] Fig.11 Another schematic diagram of the user rights management method provided in the embodiment of the present application displayed in the administrator terminal;

[0060] Fig.12 A schematic diagram of the user rights management method provided in the embodiment of the present application displayed in a common user terminal;

[0061] Fig.13 Another schematic diagram of the user rights management method provided in the embodiment of the present application displayed in a common user terminal;

[0062] Fig.14 Another schematic diagram of the user rights management method provided in the embodiment of the present application displayed in a common user terminal;

[0063] Fig.15 A schematic diagram of a computer device provided in an embodiment of the present application;

[0064] Fig.16 A schematic diagram of a user rights management device provided in an embodiment of the present application;

[0065] Fig.17 A schematic diagram of another user rights management device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0066] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0067] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0068] With the development of instant messaging technology, some enterprise-level mobile office platforms have been born, such as enterprise group chat. In addition to providing office communication, announcements and attendance within the enterprise, user accounts within the enterprise group chat can also initiate chats or add friends with user accounts outside the enterprise group chat.

[0069] Due to the need for internal company information security, the administrator of the enterprise group chat hopes to be able to manage the behavior of internal user accounts in the enterprise group chat to maintain the company's information security. For example, in the scenario of the company's external services, in order to prevent employees from taking away the company's customers, the company requires that in the company's external service group chat, group members cannot privately add relationships or have private chats.

[0070] For example, Figure 1As shown, user A is an employee of Company B, and his job title is a salesperson responsible for connecting with Party A's customer C. Therefore, user A is a member of Company B's enterprise group chat. User A and customer C connect to the enterprise group chat on the server side through their respective terminal devices, so that user A and customer C can communicate through the enterprise group chat. In order to prevent user A from taking customer C of Company B away after leaving, the administrator of Company B does not want user A and customer C to add friends privately, or does not want user A and customer C to have private chat activities outside the monitoring of the administrator of Company B. Therefore, as the administrator of Company B's enterprise group chat, a tool that can manage user account permission behavior is needed, so that the enterprise group chat administrator of Company B can connect to the server side through the terminal device to realize the permission management of user accounts and improve the group management capabilities.

[0071] Therefore, in order to solve the above problems, the embodiment of the present application provides a user authority management method. For ease of understanding, the method provided by the embodiment of the present application is described in detail below in conjunction with the accompanying drawings.

[0072] See also Figure 2 ,like Figure 2 As shown, the user rights management method provided in the embodiment of the present application includes the following steps.

[0073] 201. A server receives a permission setting request sent by a first terminal.

[0074] In this embodiment, the first terminal is one of the terminals under the server. For example, the first terminal is the terminal where the administrator of the enterprise group chat or the user with management authority is located. The terminal runs on a terminal device, such as a PC (personal computer), a smart phone or a tablet computer. The permission setting request includes the first permission of the user account in the server, and the first permission is used to limit the behavior authority of the user account in the server.

[0075] In the specific working process, the user in the first terminal allocates permissions to each user account in the server, manages the behavior of the user account in the server, generates the permission setting request based on the result of the permission allocation, and sends the permission setting request to the server.

[0076] 202. The server sets a first permission for a user account in the server according to the permission setting request.

[0077] In this embodiment, the permission setting request includes the first permission assigned to the user account by the administrator, and the server executes the permission setting request and assigns the first permission to the user account in the server at the server end.

[0078] 203. The server sends the authority allocation result to at least one terminal under the server.

[0079] In this embodiment, after the server completes the authority allocation to the user account, it is necessary to make each terminal aware of its own authority status. Therefore, the server sends the authority allocation result to the terminal under the server, wherein the authority allocation result records the first authority, so that the user account in the server knows its own authority status.

[0080] In the above working process, the server receives a permission setting request sent by the first terminal, the first terminal is one of the terminals under the server, and the permission setting request includes the permissions of the user account in the server; the server sets the permissions of the user account in the server according to the permission setting request; the server sends a permission allocation result to at least one terminal under the server, and the permission allocation result records the permissions of the user account in the server. In this embodiment, the server implements permission management of the user account by obtaining the permission setting request edited by the terminal, improves the group management capability, and broadens the application efficiency of the group in enterprise or strong management.

[0081] It should be noted that in the above working process, the first permission recorded can include multiple implementation methods. As an example, it can be divided into three situations: 1. Users can only initiate temporary conversations; 2. Users can only add friends; 3. Users can only chat publicly. The following are explained respectively.

[0082] 1. Users can only initiate temporary sessions.

[0083] See also Figure 3 ,like Figure 3 As shown, both user A and user B are user accounts in the server. In the first implementation of the first permission, user A and user B are only allowed to initiate temporary sessions, but cannot add friends to each other. In this way, the permissions of user A and user B are managed. For example, user A is a salesperson of Party B Company, and user B is a business contact person of Party A Company. In order to prevent its employee user A from taking user B away due to resignation and other reasons, thereby causing Party B to lose customer resources, Party B restricts the permissions of user A and user B, and only allows user A and user B to initiate temporary sessions but cannot add friends, so that Company B can restrict the behavior of user A. Since the current user A is an employee of Party B Company, due to business needs, the first group chat is established. User A and user B are both members of the first group chat. During the work process, user A and user B can initiate private chats through the temporary session of the first group chat to conduct work matters. If user A resigns, the administrator of the first group chat kicks user A out of the group chat, which can cut off the connection between user A and user B, thereby protecting the commercial privacy of Party B Company.

[0084] 2. Users can only add friends.

[0085] See also Figure 4 ,like Figure 4 As shown, both user A and user B are user accounts in the server. In the second implementation of the first permission, user A and user B are only allowed to add each other as friends but cannot initiate a conversation. Since the permission for user A and user B to communicate privately is restricted, user A and user B can only communicate in a group chat, and the content of the group chat is visible to all group members, so that the group chat administrator can monitor the communication between user A and user B. For example, user A is a salesperson of Party B Company, and user B is a business contact person of Party A Company. Due to business needs, a first group chat is established. User A and user B are both members of the first group chat. During the work process, user A and user B can only have a public chat in the first group chat but not a private chat, so that the administrator of the first group chat can monitor the content of the conversation between user A and user B, so that the commercial privacy of Party B Company is protected.

[0086] 3. Users can only chat publicly.

[0087] See also Figure 5 ,like Figure 5 As shown, both user A and user B are user accounts in the server. In the third implementation of the first permission, user A and user B are not allowed to add each other as friends or initiate temporary conversations, so that user A and user B can only communicate in group chats, and the content of group chats is visible to all group members, so that the group chat administrator can monitor the communication between user A and user B. For example, user A is a salesperson of Party B Company, and user B is a business contact person of Party A Company. Due to business needs, a first group chat is established. User A and user B are both members of the first group chat. During the work process, user A and user B can only have public chats in the first group chat but not private chats, so that the administrator of the first group chat can monitor the content of the conversation between user A and user B. Furthermore, user A and user B are restricted from adding each other as friends, so that the commercial privacy of Party B Company is protected.

[0088] It should be noted that the above three working processes are only examples. In the actual working process, the group chat administrator can set more different permission settings according to actual needs, and the embodiments of the present application do not limit this.

[0089] It should be further explained that the above-mentioned first permission can be refined into different granularities in the server, so as to be executed at different levels. In the actual execution process, the terminal where the administrator is located edits the granularity request and sends the granularity request to the server for execution by the server. For example, the first permission is uniformly executed on all user accounts in the server, or the first permission is executed on a specified user account in the first server. The former is a higher-level first granularity level, and the latter is a more refined second granularity level. For ease of understanding, these two situations are specifically explained below in conjunction with the accompanying drawings.

[0090] 1. The first granularity level.

[0091] At the first granularity level, the first permission is uniformly executed on all user accounts in the server. For the specific implementation of the first granularity level, please refer to the attached Figure 6 ,like Figure 6 As shown, App A is an enterprise-level mobile office platform, Company B is a user of App A, and Company B has set up multiple group chats in App A, namely the first group chat, the second group chat...the Nth group chat. When the administrator of Company B chooses to execute the permission setting request at the first granularity level, the permissions of all user accounts in the first group chat, the second group chat...the Nth group chat are assigned the first permission. For the specific implementation method of the first permission, please refer to the above records and will not be repeated here.

[0092] In this embodiment, the first granularity level is the highest granularity level. When the administrator sets the granularity level to the first granularity level, all users in the group chat in the app will execute the first permission set by the administrator, thereby achieving unified management.

[0093] 2. The second granularity level.

[0094] At the second granularity level, the first permission is only executed on the specified user account. The specific implementation methods can be divided into three types: 1. The first sub-granularity level, the user account between the specified group chat is executed with the first permission; 2. The second sub-granularity level, the user account within the specified group chat is executed with the first permission; 3. The third sub-granularity level, the specified specific user account is executed with the first permission. For ease of understanding, they are explained below respectively.

[0095] 1. The first sub-granularity level specifies the first permission for user accounts between group chats.

[0096] In a first implementation of the second granularity level, a first permission is set between a user account in the first group chat and a user account not in the first group chat, for example, Figure 7As shown, Company B created two group chats, the first group chat and the second group chat, on the enterprise-level mobile office platform App A. At this time, the server where App A is located has two group chats, the first group chat and the second group chat. Among them, the first group chat is an internal employee group of Company B, which is used for internal enterprise management and work communication of Company B; the second group chat is an external business communication group of Company B, which is used for business dealings between Company B and its customers; among them, user A is a salesperson of Company B, who is a member of both the first group chat and the second group chat. User B is a customer of Company B, not an employee of Company B, and is therefore only a member of the second group chat. In this embodiment, according to the setting of the granularity level, user A is a user account of the first group chat, and user B is a user account other than the first group chat. Therefore, the first permission needs to be executed between user A and user B. For the specific implementation method of the first permission, please refer to the above records, which will not be repeated here.

[0097] In the above embodiment, the administrator manages the permissions of users in group chats, so as to uniformly set the behavior permissions of the company's group chat employees and outsiders, thereby preventing the company's employees and outsiders from adding friends or privately chatting without permission.

[0098] 2. The second sub-granularity level specifies the user account within the group chat to execute the first permission.

[0099] In a second implementation at the second granularity level, the first permission is executed on the user account within the specified group chat, for example, Figure 8 As shown, Company B has created a first group chat on App A, an enterprise-level mobile office platform, for business dealings between Company B and its customers, wherein group members in the first group chat include salesperson A and customer B of Company B. In this embodiment, according to the setting of the granularity level, the first permission setting is executed between user accounts in the first group chat, so that both salesperson A and customer B are restricted by the first permission. For the specific implementation method of the first permission, please refer to the above records and will not be repeated here.

[0100] In this embodiment, among the multiple group chats created by Company B on App A, privacy protection may be required for only some of the group chats. For example, only the group chat between the company and external customers needs to restrict the behavior between members, while the internal work group of the company does not need to be restricted. Therefore, in the second implementation method of the second granularity level, the administrator executes the first permission on the specified group chat, thereby refining the allocation of permissions and making management more refined.

[0101] 3. At the third sub-granularity level, a specific user account is designated to execute the first permission.

[0102] In a third implementation of the second granularity level, the first permission is executed for a specific user account, for example, Fig. 9As shown, Company B, as a user of App A, an enterprise-level mobile office platform, has created multiple group chats on App A, including the first group chat, the second group chat to the Nth group chat, wherein user B is an important customer of Company B. The administrator of Company B hopes to focus on protecting User B to prevent any employee of the company from chatting privately with him or adding friends to him. At this time, the administrator of Company B needs to execute the third sub-granularity level for User B. Regardless of which group chat User B joins in App A, he is restricted by the first permission, for example, he cannot chat privately with other user accounts, or cannot add friends with other users, thereby realizing restrictions on specific user accounts.

[0103] In this embodiment, the user's permission management is further refined through the third sub-granularity level, and is directly restricted to specific user accounts, thereby making the management of user permissions in group chat more refined.

[0104] It should be noted that, in addition to the above-mentioned first granularity level and second granularity level, the administrator can also set more granularity levels according to actual needs to meet his or her own needs for user authority management, which is not limited in the embodiments of the present application.

[0105] It should be further explained that if the granularity request contains multiple granularity levels, different granularity level permission requirements can be executed according to different priorities. The specific priorities are arranged as follows:

[0106] The second granularity level > the first granularity level.

[0107] In this embodiment, the first granularity level is the level for all group chats in the app, and the second granularity level is the group chat for a specific user account. Therefore, the second granularity level is for more detailed and special situations. Therefore, when the first granularity level and the second granularity level are equally applicable to a user A, the user A executes the first permission set by the second granularity level. For example, the first granularity level is: all users can only initiate temporary sessions but cannot add friends; the second granularity level is: users in the first group chat can neither initiate temporary sessions nor add friends. User A is a member of the first group chat. At this time, user A executes the more detailed second granularity level command, and can neither initiate temporary sessions with other users nor add friends with other users.

[0108] Furthermore, in each sub-granularity level of the second granularity level, there is also a distinction in priority, and the specific priorities are arranged as follows according to the size of the priority:

[0109] The third sub-granularity level>the second sub-granularity level>the first sub-granularity level.

[0110] In this embodiment, the first sub-granularity level is the granularity level between group chats, the second sub-granularity level is the granularity level within a single group chat, and the third sub-granularity level is the granularity level for specific users. Therefore, from the first sub-granularity level to the third sub-granularity level, the granularity gradually becomes finer. Therefore, the third sub-granularity level has the finest granularity and the most specific permission management. Therefore, the third sub-granularity level has the highest priority.

[0111] The above introduces the user authority management method provided in the embodiment of the present application from a technical perspective. For ease of understanding, the working process of the user authority management method provided in the embodiment of the present application in the terminal is introduced from the perspective of the terminal.

[0112] It should be noted that, in the actual working process, the terminals of this application include administrator terminals and ordinary user terminals, and the two terminals have different working modes, which are described separately below.

[0113] 1. Administrator terminal

[0114] The method for executing user rights management by the administrator terminal specifically includes:

[0115] The terminal displays a group conversation interface including interactive controls;

[0116] The terminal responds to the interactive operation on the interactive control in the group conversation interface and displays an information interface including a list of group members;

[0117] The terminal responds to a selection operation of at least one group member icon in the group member list by displaying a group member information management interface corresponding to the group member icon, wherein when the group member identifier corresponding to the group member icon is set to a first permission, a permission setting request is generated, and the first permission includes: prohibiting at least one of private chatting or prohibiting adding friends;

[0118] The terminal sends the permission setting request to the server.

[0119] In this embodiment, the administrator terminal configures the user rights including the following steps.

[0120] 1. Enter the configuration interface.

[0121] See also Fig.10 On the enterprise-level mobile office platform, administrators can access Fig.10 The configuration interface shown in the figure can be entered from the software setting interface, from the group chat, or directly for a user to enter the configuration interface of the user account according to different granularity levels. This embodiment takes entering the configuration page from the group chat as an example. Fig.10As shown, after entering the configuration interface, click the group member management button 1001 to enter the Fig.11 The group member management interface is shown.

[0122] 2. User permission settings.

[0123] See also Fig.11 ,like Fig.11 As shown in the figure, after entering the group member management interface, you can set the permissions of group members. Fig.11 For example, you can check whether to allow group members to add relationships with each other and whether to allow group members to chat and send messages to each other. The administrator terminal thus generates a permission setting request and automatically sends the request to the server for execution. The specific execution process can be referred to the above record and will not be repeated here.

[0124] After receiving the permission setting request sent by the administrator terminal, the server executes the first permission assigned to the user account in the permission setting request and sends the permission assignment result to each common user terminal, so that each common user terminal can display its own permission status. The working status of the common user terminal is described below.

[0125] 2. Ordinary user terminal.

[0126] 1. The permission allocation results are displayed.

[0127] See also Fig.12 When the server completes the permission allocation, the ordinary user terminal will display the result of the permission allocation. Taking the permission allocation of the second sub-granularity level as an example, Fig.12 As shown, when ordinary user A clicks on the personal profile of another ordinary user B in the same group chat, a permission reminder bar 1201 is set at the bottom of user B's personal profile to display user A's permissions to user A, for example: group members cannot add relationships to each other, and group members cannot send messages to each other, so that user A can know his or her permissions in the current group chat.

[0128] Optionally, see Fig.13 If the first permission is that users can add each other as friends but cannot chat privately, the permission reminder bar of user B only displays an add as contact button 1301, so that user A can initiate the operation of adding a friend to user B on the current page.

[0129] Optionally, see Fig.14 If the administrator has not restricted the user rights in the current group chat, the permission reminder bar of user B will display the add friend button 1401 and the initiate temporary session button 1402, so that user A can add user B as a friend and have a private chat.

[0130] The above is an introduction to the scheme provided by the embodiment of the present application. It is understandable that, in order to realize the above functions, the computer device includes a hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the modules and algorithm steps of each example described in the embodiment disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel 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 the present application.

[0131] On the basis of the above embodiments, the embodiment of the present application further provides a user rights management device, the device comprising a display unit and an opening unit:

[0132] The display unit is used to display a group conversation interface of a group, wherein the group includes a plurality of group members, and the plurality of group members include at least the first group member and the second group member;

[0133] The opening unit is used to open an interaction preparation page with the second group member through the first group member in the group conversation interface, wherein the interaction preparation page is used to display an interaction entrance for the first group member and the second group member to interact individually;

[0134] The display unit is further configured to display, in the interaction preparation page, a prompt indicating that the first group member does not have the permission to interact individually with the second group member when the permission for interaction between group members in the group is disabled, wherein the permission for interaction between group members is used to identify the permission of the group member to interact individually with group members through the group;

[0135] The display unit is further used to display an interaction entry corresponding to a first interaction permission among the interaction permissions between the group members in the interaction preparation page when the first interaction permission is enabled, and the first interaction permission is used for the first group member to establish a separate interaction corresponding to the first interaction permission with the second group member.

[0136] In a possible implementation, the first interaction permission is a permission to add a friend, and the display unit is further configured to:

[0137] In response to a triggering operation on the interaction entry corresponding to the first interaction permission, a friend adding page for adding the second group member is displayed.

[0138] In a possible implementation, the first interaction permission is a private chat session permission, and the display unit is further configured to:

[0139] In response to a triggering operation on an interaction entry corresponding to the first interaction permission, a private chat session page between the first group member and the second group member is displayed.

[0140] In a possible implementation manner, the display unit is further used for:

[0141] When the first interaction permission and the second interaction permission among the interaction permissions between the group members are enabled, interaction entrances corresponding to the first interaction permission and the second interaction permission are displayed on the interaction preparation page.

[0142] In a possible implementation, the interaction preparation page is an account page of the second group member, and the opening unit is further used to:

[0143] In response to a triggering operation on the account of the second group member by the first group member in the group conversation interface, an account page of the second group member is opened.

[0144] The embodiment of the present application also provides a user authority management method, wherein the device includes a display unit and a authority unit:

[0145] The display unit is used to display a permission configuration page for a group including multiple group members, the permission configuration page including at least one interaction permission control, the at least one interaction permission control corresponding to the interaction permission provided to the group members in the group, the interaction permission being the permission for the group members to interact individually with each other through the group;

[0146] The permission unit is configured to allocate a first interaction permission corresponding to the first permission control to a group member in the group in response to the first permission control in the at least one interaction permission control being enabled;

[0147] The permission unit is further configured to disable the interaction permission for group members in the group in response to the at least one interaction permission control being disabled.

[0148] In a possible implementation manner, the display unit is further used for:

[0149] In response to triggering a corresponding group configuration control through the group conversation interface of the group, displaying a permission configuration page for a group including a plurality of group members; or,

[0150] In response to triggering a corresponding group configuration control by the social software that creates the group, displaying a permission configuration page for the group including a plurality of group members; or,

[0151] In response to triggering a corresponding group configuration control through an account page of any group member in the group, a permission configuration page for the group including the plurality of group members is displayed.

[0152] Describing from the perspective of hardware structure, the above method can be implemented by one physical device, can be implemented by multiple physical devices together, or can be a logical function module within a physical device, and the embodiments of the present application do not make specific limitations on this.

[0153] For example, the above methods can be Fig.15 This is achieved by using the computer equipment in the system. Fig.15 The hardware structure diagram of the computer device provided in the embodiment of the present application includes at least one processor 1501, a communication line 1502, a memory 1503 and at least one communication interface 1504.

[0154] Processor 1501 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (server IC), or one or more integrated circuits used to control the execution of the program of the present application.

[0155] The communication link 1502 may include a pathway to transmit information between the above-mentioned components.

[0156] The communication interface 1504 uses any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.

[0157] The memory 1503 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may exist independently and be connected to the processor via the communication line 1502. The memory may also be integrated with the processor.

[0158] The memory 1503 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 1501. The processor 1501 is used to execute the computer-executable instructions stored in the memory 1503, thereby implementing the method provided in the above embodiment of the present application.

[0159] Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.

[0160] In a specific implementation, as an embodiment, the processor 1501 may include one or more CPUs, such as Fig.15 CPU0 and CPU1 in.

[0161] In a specific implementation, as an embodiment, a computer device may include multiple processors, such as Fig.15 1501 and processor 1507 in the embodiment of the present invention. Each of these processors may be a single-CPU processor or a multi-CPU processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0162] In a specific implementation, as an embodiment, the computer device may further include an output device 1505 and an input device 1506. The output device 1505 communicates with the processor 1501 and may display information in a variety of ways. For example, the output device 1505 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 1506 communicates with the processor 1501 and may receive user input in a variety of ways. For example, the input device 1506 may be a mouse, a keyboard, a touch screen device, or a sensor device.

[0163] The computer device may be a general-purpose device or a dedicated device. In a specific implementation, the computer device may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device or a computer with Fig.15 The embodiments of the present application do not limit the type of computer device.

[0164] The embodiment of the present application can divide the storage device into functional units according to the above method example. For example, each functional unit can be divided according to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units. It should be noted that the division of units in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0165] For example, when each functional unit is divided in an integrated manner, Fig.16 A schematic diagram of a user rights management device is shown.

[0166] like Fig.16 As shown, the user rights management device provided in the embodiment of the present application includes:

[0167] A first receiving unit 1601, the receiving unit is used to receive a permission setting request sent by a first terminal, the first terminal is a terminal in the server subordinate terminal, the permission setting request includes a first permission of the user account in the server, and the first permission is used to limit the behavior permission of the user account in the server;

[0168] A setting unit 1602, the setting unit 1602 is used to set a first permission of the user account in the server according to the permission setting request received by the first receiving unit 1601;

[0169] The sending unit 1603 is configured to send the permission allocation result set by the setting unit 1602 to at least one subordinate terminal, wherein the first permission is recorded in the permission allocation result.

[0170] Optionally, the first permission includes:

[0171] Only temporary sessions are allowed between user accounts in the server, but no friends can be added to each other;

[0172] or,

[0173] Only allow user accounts in the server to add each other as friends but not initiate conversations;

[0174] or,

[0175] User accounts in the server are not allowed to add each other as friends or initiate temporary sessions.

[0176] Optionally, the apparatus further includes: a second receiving unit 1604, wherein the second receiving unit 1604 is configured to receive a granularity request sent by a terminal, wherein the granularity request includes:

[0177] a first level of granularity, the first level of granularity comprising enforcing the first permission on all user accounts in the server;

[0178] or,

[0179] A second level of granularity, the second level of granularity includes executing the first permission on a specified user account.

[0180] Optionally, the second granularity level includes:

[0181] A first sub-granularity level, the first sub-granularity level comprising setting the first permission between a user account in the first group chat and a user account not in the first group chat;

[0182] or,

[0183] A second sub-granularity level, the second sub-granularity level includes setting the first permission between user accounts in the first group chat.

[0184] Optionally, the second granularity level also includes a third sub-granularity level, and the third sub-granularity level includes setting the first permission between the first user account and other user accounts, and the first user is a designated user account.

[0185] Optionally, when the granularity request includes multiple granularity levels, the priority of the second granularity level is greater than the priority of the first granularity level, and the priority of the third sub-granularity level is greater than the priority of the second sub-granularity level which is greater than the priority of the first sub-granularity level.

[0186] Optionally, the first terminal is a terminal with administrator privileges.

[0187] Fig.17 A schematic diagram of another user rights management device provided in an embodiment of the present application is shown.

[0188] like Fig.17 As shown, the user rights management device provided in the embodiment of the present application includes:

[0189] A first response unit 1701, the first response unit 1701 is used to respond to the interactive operation of the interactive control in the group conversation interface displayed by the display unit, and display an information interface including a group member list;

[0190] The second response unit 1702 is used to respond to the selection operation of at least one group member icon in the group member list, and display the group member information management interface corresponding to the group member icon, wherein when the group member identifier corresponding to the group member icon is set to the first permission, a permission setting request is generated, and the first permission includes: prohibiting private chat or prohibiting adding friends;

[0191] The sending unit 1703 is used to send the permission setting request generated by the second response unit 1702 to the server.

[0192] Furthermore, an embodiment of the present invention also provides a computer storage medium, including instructions, which, when executed on a computer device, enable the computer device to execute the above method.

[0193] For a detailed description of the program stored in the computer storage medium provided in the embodiments of the present application, reference can be made to the above embodiments and will not be repeated here.

[0194] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0195] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0196] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0197] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the core concept or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user rights management method, characterized in that: The method comprises: Displaying a group conversation interface of a group, wherein the group includes a plurality of group members, and the plurality of group members include at least the first group member and the second group member; In the group conversation interface, the first group member opens an interaction preparation page with the second group member, the interaction preparation page being used to display an interaction entrance for the first group member and the second group member to interact individually; When the interaction permission between group members in the group is disabled, a prompt indicating that the first group member does not have the permission to interact individually with the second group member is displayed on the interaction preparation page, and the interaction permission between group members is used to identify the permission of the group member to interact individually with group members through the group; When a first interaction permission among the interaction permissions between the group members is enabled, an interaction entry corresponding to the first interaction permission is displayed on the interaction preparation page, and the first interaction permission is used for the first group member to establish a separate interaction corresponding to the first interaction permission with the second group member.

2. The method according to claim 1, characterized in that The first interaction permission is a permission to add friends. After an interaction entry corresponding to the first interaction permission is displayed on the interaction preparation page, the method further includes: In response to a triggering operation on the interaction entry corresponding to the first interaction permission, a friend adding page for adding the second group member is displayed.

3. The method according to claim 1, characterized in that The first interaction permission is a private chat session permission. After the interaction entry corresponding to the first interaction permission is displayed on the interaction preparation page, the method further includes: In response to a triggering operation on an interaction entry corresponding to the first interaction permission, a private chat session page between the first group member and the second group member is displayed.

4. The method according to claim 1, characterized in that: The method further comprises: When the first interaction permission and the second interaction permission among the interaction permissions between the group members are enabled, interaction entrances corresponding to the first interaction permission and the second interaction permission are displayed on the interaction preparation page.

5. The method according to any one of claims 1 to 4, characterized in that: The interaction preparation page is the account page of the second group member, and in the group conversation interface, opening the interaction preparation page of the second group member by the first group member includes: In response to a triggering operation on the account of the second group member by the first group member in the group conversation interface, an account page of the second group member is opened.

6. A user rights management method, characterized in that: The method comprises: Displaying a permission configuration page for a group including a plurality of group members, the permission configuration page including at least one interaction permission control, the at least one interaction permission control corresponding to an interaction permission provided to a group member in the group, the interaction permission being a permission for the group member to interact with other group members individually through the group; In response to a first permission control in the at least one interaction permission control being enabled, allocating a first interaction permission corresponding to the first permission control to a group member in the group; In response to the at least one interaction permission control being disabled, disabling the interaction permission for group members in the group.

7. The method according to claim 6, characterized in that The displaying of a permission configuration page for a group including a plurality of group members includes: In response to triggering a corresponding group configuration control through the group conversation interface of the group, displaying a permission configuration page for a group including a plurality of group members; or, In response to triggering a corresponding group configuration control by the social software that creates the group, displaying a permission configuration page for the group including a plurality of group members; or, In response to triggering a corresponding group configuration control through an account page of any group member in the group, a permission configuration page for the group including the plurality of group members is displayed.

8. A user rights management device, characterized in that: The device comprises a display unit and an opening unit: The display unit is used to display a group conversation interface of a group, wherein the group includes a plurality of group members, and the plurality of group members include at least the first group member and the second group member; The opening unit is used to open an interaction preparation page with the second group member through the first group member in the group conversation interface, wherein the interaction preparation page is used to display an interaction entrance for the first group member and the second group member to interact individually; The display unit is further configured to display, in the interaction preparation page, a prompt indicating that the first group member does not have the permission to interact individually with the second group member when the permission for interaction between group members in the group is disabled, wherein the permission for interaction between group members is used to identify the permission of the group member to interact individually with group members through the group; The display unit is further used to display an interaction entry corresponding to a first interaction permission among the interaction permissions between the group members in the interaction preparation page when the first interaction permission is enabled, and the first interaction permission is used for the first group member to establish a separate interaction corresponding to the first interaction permission with the second group member.

9. A user rights management device, characterized in that: The device comprises a display unit and an authority unit: The display unit is used to display a permission configuration page for a group including multiple group members, the permission configuration page including at least one interaction permission control, the at least one interaction permission control corresponding to the interaction permission provided to the group members in the group, the interaction permission being the permission for the group members to interact individually with each other through the group; The permission unit is configured to allocate a first interaction permission corresponding to the first permission control to a group member in the group in response to the first permission control in the at least one interaction permission control being enabled; The permission unit is further configured to disable the interaction permission for group members in the group in response to the at least one interaction permission control being disabled.

10. A computer device, characterized in that: The computer device comprises a processor and a memory: The memory is used to store computer programs; The processor is configured to execute the method of any one of claims 1 to 5 or claims 6 to 7 according to the computer program.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store a computer program, and when the computer program is executed by a computer device, the method according to any one of claims 1 to 5 or claims 6 to 7 is implemented.

12. A computer program product comprising a computer program, which, when executed on a computer device, causes the computer device to execute the method of any one of claims 1 to 5 or claims 6 to 7.

Images