The issue we're encountering it for the

delete_membership

permission. A membership can either be deleted by a member or by the business admin of the business. Without modeling the membership as its own object, we could define the

delete_membership

permission on either the business object or the member object, but there are issues with both: * If it's defined in the business, then we don't know which user's membership is being deleted, so a user could delete another user's membership. * If it's defined in the member, we don't know which business the membership corresponds to, so an admin of a business may delete a member's membership to another business

Schema with membership as a separate definition:

definition user {
    relation self: user
}

definition business {
    relation membership: user
    relation admin: user
}


definition membership {
    relation member: user
    relation business: business

    permission delete_membership: member + business->admin
}

Schema with

delete_membership

on the business definition:

definition business {
    relation admin: user
    relation membership: user
    //...
    permission delete_membership: admin + user // ???
}

Schema with

delete_membership

on the member defintion:

definition user {
  relation self: user
  relation membership: business
  //...
  permission delete_membership: self + membership->business_admin
}

do you have concerns with that approach?