Rights Management, after the need to improve, the implementation of the problem occurs.

The system is divided into master account and sub account, the original requirement is that the master account has all the permissions, sub-accounts in the group, the group has permissions.

Now, the requirements have been improved, requiring the addition of Rights Management to the master account.

• The master account has a subset of the permissions, and the sub accounts only manage the permissions that are owned by the master account.

We have User_info table, authorize table.
The User_info table contains all information about the account, including the master account (identified by Owner_uid and ID).
All permission information is stored in the Authrize table.

Sub-accounts Get permissions through the group in which they are located and are identified in another group.
The master account does not exist in any group, only logically belong to the Super Admins group, that is, in the program to control.

Now the question is how does the master Account Control the permissions?

The team leader gave a plan to add two fields to the list of permissions, Is_only/is_deny.
If the Is_only field has the master Account ID data, then there is no permission on behalf of the other master account.
Conversely, the Is_deny field has the master Account ID data, which means that other master accounts have permissions.

Reply content:

The system is divided into master account and sub account, the original requirement is that the master account has all the permissions, sub-accounts in the group, the group has permissions.

Now, the requirements have been improved, requiring the addition of Rights Management to the master account.

• The master account has a subset of the permissions, and the sub accounts only manage the permissions that are owned by the master account.

We have User_info table, authorize table.
The User_info table contains all information about the account, including the master account (identified by Owner_uid and ID).
All permission information is stored in the Authrize table.

Sub-accounts Get permissions through the group in which they are located and are identified in another group.
The master account does not exist in any group, only logically belong to the Super Admins group, that is, in the program to control.

Now the question is how does the master Account Control the permissions?

The team leader gave a plan to add two fields to the list of permissions, Is_only/is_deny.
If the Is_only field has the master Account ID data, then there is no permission on behalf of the other master account.
Conversely, the Is_deny field has the master Account ID data, which means that other master accounts have permissions.

Can you add a group concept to the master account?
The sub-accounts can then be grouped only within the group permissions of the master account.

