Methods for setting permissions, devices, and electronic devices

Abstract

Embodiments of this disclosure provide a method, apparatus, and electronic device for setting permissions. The method includes the steps of displaying a permission setting interface in response to receiving a permission setting request for setting permissions for a role, wherein the permission setting request is used to set permissions for a preset application of the role; displaying permission setting recommendation information on the permission setting interface that recommends permissions awaiting setting; and receiving permissions set based on the permission setting recommendation information and generating functional permissions associated with the role. This improves the efficiency and accuracy of permission setting.

Description

Technical Field

[0001] [Cross - reference to Related Applications] This application claims the priority of Chinese Patent Application No. 2023109066751, entitled "Permission Setting Method, Device and Electronic Device", filed on July 21, 2023, and the entire content of this application is incorporated herein by reference.

[0002] [Technical Field] Embodiments of the present disclosure relate to the technical field of computers, and in particular, to a permission setting method, device and electronic device.

Background Art

[0003] When a developer develops an application on a low - code platform, different page elements can be set on the pages of the application. For example, various page elements such as text, images, controls, tables, etc. may be included.

[0004] In order to display different page effects for each user or consider the security of page content, it is necessary to perform permission control on the page elements within the page. Therefore, in order to implement permission control on the page elements of a page, the developer needs to set the permissions of the page elements.

Summary of the Invention

[0005] Embodiments of the present disclosure provide a permission setting method, device and electronic device.

[0006] In a first aspect, a page processing method is provided for embodiments of the present disclosure. The method includes the steps of displaying a permission setting interface in response to receiving a permission setting request for setting permissions for a role, wherein the permission setting request is used to set permissions for a preset application for the role; displaying permission setting recommendation information on the permission setting interface that recommends permissions awaiting setting; and receiving permissions set based on the permission setting recommendation information and generating functional permissions associated with the role.

[0007] In a second aspect, a page processing device is provided for embodiments of the present disclosure. The device includes a first display unit that displays an authorization setting interface in response to receiving an authorization setting request for setting authorizations for a role, wherein the authorization setting request is used to set authorizations for a preset application for the role; a second display unit used to display authorization setting recommendation information on the authorization setting interface that recommends authorizations awaiting setting; and a receiving unit used to receive authorizations set based on the authorization setting recommendation information and to generate functional authorizations associated with the role.

[0008] In a third aspect, an electronic device comprising a processor and a memory is provided in an embodiment of the present disclosure. Computer executable instructions are stored in the memory, and the processor implements the computer executable instructions stored in the memory, thereby enabling the at least one processor to participate in the first aspect and various other ways in which it may participate in the first aspect.

[0009] In a fourth aspect, a computer-readable storage medium is provided for embodiments of the present disclosure. The computer-readable storage medium stores computer-executable instructions, and when a processor executes the computer-executable instructions, various methods can be implemented as described in the first aspect and as may be involved in the first aspect.

[0010] In a fifth aspect, an embodiment of the present disclosure provides a computer program product including a computer program. When executed by a processor, the computer program implements various methods that may be involved in the first aspect.

[0011] To more clearly illustrate the embodiments of this disclosure or the technical solutions in the prior art, the following is a brief introduction to the accompanying drawings that may be used in the description of the embodiments or the prior art. Clearly, the accompanying drawings in the following description are part of the embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these without any creative effort. [Brief explanation of the drawing]

[0012] [Figure 1] This is flowchart I, an example of the permission setting method provided in this disclosure. [Figure 2] This is a schematic diagram of the application scenario. [Figure 3] This is a schematic diagram of the application scenario. [Figure 4] This is a schematic diagram of the application scenario. [Figure 5] This is a schematic diagram of the application scenario. [Figure 6] This is a schematic diagram of the application scenario. [Figure 7] This is a schematic diagram of the application scenario. [Figure 8] This is a schematic diagram of the application scenario. [Figure 9] This is flowchart II, an exemplary method for setting permissions provided by this disclosure. [Figure 10] This is a block diagram showing the structure of the authorization setting device provided in this disclosure. [Figure 11] This is a schematic diagram showing the hardware structure of an electronic device provided by an embodiment of the present disclosure. [Modes for carrying out the invention]

[0013] To further clarify the purpose, technical solutions, and advantages of the embodiments of this disclosure, the technical solutions in the embodiments of this disclosure will be described clearly and completely below, in conjunction with the accompanying drawings of the embodiments of this disclosure. Obviously, the embodiments described are not all of the embodiments of this disclosure, but only a portion of them. All other embodiments that can be obtained by a person skilled in the art without creative effort based on the embodiments of this disclosure are also within the scope of this disclosure.

