Permission configuration method and apparatus, and electronic device

Abstract

Provided in the embodiments of the present disclosure are a permission configuration method and apparatus, and an electronic device. The method comprises: in response to receiving a permission configuration request for performing permission configuration on a role, presenting a permission configuration interface, wherein the permission configuration request is used for setting, for the role, a permission to a preset application; displaying permission configuration recommendation information in the permission configuration interface, wherein the permission configuration recommendation information is used for recommending a permission to be configured; and receiving a permission, which is configured according to the permission configuration recommendation information, and generating function permissions associated with the role. The efficiency and accuracy of permission configuration are improved.

Description

Permission configuration method, device and electronic device

[0001] This application claims priority to the Chinese invention patent application entitled “Permission configuration method, device and electronic device” and application number 2023109066751, filed on July 21, 2023. The entire contents of that application are incorporated by reference into this application. Technical Field

[0002] The present disclosure relates to the field of computer technology, and more particularly to a permission configuration method, device, and electronic device. Background Art

[0003] When developers develop applications on a low-code platform, they can set different page elements on the application page, such as text, images, controls, tables, and other page elements.

[0004] In order to display different page effects to different users and to consider the security of page content, it is necessary to perform permission control on the page elements in the page. Accordingly, in order to implement permission control on the page elements of the page, the developer needs to configure the permissions of the page elements.

[0005] Summary of the Invention

[0006] Embodiments of the present disclosure provide a permission configuration method, apparatus, and electronic device.

[0007] In a first aspect, an embodiment of the present disclosure provides a page processing method, the method comprising: in response to receiving a permission configuration request for configuring permissions for a role, displaying a permission configuration interface; wherein the permission configuration request is used to set permissions for preset applications for the role; displaying permission configuration recommendation information in the permission configuration interface, the permission configuration recommendation information being used to recommend permissions to be configured; receiving permissions configured according to the permission configuration recommendation information, and generating functional permissions associated with the role.

[0008] In a second aspect, an embodiment of the present disclosure provides a page processing device, which includes: a first display unit, for displaying a permission configuration interface in response to receiving a permission configuration request for configuring permissions for a role; wherein the permission configuration request is used to set permissions for preset applications for the role; a second display unit, for displaying permission configuration recommendation information in the permission configuration interface, the permission configuration recommendation information being used to recommend permissions to be configured; and a receiving unit, for receiving permissions configured according to the permission configuration recommendation information, and generating functional permissions associated with the role.

[0009] In a third aspect, an embodiment of the present disclosure provides an electronic device comprising: a processor and a memory; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the first aspect above and various possible methods involved in the first aspect.

[0010] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the first aspect and various possible methods involved in the first aspect are implemented.

[0011] In a fifth aspect, an embodiment of the present disclosure provides a computer program product, including a computer program, which, when executed by a processor, implements the first aspect and various methods that may be involved in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0013] FIG1 is a schematic flow chart of a method for configuring permissions provided by the present disclosure;

[0014] Figure 2 is a schematic diagram of an application scenario;

[0015] Figure 3 is a schematic diagram of an application scenario;

[0016] Figure 4 is a schematic diagram of an application scenario;

[0017] Figure 5 is a schematic diagram of an application scenario;

[0018] Figure 6 is a schematic diagram of an application scenario;

[0019] Figure 7 is a schematic diagram of an application scenario;

[0020] Figure 8 is a schematic diagram of an application scenario;

[0021] FIG9 is a second schematic flow chart of the permission configuration method provided by the present disclosure;

[0022] FIG10 is a structural block diagram of the permission configuration device provided by the present disclosure;

[0023] FIG11 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0024] To make the objectives, technical solutions, and advantages of the embodiments of the present disclosure more clear, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present disclosure without making any creative efforts shall fall within the scope of protection of the present disclosure.

[0025] Developers can develop applications in various ways. For example, they can develop applications using low-code methods. These applications can include multiple pages. Each page can include multiple page elements.

[0026] To ensure data security in these applications, it's necessary to set permissions for page elements. For example, if a page element (such as a control) is associated with a procedural event, the procedural event will be triggered when the application user performs the corresponding operation on the page element. If permissions for this page element are not controlled based on roles, the procedural event may be frequently and improperly accessed, resulting in wasted resources. For another example, if a page element is associated with a database, permission control for this page element is also required to prevent information leakage in the database.

