Project design help on Multi-tenancy
Hey guys, I'm building a web panel where each user can manage their own data (basically their own row in the database) and some other data that is associated with them (rows in other table that share their user_id).
I had a look at multi-tenancy docs, but it seems it's designed to suite a Many users -> Many teams design, where one or more users can be part of one or more teams.
In my case, however, each user would part of one and only one team, every time.
Do you think I should still use Multi-tenancy, or use Laravel Policies to manage authorizations?
2 Replies
I think policies are the right tool for this.
Thank you, will look into that