Thanks for the quick reply. It does not, as it uses context variables.
Native I mean is that I enforce it by raising an error it it is not specified in the View. Native in the sense to keep request and models separate as per Django’s design.
As mentioned in the thread: django multi tenancy issue, thread local does not work in async. Thus if feels like a suboptimal solution and not fully compatible with Django.
It should not be that hard to enforce this at the modelmanager level ?
A possible solution would be to overwrite all “get, filter, all” methods for example and validate that the required filter (tenant / site) is set as a kwarg. I search a way that I do not need to overwrite all these methods but can overwrite a single one?