[0027] Furthermore, with the increasing demand for fine-grained permission configuration, such as the requirement for field-level permission control for database objects, the volume of permission items requiring configuration is increasing. Configuring permissions for a large volume of permission items can lead to omissions. In some application scenarios, if a role is not assigned permissions for a page element requiring permissions, the role typically lacks permission to access or operate that page element. In these scenarios, users may not be able to display the application page properly or operate the page elements normally.

[0028] In order to avoid the problem of missing page element permission configuration, the solution disclosed in the present invention displays permission configuration recommendation information when the developer needs to configure permissions for the role of a preset application, and recommends permissions to be configured to the developer. This can avoid the problem of missing application permission configuration to a certain extent, and can also improve the efficiency of configuring permissions.

[0029] Please refer to Figure 1, which shows a schematic flow chart of the permission configuration method provided by the present disclosure. As shown in Figure 1, the method includes:

[0030] S101: In response to receiving a permission configuration request for configuring permissions for a role, displaying a permission configuration interface; wherein the permission configuration request is used to set permissions of a preset application for the above role.

[0031] The execution subject in this embodiment may be a terminal device or a server. The terminal device here may be a terminal device used by an application developer (hereinafter referred to as the first user).

[0032] The preset applications here can be applications under development, applications that have been developed, applications that have been launched, etc.

[0033] In some embodiments, the permission configuration request indicates configuring operation permissions of a preset process and / or a preset data model associated with the page element.

[0034] The first user (application developer) can use the above-mentioned execution entity to set up multiple pages for the application on the low-code platform and set page elements for the pages. In the low-code platform, application development is carried out through a visual method. Developers can use a graphical user interface to create applications by dragging and dropping components. In the low-code platform, page elements can be implemented by components and models provided by the low-code platform. The components and models in the low-code platform can be pre-associated with process and / or data models.

[0035] As an illustrative example, the component corresponding to page element 1 can be associated with an event, such as a touch event. The touch event can be associated with a process, such as a problem handling process. The problem handling process is pre-configured to require operation permissions. In addition, the component corresponding to page element 2 can be associated with a data model, for example. The data model here can be understood as a pre-stored data set including multiple fields. The data set is pre-configured to require operation permissions.

[0036] Since page elements in the low-code platform are pre-associated with preset processes, different permissions can be set for different roles. For example, if the permissions of the above preset process are configured for role 1, users with the identity of role 1 will have the permission to operate the page element. These users can then operate the page element, thereby initiating the background execution of the process corresponding to the page element. The background can return the process execution result to the client, and the user with the identity of role 1 can browse the above execution result. For example, if no permissions are configured for role 2, the user with the identity of role 2 will not have the permission to operate the page element. Therefore, configuring permissions for applications developed using the low-code platform can prevent improper access to the preset processes associated with page elements in the application and leakage of database information.

[0037] In these embodiments, by configuring the above-mentioned preset processes and / or preset operation permissions of the models associated with the above-mentioned page elements, functions corresponding to the above-mentioned preset processes and / or data models can be executed according to the user's operation on the page elements.

[0038] The role here can be a role that the developer is currently creating or a role that has already been created.

[0039] After the first user configures at least one page for the application, in order to enable users with the above roles to normally browse and operate page elements of the application pages, the permissions of the above roles need to be configured.

[0040] The role here can be any role configured by the first user for a preset application. For example, the roles configured by the first user can be a normal browser, manager, owner, and other roles. The first user can set different roles for different applications. For example, for an application running in a library, roles such as librarian for managing books and user administrator for managing book users can be configured.

[0041] The first user may initiate a permission configuration request for configuring the permission of the role. After receiving the permission configuration request, the execution subject may display a permission configuration interface.

[0042] S102: Displaying permission configuration recommendation information in the permission configuration interface, where the permission configuration recommendation information is used to recommend permissions to be configured.

[0043] After receiving the permission configuration request, the execution entity may display the permission configuration interface and display the permission configuration recommendation information in the permission configuration interface.

[0044] The permission configuration recommendation information includes the permission items recommended by the execution entity for permission configuration and the permission setting control for configuring permissions for the permission items. For example, the execution entity may determine the permission items to be configured based on the permission control information pre-set for the process and / or data model associated with the page element.

