I can't say either approach is appealing :) as both seem to miss the real problem, object oriented design, how to model tenancy (i rent you rent we rent a dwelling, not Multitenancy principle of software architecture )

From what little I can understand, and from what I've seen over the years, the common pattern , often seen in database tutorials, is to have a collection, a tenant is a tenant (name, contact info, financials...), addTenant, removeTenant ... just rows in a tenants table