About implementing ACLs

Used 5 sheets.
1:roles role
2:permissions Permissions
3:permission_role Permissions-Role Correspondence table
4:role_user Role-User correspondence table
5:users User Table

This design, you danale have any better design?

Reply content:

Used 5 sheets.
1:roles role
2:permissions Permissions
3:permission_role Permissions-Role Correspondence table
4:role_user Role-User correspondence table
5:users User Table

This design, you danale have any better design?

This is a more classic design, nothing to modify. This design can only be for the role of the rights management, the user can not be independent authorization, of course, there is no need to consider this issue.

Well, not a better design.
It feels like if the post-extension is less, and the role type is less, permissions can go directly to the profile

The landlord reference under the Yii2 RBAC can

This is the structure of RBAC, not the ACL, so if the scope is limited to ACLs, as long as the structure of an ACL is better than yours, hmm.

As for RBAC, because you give only the name of the table can not give any specific advice, but also not to the business scenario, leaving business talk about design is bullying