[0045] S103: Receive the permissions configured according to the permission configuration recommendation information, and generate functional permissions associated with the above role.

[0046] The first user can browse the permission configuration recommendation information to configure the permission items recommended by the permission configuration recommendation information. Configuring the permission items refers to granting the permission items to the role.

[0047] The execution subject can generate the functional permissions associated with the role based on the received permission configuration results. Schematically, the functional permissions include the permission to browse / operate pages, the permission to operate processes involved in preset applications, and the permission to browse / operate data.

[0048] The above roles have the permissions to browse, click, view, modify, and perform other operations on the page elements associated with the permission items that have been configured with permissions.

[0049] One method for configuring permissions for an application is to configure it in a permission setting list corresponding to the application. The permission setting list can include all the page elements of the application that require permission control, as well as the permission items that need to be configured for the page elements. The user configures permissions for the page elements one by one in the list. The above-mentioned element setting list is relatively large. When configuring permissions for page elements in a large permission setting list, it is inevitable that omissions in the permission configuration will occur, resulting in the user being unable to browse the page normally or being unable to operate the page elements.

[0050] In this embodiment, in response to receiving a permission configuration request for configuring permissions for a role, a permission configuration interface is displayed; wherein the permission configuration request is used to set permissions for a preset application for the aforementioned role; permission configuration recommendation information is displayed in the permission configuration interface, and the permission configuration recommendation information is used to recommend permissions to be configured; permissions configured according to the permission configuration recommendation information are received, and functional permissions associated with the aforementioned role are generated. This provides permission configuration recommendation information when performing permission configuration, and the permission configurer can configure permissions based on the permission configuration recommendation information. This can avoid omissions in permission configuration and improve the efficiency of permission configuration and the accuracy of configuration results.

[0051] In some embodiments, the above-mentioned step S101 includes: in response to receiving a page permission configuration request for configuring permissions of the target page for the above-mentioned role, displaying a page permission configuration interface; and step S102 includes: displaying the process permission configuration information and / or data model permission configuration recommendation information involved in the target page in the page permission configuration interface.

[0052] Please refer to Figures 2 and 3. Figure 2 is a schematic diagram of an application scenario; Figure 3 is a schematic diagram of an application scenario. As shown in Figure 2, the first user can open a role list, which can include information (role identifiers) of multiple roles, such as role A1, role A2, and role A3 shown in Figure 2.

[0053] The first user (developer) selects a target role "Role A1" for which permissions are to be configured in a role list for a preset application (the roles in the role list may be created by the first user).

[0054] After the first user selects the target role A1, they can initiate a permission configuration request to configure permissions for role A1. Alternatively, the first developer can create role A1 in real time and then initiate a permission configuration request to configure permissions for role A1. As shown in Figure 3, after receiving the permission configuration request, the execution entity can display the permission setting items in the interface: "Page Permissions," "Process Permissions," and "Data Model Permissions."

[0055] The first user can click on the page permission to display the page list 301. The page list 301 can display information about all pages involved in the preset application, such as page 1, page 2, and page 3 in Figure 3. In addition, the page list 301 can also display recommended configuration permission information for configuring permissions for each page. For example, the recommended configuration permission information "0 / 3" corresponding to page 1 in Figure 3, where "3" is the number of permission items recommended for configuration in page 1, and "0" is the number that has been configured. The recommended configuration permission information "0 / 6" corresponding to page 2, where "6" is the number of permission items recommended for configuration in page 2, and "0" is the number of permission items that have been configured. The recommended configuration permission information "0 / 2" corresponding to page 3, where "2" is the number of permission items recommended for configuration in page 1, and "0" is the number that has been configured.

[0056] The first user can perform a trigger operation on the preset position of page 2 in the page list 301 in Figure 3, for example, perform a trigger operation on the area around the recommended configuration permission information "0 / 6" on page 2, thereby displaying the page permission configuration interface 401 of page 2, as shown in Figure 4, which is a schematic diagram of an application scenario. As shown in Figure 4, on page 2, 6 permission items are recommended for permission configuration. As shown in the page permission configuration interface 401. The process permission configuration recommendation information includes the process name and the permission setting control 402 for configuring the permission items of the process. As shown in Figure 2, the permission items of the process include allowing triggering. The processes involved in page 2 include B1 process, B2 process, and B3 process. The permission setting control 402 corresponding to each process can be displayed in association with the process name. Specifically, the permission setting control corresponding to each process is set on one side of the process name of the process. The first user can set the permissions of a process by performing a preset operation (such as a selection operation) on the permission setting control associated with the process name of the process.

