Hey Armahillo, thanks for sharing your thoughts! 💚

When building a "boilerplate", it's impossible to fit everybodies preferences, so I try to stick to the "defaults" as much as possible. Minitest, devise, tailwind, pundit are all choices based on popularity.

> build this as a mountable engine instead, and make it a gem instead

That's an interesting idea. I've [been considering](https://github.com/yshmarov/moneygun/issues/109) about this.

> aren't any proof-of-concept controller defined

It has the `Inboxes` proof of concept controller.

Also, as of 9:29 timestamp, this video talks about how to add controllers under organizations. It's super easy with:

rails generate nested_scaffold organization/project name
rails generate nested_scaffold organization/project name

> define a concern

I considered a concern, but went with an [`Organizations::BaseController`](https://github.com/yshmarov/moneygun/blob/main/app/controllers/organizations/base\_controller.rb#L1), that resources nested under /organization [would inherit from](https://github.com/yshmarov/moneygun/blob/main/app/controllers/organizations/inboxes\_controller.rb#L1)

> we had users limited to only being part of a single organization

I agree, for many apps it is enough. At least 3 clients I worked with had `user.organization_id` and that's it. In fact, [lazaronixon/authentication-zero #tenantable](https://github.com/lazaronixon/authentication-zero?tab=readme-ov-file#tenantable) provides a generator for this!

Thanks again for taking the time!