Wave, records ownership for SaaS, how
Hi, I'm comming back 2 years later to see how Wave has evolved. Looks nice and now it works at first try.
But for a Saas starter kit I'm missing how to handle records ownership. I don't see how to do it. I'm afraid of the answer.
Thanks Jose
















Hi there,
Wave is now open-source and is under the the MIT License.
You would have full ownership of your SaaS project.
Best,
Bobby
Hmmm, I mean how to define who is the owner of each record in the database, the procedure in Wave to do it.
My question Is not about what is the license or who is the owner of the whole Saas system.
Excuse me if is not clear enough. Thanks
Hi Jose,
Thanks for the clarification!
Laravel makes this quite easy through different types for relationships, this is very well documented here:
https://laravel.com/docs/8.x/eloquent-relationships
As a standard practice when working with a relation database, this can be achieved with a simple foreign key in each table linked to the primary key from the User's table.
For example if you create a Model called Post associated with a posts table. In the posts table you would have a user_id column as as a foreign key to the users table. That way you can associated posts with specific users.
For more information about this I would recommend the official Laravel documentation here:
https://laravel.com/docs/8.x/migrations#foreign-key-constraints
Let me know if you have any questions.
Best,
Bobby
Hi Bobby,
thanks to take the time answer my questions.
I know how relationships works in Laravel, but that is not the question. What I need to know if is Wave is ready to create the data structure of a typical SaaS solution. And a key feature it is give the data owners, tenants, sellers or any other figure, the ownership of their data.
That is done automatically in other Laravel "generators" like Quickadminpanel simply with a checkbox, like... https://helpdocs.quickadminpanel.com/modules/multi-tenancy
Because Wave is market as a SaaS kit and includes CRUD feature, I assumed it has the ability to create a database structure and needed hooks or anything else to make multi-tenancy applications.
I'm wrong or missing something?
Thanks
I found a "dirty" solution, but it is like code any other thing, I would like to see as feature of Wave.
https://devdojo.com/ghost/how-to-apply-multi-tenancy-in-voyager
Thanks
Hi there,
Thank you for the clarification! Yes, multi tenancy is not available out of the box with Wave. Though the solution from this tutorial looks solid, the impelemntation is quite similar to the Quick Admin Panel trait.
I will look into this further but can't give an ETA on when this would be implemented.
Best,
Bobby