[0014] Developers can develop applications using various development methods. For example, developers can develop applications using a low-code approach. The developed application may contain multiple pages. Each page may contain multiple page elements.

[0015] To ensure data security in the above application, appropriate permissions must be set for page elements. For example, a page element (e.g., a control) is associated with a process event that is triggered when an application user performs a corresponding operation on that page element. If the permissions for this page element are not controlled based on roles, this process event may be frequently accessed inappropriately, leading to wasted resources. For example, if a page element is associated with a database, the permissions for this page element must be controlled to prevent information leakage from that database.

[0016] In addition, as the requirement for fine - grained permission settings, such as setting the permission control of database objects down to the field level, becomes higher, the number of permission items for which permissions need to be set increases. When setting permissions for a large number of permission items, there is a possibility of omission. In some application scenarios, if some page elements that require permissions do not have permissions set for a role, usually, this role does not have the permission to access or operate on this page element. In such application scenarios, there is a possibility that the user cannot display the application page normally or cannot operate the page elements within the page normally.

[0017] To avoid the problem of missing permission settings for page elements, in the solution of the present disclosure, when a developer needs to set permissions for a preset application role, recommended information for permission settings is displayed to recommend the permissions waiting to be set to the developer. Thereby, the problem of missing permission settings in the application can be avoided to a certain extent, and furthermore, the efficiency of permission setting can be improved.

[0018] Referring to FIG. 1, it is an exemplary flowchart I of the permission - setting method provided by the present disclosure. As shown in FIG. 1, this method includes S101: In response to receiving a permission - setting request for setting the permissions of a role, it is a step of displaying a permission - setting interface, where the permission - setting request includes steps used for setting the permissions of a preset application for the above - mentioned role.

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

[0020] The preset application referred to here may be an application under development, a developed application, or may include an application that has already been launched, etc.

[0021] In some embodiments, the permission setting request instructs the operation permission to set a preset process and / or a preset data model associated with the page element.

[0022] The first user (application developer) can use the above execution entity to set a plurality of pages for the application on the low-code platform and set page elements on the pages. Application development is carried out in a visual way on the low-code platform, and the developer can create an application by dragging and dropping components through a graphical user interface. On the low-code platform, page elements can be realized by components and models provided by the low-code platform. The components and models on the low-code platform may be pre-associated with a process and / or a data model.

[0023] As an illustrative example, the component corresponding to page element 1 may be associated with an event such as a touch event, etc. This touch event may be associated with one process such as a problem handling process. This problem handling process is preset to require operation permission. Also, the component corresponding to page element 2 may be associated with a data model, for example. The data model referred to here can be understood as a pre-stored data set composed of a plurality of fields. This data set is preset to require permission for operations.

[0024] In low-code platforms, page elements are pre-associated with preset processes, allowing different permissions to be set for different roles. For example, if the above preset process permission is set for Role 1, users with the ID of Role 1 are granted permission to manipulate this page element. By manipulating this page element, these users can initiate background execution of the process corresponding to this page element. The background process can return the execution results to the user, and users with the ID of Role 1 can view these results. As another example, if no permission is set for Role 2, users with the ID of Role 2 are not granted permission to manipulate this page element. Therefore, by setting permissions for applications developed using a low-code platform, it is possible to prevent inappropriate access to preset processes associated with page elements within the application and the leakage of database information.

[0025] In these embodiments, by setting operational permissions for the preset process and / or preset data model associated with the page element, it is possible to execute functions corresponding to the preset process and / or data model based on user actions on the page element.

[0026] The roles referred to here may be roles currently being created by the developer, or roles that have already been created.

[0027] After the first user has configured at least one page in the application, the permissions for the above role must be set in order for a user with the ID of the above role to be able to successfully view the application's pages and manipulate the page elements of the application's pages.

[0028] The roles referred to here may be any roles set by the first user for a preset application. For example, the above roles may be regular viewer, administrator, owner, etc., roles set by the first user. The first user can set different roles for different applications. For example, for an application running in a library, roles such as librarian who manages books and user administrator who manages users of books may be set.

[0029] The first user can initiate a permission setting request to grant permissions to the above role. After receiving the permission setting request, the executing entity can display the permission setting interface.

[0030] S102: The permission settings interface displays recommended permission settings information for permissions that are awaiting configuration.

[0031] After receiving the permission setting request, the above-mentioned implementing entity may display the permission setting interface and display recommended permission setting information on the permission setting interface.

[0032] The recommended permission settings information above includes the permission items to be granted permissions to, as recommended by the executing entity, and the permission setting controls for granting permissions to those permission items. For example, the executing entity can determine which permission items are awaiting permission setting based on the preset permission control information of the process and / or data model associated with the page element.

