@hsluoyz I understood you well. You can store it in a single Database field. The downside of it, the format as it is is useless. An userfriendly application has something where you have a permission process like this: 1. Create Users in e.g Table: User 2. Create Role in e.g. Table Role 4. Create Rights in e.g. Table Right 5. Assign Rights to Roles in e.g. Table Role_Right 6. Assign Users to Roles in e.g. Table Role_User So when you have a database design like this you have to transform the data for Casbin. Wouldnt it be easier if Casbin would a similar database design schema? In youre application you have a control or form or something for each of these objects.

Casbin = way to authorization

A place for Casbin developers and users

现在注册

已注册用户请登录

主题样式选择

默认主题样式 ✅

知乎主题样式

Kingside

@hsluoyz I understood you well. You can store it in a single Database field. The downside of it, the format as it is is useless. An userfriendly application has something where you have a permission process like this: 1. Create Users in e.g Table: User 2. Create Role in e.g. Table Role 4. Create Rights in e.g. Table Right 5. Assign Rights to Roles in e.g. Table Role_Right 6. Assign Users to Roles in e.g. Table Role_User So when you have a database design like this you have to transform the data for Casbin. Wouldnt it be easier if Casbin would a similar database design schema? In youre application you have a control or form or something for each of these objects.