Should system tables that are not domain separated by default be set up to be domain separated?

Setting system tables that are not domain separated by default to remain non-domain-separated is appropriate because these tables typically contain shared data that is relevant across different domains. By keeping these tables non-domain separated, it ensures that all users and domains can access and utilize the information consistently without unnecessary restrictions.

Domain separation is critical for isolating data between different entities or clients, particularly in multi-tenant applications, but applying domain separation indiscriminately to system tables can lead to complications. For instance, important functions like system maintenance, reporting, and administration may become more cumbersome or less efficient if essential shared data is unnecessarily fragmented.

In many cases, only specific user data should be domain-separated to maintain security and data integrity, allowing organizations to tailor their approach to data access based on their unique requirements and the roles of their users. Therefore, keeping system tables as non-domain separated facilitates ease of access and usability across the intended user base.