[0033] S103: Receives permissions set based on recommended permission settings and generates functional permissions associated with the role.

[0034] The first user can view the recommended permission settings information and set permissions for the permission items recommended by that information. Setting permissions for the above permission items means granting permissions for those permission items to the above role.

[0035] The above-mentioned entity can generate functional permissions associated with the above role based on the received permission setting results. Illustratively, these functional permissions may include permissions to view / manipulate pages, permissions to operate processes involved in preset applications, and permissions to view / manipulate data.

[0036] The above roles have permission to perform actions such as viewing, clicking, searching, and modifying on page elements associated with the permission items for which they have been assigned.

[0037] The method for setting permissions for an application is performed using a list of permission settings corresponding to the application. This list of permission settings may include all page elements of the application that need permission control, and the permission items that need to be set for each page element. Users set permissions for each page element one by one using this list. The above element setting list is lengthy. When setting permissions for page elements using a lengthy permission setting list, it is inevitable that permission settings will be missed, resulting in users being unable to properly view pages or interact with page elements.

[0038] In this embodiment, the authorization setting interface is displayed in response to receiving an authorization setting request for setting role permissions. Here, the authorization setting request is used to set permissions for a preset application for the role, and the authorization setting interface displays authorization setting recommendation information that suggests permissions awaiting setting, receives the permissions set based on the authorization setting recommendation information, and generates the functional permissions associated with the role. When authorization setting is performed, authorization setting recommendation information is provided, and the authorization setter can set permissions based on the authorization setting recommendation information, thereby avoiding omissions in authorization setting on the one hand, and improving the efficiency of authorization setting and the accuracy of the setting results on the other hand.

[0039] In some embodiments, step S101 includes displaying a page permission setting interface in response to receiving a page permission setting request to perform permission setting for the target page for the role, and step S102 includes displaying relevant process permission setting information and / or recommended data model permission setting information for the target page in the page permission setting interface.

[0040] Referring to Figures 2 and 3, Figure 2 is a schematic diagram of the application scenario, and Figure 3 is a schematic diagram of the application scenario. As shown in Figure 2, the first user can open the list of roles, which may contain information (role identifiers) for multiple roles, such as role A1, role A2, and role A3 shown in Figure 2.

[0041] The first user (developer) selects the target role "Role A1" awaiting permission settings in the preset application's role list (roles in the role list may be created by the first user).

[0042] After the first user selects the target role A1, they can initiate a permission setting request to set permissions for role A1. The first developer can also create role A1 in real time and then initiate a permission setting request to set permissions for role A1. As shown in Figure 3, after receiving the permission setting request, the executing entity can display permission setting items for "page permissions," "process permissions," and "data model permissions" on the interface.

[0043] The first user can click on page permissions to display page list 301. Page list 301 may display all page information related to the preset application, such as page 1, page 2, and page 3 in Figure 3. Page list 301 may also display recommended permission settings for setting permissions for each page. In Figure 3, the recommended permission settings information "0 / 3" corresponds to page 1, where "3" is the number of permission items that are recommended to be set on page 1, and "0" is the number that has been set. The recommended permission settings information "0 / 6" corresponds to page 2, where "6" is the number of permission items that are recommended to be set on page 2, and "0" is the number that has been set. The recommended permission settings information "0 / 2" corresponds to page 3, where "2" is the number of permission items that are recommended to be set on page 1, and "0" is the number that has been set.

[0044] The first user can perform a trigger operation on a preset location on page 2 in the page list 301 in Figure 3. For example, by performing a trigger operation on the area surrounding the recommended permission information "0 / 6" on page 2, the page permission setting interface 401 on page 2 can be displayed, as shown in Figure 4. Figure 4 is a schematic diagram of the application scenario. As shown in Figure 4, page 2 displays six recommended permission items for permission setting, as shown in the page permission setting interface 401. The recommended information for process permission setting includes the process name and permission setting controls 402 for setting the process permission items. As shown in Figure 2, the process permission items include trigger permission. The processes associated with page 2 include processes B1, B2, and B3. The permission setting controls 402 corresponding to each process can be displayed in association with this process name. Specifically, the permission setting controls corresponding to each process are set on one side of the process name of this process. The first user can set the process permission by performing a preset operation (such as a selection operation) on the permission setting controls associated with the process name of the process.