[0057] The above-mentioned permission configuration recommendation information also includes data model recommended configuration permission information, and the data model recommended configuration permission information includes the permission configuration information of data model 1, data model 2 and data model 3 involved in page 2. The names of the above-mentioned data model 1, data model 2 and data model 3 can be displayed in the page permission configuration interface 401, as well as multiple permission items pre-configured for the data models, such as the permission items "View", "Edit", "Add", "Delete" and other permission items in Figure 4. The first user can selectively configure the above-mentioned permission items of the above-mentioned data model 1, data model 2 and data model 3 recommended in page 2 in Figure 4.

[0058] In some embodiments, the method further comprises:

[0059] Display permission configuration prompt information near the permission setting control of the recommended permission item.

[0060] The permission configuration prompt information may include characters and / or graphics. Schematically, the prompt information includes a solid circle graphic.

[0061] As an illustrative example, in the page permission configuration interface, each of the recommended data models may include multiple permission items, and the execution entity may also determine the permission items recommended for permission configuration for the data model. The execution entity may display permission configuration prompt information, such as permission configuration prompt information 405 in FIG4 , near the permission setting controls for the recommended permission items to prompt the first user to configure permissions for these permission items. By displaying permission configuration prompt information near the permission setting controls for the recommended permission items, the efficiency and accuracy of permission configuration may be further improved.

[0062] In some embodiments, the display style of the permission configuration prompt information is different before and after the permissions of the corresponding permission item are configured.

[0063] Illustratively, the color and size of the permission configuration prompt information are different before and after the corresponding permission item is configured with permissions.

[0064] In these embodiments, by displaying permission configuration prompt information in different styles before and after the corresponding permission item is configured with permissions, the first user can be prompted whether these permissions have been configured, which helps prevent the omission of unconfigured permissions and also makes it easier for the first user to browse the information of configured permission items.

[0065] In some embodiments, a one-click configuration control is displayed in the permission configuration interface, and the one-click configuration control is used to perform one-click configuration of multiple permission items indicated by the permission configuration recommendation information.

[0066] As shown in FIG4 , a one-click configuration control 404 can be displayed in the page permission configuration interface. The first user can trigger the one-click configuration control 404. After receiving the trigger operation, the execution subject can perform permission configuration for the recommended permission items corresponding to data model 1, data model 2, and data model 3 in the background. This enables one-click configuration of the permission items of the recommended data models.

[0067] By setting a one-click configuration control in the permission configuration interface, you can configure multiple permission items with one click, further improving the efficiency of permission configuration.

[0068] In some embodiments, the above-mentioned step S101 includes: displaying the process permission configuration interface in response to receiving a permission configuration request for configuring permissions for a role issued through a process permission configuration channel; and step S102 includes: displaying the process permission configuration information of multiple processes involved in the recommended preset application in the process permission configuration interface.

[0069] Furthermore, at least one process among the multiple processes is associated with a data model, and the process permission configuration interface also displays permission configuration information of the data model associated with the at least one process.

[0070] The following is explained in conjunction with Figures 3, 5 and 6. Figure 5 is a schematic diagram of an application scenario. Figure 6 is a schematic diagram of an application scenario. The first user can perform a selection operation on the process permission in the permission setting item in Figure 3, thereby issuing a permission configuration request for configuring permissions for the role through the process permission configuration channel. After receiving the above permission configuration request, the above-mentioned execution subject can display the process permission configuration interface, as shown in Figure 5. The process permission configuration interface 501 can determine the target process from the processes associated with the page elements of all pages of the preset application, and display the permission configuration recommendation information for configuring permissions for these target processes. As shown in Figure 5, the B1 process, B2 process, B3 process and B4 process are recommended for permission configuration, and a permission setting control 502 is set for each process.

