If a user has two roles and the non-primary role has no data access, what will happen?

When a user has two roles and the non-primary role has no data access, the user defaults to the primary data access. In systems where users can have multiple roles, typically the primary role is the one that determines the level of data access. If the additional role does not grant any access, it does not override or diminish the access provided by the primary role.

This concept is important for maintaining a clear hierarchy and ensuring that users retain necessary access to perform their functions effectively. As such, if the non-primary role lacks permissions, the user can still perform tasks and access data based on the permissions assigned to their primary role. This ensures that users are not inadvertently locked out of features or data they need to operate efficiently.

With this understanding, it becomes clear that the system is designed to prioritize primary role settings over non-primary roles, thus allowing users to effectively leverage their primary permissions regardless of any limitations from secondary roles.