[0045] The recommended permission settings information above also includes the recommended permission settings information for the data model, which includes the permission settings information for data model 1, data model 2, and data model 3 associated with page 2. The page permission setting interface 401 displays the names of data model 1, data model 2, and data model 3, as well as multiple permission items pre-configured for the data model, such as the permission items "Search," "Edit," "Add," and "Delete" in Figure 4. The first user can selectively configure the above-mentioned permission items for data model 1, data model 2, and data model 3 that are recommended on page 2 in Figure 4.

[0046] In some embodiments, this method is Further steps include displaying prompt information for permission settings near the permission settings control for permission items that are recommended to be configured.

[0047] The above permission setting prompt information may include text and / or graphics. For example, the above prompt information may include a graphic of a solid circle.

[0048] As an illustrative example, in a page permission setting interface, for each recommended data model that may contain multiple permission items, the executing entity can determine which permission items are recommended for setting permissions for the data model. The executing entity can prompt the first user to set permissions for these permission items by displaying permission setting prompt information, such as permission setting prompt information 405 in Figure 4, near the permission setting control for the permission items that are recommended to be set. Displaying permission setting prompt information near the permission setting control for the permission items that are recommended to be set can further improve the efficiency and accuracy of permission setting.

[0049] In some embodiments, permission setting prompt information is displayed in different styles before and after the permission for the corresponding permission item is set.

[0050] For example, the permission setting prompt information shown above is displayed in different colors and sizes before and after the permission is set for the corresponding permission item.

[0051] In these embodiments, by displaying permission setting prompt information in different styles before and after permissions are set for the corresponding permission items, the first user can be shown whether or not these permissions are set, which helps prevent unset permissions from being overlooked, and also makes it easier for the first user to view information on the permission items that have been set.

[0052] In some embodiments, a one-key configuration control is displayed in the authorization configuration interface, and the one-key configuration control is used to configure multiple authorization items presented by authorization configuration recommendation information with a single key.

[0053] As shown in Figure 4, a one-key setting control 404 can be displayed in the page permission setting interface. The first user can perform a trigger operation on this one-key setting control 404, and after receiving the trigger operation, the execution entity can perform permission settings in the background for the recommended permission items corresponding to data model 1, data model 2, and data model 3, respectively. This enables one-key setting for the permission items of the recommended data models.

[0054] By configuring a one-key setting control in the permission settings interface, multiple permission items can now be set with a single key, further improving the efficiency of permission settings.

[0055] In some embodiments, step S101 includes displaying the process authorization interface in response to receiving an authorization request for authorization to a role, which has been sent via the process authorization channel, and step S102 includes displaying recommended process authorization information for a plurality of processes related to a preset application in the process authorization interface.

[0056] Furthermore, at least one process in a multi-process architecture is associated with a data model, and the process permission settings interface also displays permission information for the data model associated with this at least one process.

[0057] The following explanation combines Figures 3, 5, and 6. Figure 5 is a schematic diagram of the application scenario. Figure 6 is a schematic diagram of the application scenario. The first user can send a permission setting request to set permissions for a role via the process permission setting channel by performing a selection operation on the process permission setting item in Figure 3. After receiving the permission setting request, the execution entity can display the process permission setting interface as shown in Figure 5. The process permission setting interface 501 can determine the target processes from the processes associated with each page element of all pages of the preset application and display recommended permission setting information for setting permissions for these target processes. In Figure 5, processes B1, B2, B3, and B4 are recommended for setting permissions, and permission setting controls 502 are set for each process.

[0058] Furthermore, if the recommended process is further associated with a data model, the recommended data model permission settings information can be displayed in the process permission settings interface 501 as "Set (0 / 3)" in the "Recommended Permissions to Open" column corresponding to process B1 in Figure 5. This recommended data model permission settings information is used by the first user to open permissions for the data model associated with process B1. By performing a trigger operation on the above recommended data model permission settings information, the first user can display the data model permission settings interface 601 for the data model associated with process B2, as shown in Figure 6. Figure 6 is a schematic diagram of the application scenario. The data model permission settings interface 601 can display the data model identifiers for data model 4, data model 5, and data model 6, and a list of data model permission settings associated with process B2, including permission items "Search," "Edit," "Add," and "Delete" corresponding to each data model. Each permission item for each data model corresponds to one permission setting control 602. The first user can set permissions for the data model associated with process B2 in the above data model permission settings interface 601.

[0059] In these embodiments, the first user can set permissions in terms of multiple processes associated with a preset application by providing a process permission setting channel for the first user to set process permissions, thereby providing the first user with other channels for setting permissions so that the first user can set process permissions through different channels.

[0060] In some embodiments, step S101 includes displaying the data model authorization interface in response to receiving an authorization request via the data model authorization channel to set authorizations for a role, and step S102 includes displaying recommended information for a number of data model authorization settings related to a preset application on the data model authorization interface.