[0071] In addition, if the recommended process is also associated with a data model, the data model permission configuration recommendation information can be displayed in the process permission configuration interface 501, such as "Configure (0 / 3)" in the "Recommended Permissions" column corresponding to the B1 process in Figure 5. This data model permission configuration recommendation information is used by the first user to enable permissions for the data model associated with process B1. The first user can perform a trigger operation on the above-mentioned data model permission configuration recommendation information, thereby displaying the data model permission setting interface 601 for the data model associated with process B2, as shown in Figure 6. Figure 6 is a schematic diagram of an application scenario. The data model permission setting interface 601 can display a permission setting list for the data models associated with process B2, including the data model identifiers of data model 4, data model 5, and data model 6, as well as the permission items "View", "Edit", "Add", and "Delete" corresponding to each data model. Each permission item of each data model corresponds to a permission setting control 602. The first user can set permissions for the data models involved in process B2 in the above-mentioned data model permission setting interface 601.

[0072] In these embodiments, a process permission configuration channel is provided to configure process permissions for the first user, so that the first user can configure permissions from the perspective of multiple processes involved in the preset application, and an additional channel for permission setting is provided for the first user, which helps the first user to configure process permissions through different channels.

[0073] In some embodiments, the above-mentioned step S101 includes: displaying the data model permission configuration interface in response to receiving a permission configuration request for configuring permissions for a role through a data model permission configuration channel; and step S102 includes: displaying permission configuration recommendation information for multiple data models involved in a preset application in the data model permission configuration interface.

[0074] The following description is provided in conjunction with Figures 3 and 7. Figure 7 is a schematic diagram of an application scenario. A first user can select a data model permission in the permission setting item in Figure 3, thereby issuing a permission configuration request to configure permissions for a role through the data model configuration channel. After receiving the permission configuration request, the execution entity can display a data model permission configuration interface, as shown in Figure 7. Data model permission configuration interface 701 identifies target data models for which permissions are recommended from the data models associated with page elements on all pages of the preset application (including data models associated with processes) and displays permission configuration recommendations for these target data models. As shown in Figure 7, the recommended permission configurations include Data Model 1, Data Model 2, Data Model 3, Data Model 4, Data Model 5, and Data Model 6, and their permission items. The permission items corresponding to each data model include "View," "Edit," "Add," and "Delete." Each permission item in each data model corresponds to a permission setting control 702. The first user can set permissions for the data models in the data model permission setting interface 701.

[0075] In these embodiments, by providing data model permission configuration and configuring data model permissions for the first user, the first user can configure permissions from the perspective of multiple data models involved in the preset application, providing the first user with an additional channel for permission setting, which helps the first user to configure data model permissions through different channels.

[0076] In some embodiments, the permission configuration recommendation information of the data model includes field configuration prompt information; the method further includes:

[0077] In response to receiving a triggering operation performed on the field configuration prompt information, displaying a field permission configuration interface;

[0078] In the field permission configuration interface, permission configuration prompt information for the fields recommended for permission configuration is displayed.

[0079] Please explain the following with reference to Figures 4, 6, 7 and 8. Figure 8 is a schematic diagram of an application scenario. As shown in Figures 4, 6 and 7, the recommended information on permission configuration related to the data model includes field permissions. Field permissions cannot be configured in the above Figures 4, 6 and 7. As shown in Figure 7, the field permissions of data model 2 need to be configured. At this time, field configuration prompt information 702 can be displayed in the display information of the field permissions of data model 2. The first user can perform a trigger operation on the display information of the field permissions of the above data model 2, thereby displaying the field permission configuration interface. The field permission configuration interface can display a field permission configuration list, including the field names corresponding to multiple fields, and the permission items "View" and "Edit" corresponding to each field. For each permission item of each field, a permission setting control can be set. The first user can set the recommended permission items by operating the permission setting control 802.

[0080] In addition, as shown in FIG8 , permission configuration prompt information 803 is displayed near the permission setting controls corresponding to the "View" permission item of Field 2 and the "Edit" permission item of Field 1, which are recommended permission items for permission configuration, in the field permission configuration interface to prompt the first user to configure permissions for these permission items.

[0081] In these embodiments, by providing the first user with a field permission configuration function, the first user can configure permissions for the field dimension of the data model, thereby further refining the dimensions for configuring permissions for the data model.

[0082] Please refer to Figure 9, which shows a schematic flow chart 2 of the permission configuration method provided by the present disclosure. As shown in Figure 9, the method includes:

