Multi-tenancy using the same database

I've been chatting with you guys in [Discord]( about this (and you are amazing!) Per your request, here's the summary of our discussion: Right now there are two solutions for multi-tenancy: • using separate databases: this is a clean solution and I like that it keeps every client's data completely separate from the others. However, if we want to have the same collection for all tenants (which is the case for me), it would be difficult to keep all these databases in synced. • the other option is achieving multi-tenancy through roles and filtering data based on $CURRENT_USER. The problem with that is I lose the ability to have multiple users for each tenant, as only the owner of the records would be able to access the data, and not their teammates. I believe there is a simple solution for this: using Project ID. For this, we would have to do two things: • In collections, the same way we have "created by" and "created on",…