[0061] Figures 3 and 7 will be explained below. Figure 7 is a schematic diagram of the application scenario. The first user can select an operation for executing data model permissions in the permission setting items in Figure 3, thereby sending a permission setting request to set permissions for a role via the data model setting channel. After receiving the permission setting request, the execution entity can display the data model permission setting interface as shown in Figure 7. The data model permission setting interface 701 can determine the target data models for which permission setting is recommended from the data models associated with page elements on all pages of the preset application (including data models associated with processes), and display recommended permission setting information for setting permissions for these target data models. As shown in Figure 7, the following are recommended for permission setting: data model 1, data model 2, data model 3, data model 4, data model 5, data model 6, and permission items. The permission items corresponding to each data model include "search," "edit," "add," and "delete." Each permission item for each data model corresponds to one permission setting control 702. The first user can set permissions for the above data models using the data model permission setting interface 701.

[0062] In these embodiments, the first user sets permissions in terms of multiple data models related to a preset application by providing data model permission settings for the first user to set permissions for a data model, and the first user sets permissions for a data model through different channels by providing the first user with other channels for permission settings.

[0063] In some embodiments, the data model permission settings recommendations include field setting prompts. This method further includes: The steps include: displaying the field permission setting interface in response to receiving a trigger operation to be performed on the field setting prompt information; The field permission setting interface includes a step of displaying permission setting prompt information for fields where permission settings are recommended.

[0064] Figures 4, 6, 7, and 8 will be explained below in conjunction with each other. Figure 8 is a schematic diagram of the application scenario. As shown in Figures 4, 6, and 7, the recommended information for permission settings related to the data model includes field permissions. In Figures 4, 6, and 7, it is not possible to set field permissions. As shown in Figure 7, it is necessary to set the permissions for the fields of data model 2, and at this time, prompt information for field settings can be displayed in the display information for field permissions of data model 2. The first user can display the field permission setting interface by performing a trigger operation on the information that displays the field permissions of data model 2. The field permission setting interface can display a list of field permission settings, including the field names for each of the multiple fields, and "search" and "edit" for the permission items corresponding to each field. Permission setting controls can be set for each permission item of each field. The first user can set the recommended permission items by operating the permission setting control 802.

[0065] Furthermore, as shown in Figure 8, in the field permission setting interface, permission setting prompt information 803 is displayed near the permission setting controls corresponding to the "Search" permission item in Field 2 and the "Edit" permission item in Field 1, which are permission items for which permission setting is recommended. This allows the first user to be prompted to set permissions for these permission items.

[0066] In these embodiments, by providing the first user with the ability to set field permissions, the first user can set field dimension permissions for the data model. This further narrows down the dimensions for which permissions can be set for the data model.

[0067] Referring to Figure 9, an exemplary flowchart II of the authorization setting method provided in this disclosure is shown. As shown in Figure 9, this method is S901: A step of displaying the permission setting interface in response to receiving a permission setting request for setting permissions for a role, wherein the permission setting request is used to set permissions for a preset application for the role, S902: The permission settings interface includes a step to display recommended permission settings information for permissions awaiting configuration, and S903: The steps include receiving permissions configured based on the recommended permission settings and generating functional permissions associated with the above role, S904: Includes the step of displaying a permission setting guidance page for setting permission setting guidance information for a scenario without operational permissions, so that the first user sets permission setting guidance information on the permission setting guidance page.

[0068] In this embodiment, the execution entity can be a terminal device or server for a developer to develop an application.

[0069] There are no strict order restrictions between step S904 and steps S901 to S903. In other words, step S904 may be set before step S901, after step S901, or executed between steps S901 and S903.

[0070] The specific implementation of steps S901 to S903 described above can be found in the relevant explanations of the embodiment shown in Figure 1, so they will not be repeated here.

[0071] The above guidance information is used to prompt users to request permission for items for which they do not currently have the necessary operational rights.

[0072] The above permission settings guidance page includes a setting for non-authorized guide copywriters. The first user can enter a guide copywriter in the non-authorized guide copywriter setting field or perform a selection operation on the provided guide copywriters. This determines the target non-authorized guide copywriters. If a user accessing the preset application does not have permission to access the permission fields, these target non-authorized guide copywriters will be displayed on the user's terminal device (the client running on the terminal device).

[0073] In some embodiments, the content displayed on the permission setting guidance page may include: This includes installation items and / or an installation window used to install user information for a second user who has configuration privileges.