[0083] S901: In response to receiving a permission configuration request for configuring permissions for a role, displaying a permission configuration interface; wherein the permission configuration request is used to set permissions of a preset application for the above role.

[0084] S902: Displaying permission configuration recommendation information in the permission configuration interface, where the permission configuration recommendation information is used to recommend permissions to be configured.

[0085] S903: Receive the permissions configured according to the permission configuration recommendation information, and generate functional permissions associated with the above role.

[0086] S904: Displaying a permission configuration guidance page for setting permission configuration guidance information for an unauthorized operation scenario, so that the first user configures the permission configuration guidance information on the permission configuration guidance page.

[0087] The execution subject in this embodiment may be a terminal device or a server for a developer to develop an application.

[0088] There is no strict order restriction between the above step S904 and steps S901 to S903. That is, step S904 can be set before step S901, or can be set after S901, or can be executed between steps S901 and S903.

[0089] The specific implementation of the above steps S901 to S903 can refer to the relevant description of the embodiment shown in FIG1 , which will not be repeated here.

[0090] The above guidance information is used to guide users to apply for permissions for permission items that they do not have permission to operate.

[0091] The permission configuration guidance page includes a non-permission guidance text configuration item. The first user can enter a guidance text in the non-permission guidance text configuration item, or select a provided guidance text. This determines the target non-permission guidance text. When a user accessing a preset application does not have permission to access a permission item, these target non-permission guidance texts will be displayed on the user's terminal device (the client running on the terminal device).

[0092] In some embodiments, the content displayed on the permission configuration guide page includes:

[0093] Used to set user information setting items and / or setting windows for a second user with configuration authority.

[0094] In one example, the permissions configuration guide page displays a user information setting item for setting the user information of a second user with configuration permissions. This setting item includes a setting item for setting the user information of all second users with configuration permissions, such as "All Administrators," and may also include a setting item for setting the user information of a selected second user, such as "Specify." When a first user triggers the "Specify" setting item, a list of multiple second users may be displayed. The first user may select a target second user from the list as the user for whom permissions are to be configured for the feedback of unauthorized information.

[0095] In one example, the first user may input user information of the second user who is to configure permissions for the feedback information without permission, such as a user ID, in the setting window.

[0096] In this embodiment, by displaying the permission configuration guide page, developers are supported to configure the guidance information of the no-permission page, so as to shorten the problem-solving path for users who encounter no-permission scenarios.

[0097] Corresponding to the permission configuration method of the embodiment shown in FIG1 above, FIG10 is a structural block diagram of the permission configuration device provided by the embodiment of the present disclosure. For the sake of convenience, only the parts related to the embodiment of the present disclosure are shown. Referring to FIG10, the device 100 includes a first display unit 1001, a second display unit 1002 and a receiving unit 1003.

[0098] The first display unit 1001 is configured to display a permission configuration interface in response to receiving a permission configuration request for configuring permissions for a role; wherein the permission configuration request is used to set permissions for a preset application for the above role;

[0099] The second display unit 1002 is used to display permission configuration recommendation information in the permission configuration interface, where the permission configuration recommendation information is used to recommend permissions to be configured;

[0100] The receiving unit 1003 is configured to receive the permissions configured according to the permission configuration recommendation information, and generate functional permissions associated with the above role.

[0101] In one embodiment of the present disclosure, the permission configuration request indicates an operation permission for configuring a preset process and / or a preset data model associated with a page element.

[0102] In one embodiment of the present disclosure, the first display unit 1001 is further configured to:

[0103] In response to receiving a page permission configuration request for configuring permissions of a target page for a role, displaying a page permission configuration interface; and the second display unit 1002 is further configured to:

[0104] The page permission configuration interface displays the process permission configuration information and / or data model permission configuration recommendation information involved in the target page.

[0105] In one embodiment of the present disclosure, the first display unit 1001 is further configured to:

[0106] In response to receiving a permission configuration request for configuring permissions for the above role sent through a process permission configuration channel, displaying a process permission configuration interface;

[0107] The second display unit 1002 is further used for:

[0108] The process permission configuration interface displays the process permission configuration information of multiple processes involved in the recommended preset application.

[0109] In one embodiment of the present disclosure, at least one process among the multiple processes is associated with a data model, and the second display unit 1002 is further used to: display permission configuration information of the data model associated with the at least one process in the process permission configuration interface.

