Skip the explanation of the theoretical model here, take a recent project as an example, and talk about the application in practical projects. First the background:
(1) Simple e-commerce background version, which means that it is very small and does not require any complicated permissions, and permissions are not considered at the beginning.
(2) There is an administrator account in use for both operation and development, and a financial account to guide the financial data, create a new supplier and generate a merchant account at the same time, and ship the goods to the merchant.
(3) The opportunity to increase the authority phone number list is that with the expansion of the business, the functions become more complicated, and if you don't do it, it will be messy.
The functional module of permissions is divided into three parts:
User management is to add a login account to a user so that the user can log in to the system;
The role is to tell you what I can do in the system under this identity;
Permission configuration is the management of permission functions, allowing system administrators or developers to more clearly and flexibly manage and configure system page permissions and function permissions, which are not needed by ordinary users anyway.