[0074] In one example, the above permission setting guidance page displays configuration items used to set the user information of a second user who has configuration privileges. These configuration items include configuration items such as "All Administrators," which are used to set the user information of all second users who have configuration privileges, and may also include configuration items such as "Specify," which are used to set a selected second user. When the first user performs a trigger operation on the "Specify" configuration item, a list of multiple second users is displayed, and the first user can select the target second user from the list of second users to set as the user with permissions as the unauthorized information to be fed back.

[0075] In one example, the first user can input user information, such as the user identifier, of a second user who does not have the authority to set the information to be fed back into the installation window.

[0076] In this embodiment, displaying a permission setting guidance page helps developers configure guidance information for pages they do not have permission to access, thereby shortening the route to resolving the issue of users encountering permissionless scenarios.

[0077] Corresponding to the authorization setting method of the embodiment shown in Figure 1 above, Figure 10 is a block diagram showing the structure of the authorization setting device provided by the embodiment of the present disclosure. For the sake of ease of explanation, only the parts relevant to the embodiment of the present disclosure are shown. Referring to Figure 10, the device 100 has a first display unit 1001, a second display unit 1002, and a receiving unit 1003. Here, The first display unit 1001 is used to display an authorization setting interface in response to receiving an authorization setting request for setting authorizations for a role, where the authorization setting request is used to set authorizations for a preset application for the role. The second display unit 1002 is used to display recommended permission settings information on the permission setting interface, which recommends permissions that are awaiting configuration. The receiving unit 1003 receives the permissions set based on the recommended information for permission settings and is used to generate the functional permissions associated with the role.

[0078] In one embodiment of the present disclosure, a permission setting request instructs to set permissions to operate on a preset process and / or preset data model associated with a page element.

[0079] In one embodiment of the present disclosure, the first display unit 1001 further comprises: It is used to display the page permission setting interface in response to receiving a page permission setting request to set permissions for the target page for a role. Furthermore, the second display unit 1002 also: This is used to display process permission settings information and / or recommended data model permission settings associated with the target page in the page permission settings interface.

[0080] In one embodiment of the present disclosure, the first display unit 1001 further comprises: This is used to display the process privilege setting interface in response to receiving a privilege setting request to set privileges for the above role, which has been sent via the process privilege setting channel.

[0081] The second display unit 1002 further, This is used to display process permission settings information for multiple processes related to the recommended preset application in the process permission settings interface.

[0082] In one embodiment of the present disclosure, at least one process in a plurality of processes is associated with a data model, and a second display unit 1002 is further used to show the data model authorization information associated with this at least one process to the process authorization setting interface.

[0083] In one embodiment of the present disclosure, the first display unit 1001 is further used to display a data model authorization interface in response to receiving an authorization request to set authorizations for a role via a data model authorization channel. The second display unit 1002 is further used to display recommended information for multiple data model permission settings related to a preset application on the data model permission setting interface.

[0084] In one embodiment of the present disclosure, the recommended information for data model authorization settings includes prompt information for the presented field settings. A second display unit 1002 is further used to display the field authorization setting interface in response to receiving a trigger operation performed on the field setting prompt information.

[0085] The field permission settings interface displays permission setting prompt information for fields where permission settings are recommended.

[0086] In one embodiment of this disclosure, the recommended information for permission settings includes: This includes permission items and permission setting controls corresponding to those permission items.

[0087] In one embodiment of the present disclosure, the permission setting recommendation information includes permission items and permission setting controls corresponding to the permission items. The second display unit 1002 further, This is used to display permission setting prompt information near the permission setting controls for permission items that are recommended to be configured.

[0088] In one embodiment of this disclosure, permission setting prompt information is displayed in different styles before and after the permission for the corresponding permission item is set.

[0089] In one embodiment of the present disclosure, the second display unit 1002 further comprises: It is used to display a one-key configuration control in the permission settings interface, and the one-key configuration control is used to configure multiple permission items indicated by the permission setting recommendations with a single key.

[0090] In one embodiment of the present disclosure, the apparatus 100 further comprises a third display unit (not shown), the third display unit is This is used to display a permission settings guidance page for setting permission settings guidance information for scenarios where the user has no operational permissions, so that the first user can set permission settings guidance information on the permission settings guidance page.

[0091] In one embodiment of this disclosure, the content displayed on the permission setting guidance page includes: This includes installation items and / or an installation window used to configure user information for a second user who has configuration privileges.

[0092] To realize the above embodiments, the present disclosure further provides electronic devices.

