In contrast, with the implementation of Role Security; the ability to associate a User record with more than one User Group per Organization is now possible. One-to-many relationship(s) between Organizations and User Groups may now be permitted when Role security is enabled. To do so, a system administrator must incorporate one or more Role(s) for the User; which accordingly then designate the User Group into which the User will be associated for that particular Organization.
When Role Security is enabled, it is important to note that the behavior of the system changes such that permissions, menu structure, and page layout(s) for a User are determined in a slightly different manner than when it is not enabled. With Role Security, when the intermediate Role entity is configured to associate a User record to a User Group and then to an Organization; it is the User Group defined on the Role record that determines menu structure and page layout(s) for the user, where the linkage between User Group and Organization determines permissions for the user. These changes are discussed in more specific detail in later sections of this document.
Finally, it is noted that HxGN EAM users working in environments where they are required to perform multiple sets of functions (for example, purchasing, work scheduling, etc.) within a single Organization on a regular basis, may see the most impact from the adoption of the Role Security feature. If this is not the case, and an EAM User needs only to perform a single set of functions within an Organization (for example, the user is a buyer or purchaser only), then the effect of this feature may not dramatically change the user experience for that User when they access the system.