Hacker News Reader

This has a pretty good discussion how to store hierarchical data:

Also,

you would need a user_org table for user org relation.

probably a subscription table and permission table between product and org(subscriptions) and prod and user(permissions)

you might also look at a graph database

Thanks for the reference.

This helps me think about the hierarchy of the relationships.

So it makes sense to have a user account be a member of an org.

Then have orgs have a relationship with products.

Im still questioning where I would apply role based permissions.

If a user account is a member of an org should I apply the role permission at every level?