[0093] Referring to Figure 11, Figure 11 shows a schematic diagram of the structure of an electronic device 1100 suitable for use in realizing an embodiment of the present disclosure. This electronic device may be a terminal device or a server. Here, the terminal device includes, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, personal portable information devices (PDAs), tablet computers (PADs), portable multimedia players (PMPs), and in-vehicle terminals (such as in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop PCs. The electronic device shown in Figure 11 is merely an example and should not impose any limitations on the function and scope of use of the embodiment of the present disclosure.

[0094] As shown in Figure 11, the electronic device 1100 may include a processing unit (e.g., a central processing unit, a graphics processor, etc.) 1101 that can perform various appropriate operations and processes based on 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. The RAM 1103 stores various programs and data necessary for the operation of the electronic device 1100. The processing unit 1101, ROM 1102, and 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.

[0095] Typically, the I / O interface 1105 can be connected to input devices 1106, including touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 1107, including liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1108, including magnetic tape, hard drives, etc.; and communication devices 1109. The communication device 1109 can enable the electronic device 1100 to communicate with other devices wirelessly or via wired connections to exchange data. Figure 11 shows the electronic device 1100 with various devices, but it should be understood that it is not necessary to implement or include all of the devices shown. Alternatively, more or fewer devices may be implemented or included.

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

[0097] It should be noted that the computer-readable media described herein may be computer-readable signal media, computer-readable storage media, or any combination of the two. Computer-readable storage media may be, but are not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or components, or any combination thereof. More specific examples of computer-readable storage media include, but are not limited to, electrical connections with one or more leads, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disc read-only memory (CD-ROM), optical storage components, magnetic storage components, or any suitable combination of the above. In this disclosure, computer-readable storage media may be any tangible medium containing or storing programs (computer-executable instructions) that can be used by or in combination with instruction execution systems, devices, or components. In this disclosure, a computer-readable signal medium may include data signals propagated in the baseband or as part of a carrier wave, wherein computer-readable program code is carried therein. The data signals propagated in this manner may include, but are not limited to, electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium may be any computer-readable medium other than a computer-readable storage medium, and this computer-readable signal medium may transmit, propagate, or transmit programs used by or in combination with instruction execution systems, devices, or components. The program code contained in the computer-readable medium may be transmitted using any suitable medium, including, but not limited to, electric wires, fiber optic cables, RF (radio frequency), or any suitable combination thereof.

[0098] The computer-readable medium described above may be included in the electronic device, or it may exist independently without being combined with the electronic device.

[0099] The computer-readable medium described above carries one or more programs that, when executed by the electronic device, cause the electronic device to perform the method shown in the above embodiment.

[0100] Computer program code for performing the operations of this disclosure may be written in one or more programming design languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and traditional procedural programming languages ​​such as the C language or similar programming languages. The program code may run entirely on the user's computer, partially on the user's computer, partially on the user's computer as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. If a remote computer is involved, the remote computer may be connected to the user's computer via any kind of network, including a local area network (LAN) or a wide area network (WAN), or it may be connected to an external computer (for example, connected via the Internet using an Internet service provider).

[0101] The flowcharts and block diagrams in the accompanying drawings illustrate the architectures, functions, and operations that can be implemented in systems, methods, and computer program products based on various embodiments of this disclosure. In this regard, each box in a flowchart or block diagram may represent a module, program segment, or part of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions shown within the boxes may occur in a different order than shown in the accompanying drawings. For example, two boxes shown consecutively may actually be executed substantially in parallel, or they may be executed in reverse order depending on the functions involved. It should also be noted that each box in a block diagram and / or flowchart, and combinations of boxes in a block diagram and / or flowchart, may be implemented based on a dedicated hardware-based system that performs the specified function or operation, or by a combination of dedicated hardware and computer instructions.

[0102] The units described in embodiments of this disclosure and relating to them may be implemented in software or in hardware. Where the names of the units do not, in some cases, constitute a limitation on the units themselves, for example, the first display unit may also be described as "a unit that displays an authorization setting interface in response to receiving an authorization setting request for setting authorizations for a role."

[0103] The functions described herein may be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that may be used include, but are not limited to, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standards (ASSPs), systems on chips (SOCs), and composite programmable logic devices (CPLDs).

[0104] In the context of this disclosure, machine-readable media may be tangible media that contain or can store programs used by or in combination with instruction execution systems, apparatuses, or devices. Machine-readable media may be machine-readable signal media or machine-readable storage media. Machine-readable media include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0105] The above description is merely a description of preferred embodiments of the Disclosure and a description of the technical principles used. Those skilled in the art will understand that the scope of the disclosure relating to this disclosure is not limited to technical solutions formed by specific combinations of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or equivalent features without departing from the above-disclosed concepts, for example, technical solutions formed by replacing the above features with similarly functional technical features disclosed in this disclosure (but not limited to these).

