Muti-Tenant Design Pattern

If creating a multi tenant system (for example with multiple companies), the AI should not try to extend the base User entity and pretend that you will be able to manage users and list them. Only to be surprised by a nasty error saying none of that is allowed once you deploy to production. The Build AI should know that. In a muti tenant system, it should instead create it's own extended junction. Trying to extend the User entity is a waste of time and credits

instead, it should create a custom entity junction like "CompanyUser", and build everything off that linked back to the base User entity by id. It should not try to add fields to the base User entity at all. My complaint here is that not everyone is an Enterprise Architect. If you want to tout that "Anyone can build an app" with Base44, it needs to follow not only basic design patterns, but it should also know it's own data restrictions, like the User entity limitations, and not code that way