In the previous article, we described the detailed steps and processes of module registration. In this article, we will look at the specific ideas of permission allocation and permission design. We will sort out the simple ideas of permission design, although permission design is not considered
Data permission control, but in terms of functional permissions, the configuration method is simple and flexible, and can meet the requirements of most functional permissions, the Platform also provides configuration and management of functional permissions, which are placed in specific
Data permission module. Here is the idea, which is placed in specific development and implementation, for different enterprise applications.ProgramAnd cannot make common data permission components.
Let's take a look at the permission control diagram provided by the Platform:
Let's take a look at the specific database table design:
ACL table:
Account table:
Role table:
Association table between roles and accounts:
These tables are associated to support the permission management system module of the platform. Next, let's start with the topic-Permission configuration.
This section describes the specific steps and details of permission configuration. Now that we know the concept of permission design and the specific explanations and descriptions of related tables, I believe that you have some knowledge about permission control.
How to Use the permission component to assign permissions to the module is explained and configured in each step. We try to achieve what you can understand at a glance, probably because of my limited level, this may cause unclear or vague descriptions.
Please point out and criticize.
I. Account Management:
1. Go to agileeas. NET Resource Manager:
We do not have an account here, so let's create an account first:
We create a new account for storing medicines:
After the Account type is created, the following interface is displayed:
View the association between an account and employee table or other information:
Set the binding relationship between the account and the role:
Set the association between the account and the module:
In this way, the account is bound to other information. In general, permissions can be allocated both in the account and in subsequent role management.
Ii. role management:
1. Go to the agileeas. NET Resource Management Platform:
2. Go to the role management page.
3. Click "CREATE". We will create a user role in the system. We will take the previous "drug warehouse receiving" as an example to illustrate that there is a warehouse receiving personnel.
4. Here we enter "drug warehouse receiving" and the description of this role, and then let's take a look at the content of the Module Access tab:
5. After the configuration is complete, click "OK ":
After the role is created, edit the association maintenance between the role and the account and the relationship between the role and the module.
Maintain the relationship between accounts and roles:
Next, we enter the role information dialog box. We add and delete account information to maintain the binding relationship between the account and the role:
Click "add ":
Search for account information and select the account to bind to this role:
Click "OK" to confirm our selection. Our selection will be displayed in the maintenance list of roles and accounts.
We have completed the association and binding between roles and accounts. Let's take a look at the association and binding between roles and modules. The specific process and method are similar to the binding relationship between the role and the account:
Click "add" to add the module for specific operations of the role, and configure the role to have specific permissions for operating the module:
Enter "drug warehouse receiving". The query result is used as an example to describe the binding between a role and a module. Enter "drug warehouse receiving" to query this module:
Click "OK:
3. Configure program grouping
If you do not configure a program group, it cannot be loaded by the Resource Management Platform. Because the module must be recorded as a program group, let's take a look at the maintenance of the group information:
1. Create a group:
2. Create a winform Program Group:
3. Click "new ":
,
Create a new "pharmacy management" group and add modules:
In this way, the module configuration is completed:
Click "OK:
In this way, we have completed the binding between roles and accounts, roles and modules, and thus completed permission control and allocation. Let's take a look at the specific effect:
Username: Hot, password: 123 login:
Click the drug warehouse receiving module:
In this way, the permissions are configured and accessed. Hope to help you!