[0110] In one embodiment of the present disclosure, the first display unit 1001 is further configured to: in response to receiving a permission configuration request for configuring permissions for a role through a data model permission configuration channel, display a data model permission configuration interface;

[0111] The second display unit 1002 is further configured to display permission configuration recommendation information of multiple data models involved in a preset application in the data model permission configuration interface.

[0112] In one embodiment of the present disclosure, the permission configuration recommendation information of the data model includes prompt field configuration prompt information; the second display unit 1002 is further configured to: in response to receiving a trigger operation performed on the field configuration prompt information, display a field permission configuration interface;

[0113] In the field permission configuration interface, permission configuration prompt information for the fields recommended for permission configuration is displayed.

[0114] In one embodiment of the present disclosure, the permission configuration recommendation information includes:

[0115] Permission items and the permission setting controls corresponding to the permission items.

[0116] In one embodiment of the present disclosure, the permission configuration recommendation information includes a permission item and a permission setting control corresponding to the permission item; the second display unit 1002 is further configured to:

[0117] Display permission configuration prompt information near the permission setting control of the recommended permission item.

[0118] In one embodiment of the present disclosure, the display styles of the permission configuration prompt information are different before and after the permissions of the corresponding permission item are configured.

[0119] In one embodiment of the present disclosure, the second display unit 1002 is further configured to:

[0120] A one-click configuration control is displayed in the permission configuration interface, and the one-click configuration control is used to perform one-click configuration of multiple permission items indicated by the permission configuration recommendation information.

[0121] In one embodiment of the present disclosure, the apparatus 100 further includes a third display unit (not shown in the figure), which is configured to:

[0122] A permission configuration guidance page for setting permission configuration guidance information for an unauthorized operation scenario is displayed, so that the first user configures the permission configuration guidance information on the permission configuration guidance page.

[0123] In one embodiment of the present disclosure, the content displayed on the permission configuration guide page includes:

[0124] Used to set user information setting items and / or setting windows for a second user with configuration authority.

[0125] In order to implement the above embodiment, the embodiment of the present disclosure further provides an electronic device.

[0126] Referring to FIG11 , a schematic diagram of the structure of an electronic device 1100 suitable for implementing an embodiment of the present disclosure is shown. The electronic device 1100 may be a terminal device or a server. The terminal device may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (Portable Android Devices, PADs), portable multimedia players (PMPs), vehicle-mounted terminals (e.g., vehicle-mounted navigation terminals), and fixed terminals such as digital TVs and desktop computers. The electronic device shown in FIG11 is merely an example and should not limit the functionality and scope of use of the embodiments of the present disclosure.

[0127] As shown in FIG11 , the electronic device 1100 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 1101, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1102 or a program loaded from a storage device 1108 into a random access memory (RAM) 1103. Various programs and data required for the operation of the electronic device 1100 are also stored in the RAM 1103. The processing device 1101, the ROM 1102, and the RAM 1103 are connected to each other via a bus 1104. An input / output (I / O) interface 1105 is also connected to the bus 1104.

[0128] Typically, the following devices may be connected to the I / O interface 1105: an input device 1106 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 1107 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 1108 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1109. The communication device 1109 may allow the electronic device 1100 to communicate with other devices wirelessly or by wire to exchange data. Although FIG11 shows an electronic device 1100 having various devices, it should be understood that it is not required to implement or have all of the devices shown. More or fewer devices may be implemented or have alternatively.

[0129] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network via the communication device 1109, or installed from the storage device 1108, or installed from the ROM 1102. When the computer program is executed by the processing device 1101, the above-mentioned functions defined in the method of the embodiment of the present disclosure are performed.

[0130] It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program (computer-executable instructions) that can be used by or in conjunction with an instruction execution system, device, or component. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.

[0131] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0132] The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device executes the method shown in the above embodiment.

[0133] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0134] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0135] The units described in the embodiments of the present disclosure may be implemented in software or hardware. The name of a unit does not, in some cases, limit the unit itself. For example, the first display unit may be described as "a unit that displays a permission configuration interface in response to receiving a permission configuration request for configuring permissions for a role."

[0136] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, and without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chip (SOCs), complex programmable logic devices (CPLDs), and the like.