[0106] Furthermore, although each operation is described in a specific order, this should not be understood as requiring such operations to be performed in a specific order or sequential sequence as shown. Multitasking and parallel processing may be advantageous in certain environments. Similarly, although some specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented in multiple embodiments, individually or in any suitable subcombination.

[0107] While this subject matter is described using language specific to the structural features and / or logical operation of the method, it should be understood that the subject matter defined in the attached claims is not necessarily limited to the specific features or operations described above. Rather, the specific features and operations described above are merely exemplary forms of implementing the claims.

Claims

1. A method for setting permissions, A step of displaying a permission setting interface in response to receiving a permission setting request for setting permissions for a role, wherein the permission setting request is used to set permissions for a preset application for the role, The aforementioned permission setting interface includes a step of displaying recommended permission setting information to recommend permissions awaiting configuration, A method comprising the steps of receiving permissions set based on the aforementioned permission setting recommendations and generating functional permissions associated with the role.

2. The aforementioned permission setting request instructs the user to grant operational permissions to set a preset process and / or preset data model associated with a page element. The method according to claim 1.

3. In response to receiving a permission setting request to perform the aforementioned permission setting, the step of displaying the permission setting interface includes: The steps include displaying the page permission setting interface in response to receiving a page permission setting request to set permissions for the target page for the aforementioned role, and The step of displaying recommended information for the permission settings in the permission setting interface includes: The page permission setting interface includes a step of displaying process permission setting information and / or recommended data model permission setting information related to the target page. The method according to claim 1.

4. In response to receiving the permission setting request for setting the permissions of the role, the step of displaying the permission setting interface includes: The step includes displaying the process privilege setting interface in response to receiving a privilege setting request for setting the privileges of the role, which has been sent via the process privilege setting channel. The step of displaying recommended information for the permission settings in the permission setting interface includes: The process permission setting interface includes a step of displaying recommended process permission setting information for multiple processes associated with the preset application. The method according to claim 1.

5. At least one of the aforementioned processes is associated with a data model, and the process permission setting interface also displays permission setting information for the data model associated with this at least one process. The method according to claim 4.

6. In response to receiving the permission setting request for setting the permissions of the role, the step of displaying the permission setting interface includes: The step includes displaying the data model authorization interface in response to receiving an authorization request to configure the permissions of the role via the data model authorization channel. The step of displaying recommended information for the permission settings in the permission setting interface includes: The data model permission setting interface includes a step of displaying recommended permission settings for multiple data models related to the preset application. The method according to claim 1.

7. The recommended information for data model permission settings includes prompt information for field settings, and the method further includes: The steps include: displaying the field permission setting interface in response to receiving a trigger operation to be performed on the prompt information of the field setting; The field permission setting interface includes the step of displaying permission setting prompt information that recommends performing permission setting on the field, The method according to any one of claims 3, 5, or 6.

8. The recommended information for the aforementioned permission settings includes: This includes permission items and permission setting controls corresponding to those permission items. The method according to claim 1.

9. The recommended information for the permission settings includes permission items and permission setting controls corresponding to those permission items, and the method further includes: The step includes displaying permission setting prompt information near the permission setting control for the permission item for which the setting is recommended. The method according to any one of claims 2 to 6.

10. The prompt information for the aforementioned permission settings has a different display style before and after the permission for the corresponding permission item is set. The method according to claim 9.

11. The above method further, The step includes displaying a one-key setting control in the permission setting interface, wherein the one-key setting control is used to perform one-key settings for multiple permission items indicated by the permission setting recommendation information. The method according to claim 1.

12. The above method further, The process includes the step of displaying a permission settings guide page for setting permission settings guide information for a scenario without operational permissions, so that the first user can set permission settings guide information on the permission settings guide page. The method according to claim 1.

13. The information displayed on the aforementioned permission settings guidance page includes: This includes installation items and / or an installation window used to install user information for a second user who has configuration privileges. The method according to claim 1.

14. It is an authorization setting device, A first display unit that displays a permission setting interface in response to receiving a permission setting request for setting permissions for a role, wherein the permission setting request is used to set permissions for a preset application for the role, The aforementioned permission setting interface includes a second display unit used to display permission setting recommendation information for recommending permissions awaiting configuration, A receiving unit that receives permissions set based on the recommended information for the permission settings and is used to generate functional permissions associated with the role, Device.

15. It is an electronic device, Equipped with a processor and memory, The aforementioned memory stores computer executable instructions. The processor performs the method according to any one of claims 1 to 13 by executing computer executable instructions stored in the memory. Electronic devices.

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

Images