Jon

To close this off, I couldn't get the above approach to work, and decided I don't really need it at this point, I can create Users and Companies from my admin dashboard.

I was able to get the model relations working, the only problem I encountered was I couldn't figure out how to bypass acts_as_tenant on my static(marketing) pages, so had to implement for each controller, which will work (just have to remember for new controllers!).

Thanks! To clarify, are you suggesting I create Company and User in the same form? I'm looking at blog posts like this for guidance: https://revs.runtime-revolution.com/saving-multiple-models-with-form-objects-and-transactions-2c26f37f7b9a.

Is that heading in the right direction?

Relative newbie here developing my first SaaS app and I"m struggling with the data model hierarchy. I'm expecting my customers will have 2-10 Users per Company. Currently I'll be manually onboarding customers, so I could have Users belong to a Company and create each Company and it's Users.
Seems counter to the typical model where User sits at the top, and also could be a problem if I move to self-serve signup down the road(though obviously I could create a dummy company until they fill in the info)
Any advice?