[0137] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0138] The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, but also includes other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the above-mentioned disclosed concepts. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this disclosure.

[0139] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details have been included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0140] Although the subject matter has been described in language specific to structural features and / or methodological logical acts, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims.

Claims

1. A permission configuration method, comprising: In response to receiving a permission configuration request for configuring permissions for a role, displaying a permission configuration interface; wherein the permission configuration request is used to set permissions of a preset application for the role; Displaying permission configuration recommendation information in the permission configuration interface, where the permission configuration recommendation information is used to recommend permissions to be configured; Receive permissions configured according to the permission configuration recommendation information, and generate functional permissions associated with the role.

2. The method according to claim 1, wherein the permission configuration request indicates the operation permission of configuring a preset process and / or a preset data model associated with the page element.

3. The method according to claim 1, wherein in response to receiving a permission configuration request for performing permission configuration, displaying a permission configuration interface comprises: In response to receiving a page permission configuration request for configuring permissions of a target page for the role, displaying a page permission configuration interface; as well as The displaying of the permission configuration recommendation information in the permission configuration interface includes: The process permission configuration information and / or data model permission configuration recommendation information involved in the target page are displayed in the page permission configuration interface.

4. The method according to claim 1, wherein in response to receiving a permission configuration request for configuring permissions for a role, displaying a permission configuration interface comprises: In response to receiving a permission configuration request for configuring permissions for the role sent through a process permission configuration channel, displaying a process permission configuration interface; The displaying of the permission configuration recommendation information in the permission configuration interface includes: The process permission configuration information of the recommended multiple processes involved in the preset application is displayed in the process permission configuration interface.

5. The method according to claim 4, wherein at least one of the multiple processes is associated with a data model, and the process permission configuration interface also displays permission configuration information of the data model associated with the at least one process.

6. The method according to claim 1, wherein in response to receiving a permission configuration request for configuring permissions for a role, displaying a permission configuration interface comprises: In response to receiving the permission to configure permissions for the role through the data model permission configuration channel For configuration requests only, the data model permission configuration interface is displayed; The permission configuration interface displays the permission configuration recommendation information, including: The permission configuration recommendation information of the multiple data models involved in the preset application is displayed in the data model permission configuration interface.

7. The method according to any one of claims 3, 5, and 6, wherein the permission configuration recommendation information of the data model includes field configuration prompt information; And the method further comprises: In response to receiving a trigger operation performed on the field configuration prompt information, displaying a field permission configuration interface; In the field permission configuration interface, permission configuration prompt information of the fields recommended for permission configuration is displayed.

8. The method according to claim 1, wherein the permission configuration recommendation information comprises: Permission items and permission setting controls corresponding to the permission items.

9. The method according to any one of claims 2 to 6, wherein the permission configuration recommendation information includes a permission item and a permission setting control corresponding to the permission item; and the method further comprises: Display permission configuration prompt information near the permission setting control of the recommended permission item.

10. The method according to claim 9, wherein the permission configuration prompt information is displayed in different styles before and after the permission of the corresponding permission item is configured.

11. The method according to claim 1, wherein the method further comprises: A one-key configuration control is displayed in the permission configuration interface, and the one-key configuration control is used to perform one-key configuration on multiple permission items indicated by the permission configuration recommendation information.

12. The method according to claim 1, wherein the method further comprises: A permission configuration guidance page for setting permission configuration guidance information for an unauthorized operation scenario is displayed, so that the first user configures the permission configuration guidance information in the permission configuration guidance page.

13. The method according to claim 1, wherein the content displayed in the permission configuration guide page includes: Used to set user information setting items and / or setting windows for a second user with configuration authority.

14. A permission configuration device, comprising: A first display unit, configured to display a permission configuration interface in response to receiving a permission configuration request for configuring permissions for a role; wherein the permission configuration request is used to set permissions of a preset application for the role; A second display unit is used to display permission configuration recommendation information in the permission configuration interface, where the permission configuration recommendation information is used to recommend permissions to be configured; The receiving unit is used to receive the permissions configured according to the permission configuration recommendation information and generate functional permissions associated with the role.

15. An electronic device, comprising: Processor and memory; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 13.

16. A computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when a processor executes the computer-executable instructions, the method according to any one of claims 1 to 13 is implemented.

Images