Collaboration group relations with WFM hierarchy
Updated
by
Victor Jespersen
This article will provide a detailed explanation of the relations between the collaboration group functionality and the WFM hierarchy. The complex systems can cause confusion at first, but after reading this article, you'll have all the knowledge you need to understand how these two systems work with each other.
WFM hierarchy
The WFM hierarchy is your organizational structure, which you set up in Quinyx. The hierarchy includes the domain, district, units, and sections. The hierarchy should reflect your internal organization's structure, and the employees should be assigned to the hierarchy groups accordingly. By doing so, you can have a clear view of which unit or stores are under which district, and who is working under what unit/ store, etc.
Collaboration groups
The collaboration group is an Employee Hub-specific hierarchy that works in tandem with the WFM hierarchy. The collaboration group hierarchy should also reflect your company structure for a clearer understanding of the different managerial groups and stores.
Relations between the two hierarchies
Collaboration groups primarily exist for organizations using both Employee Hub and Quinyx WFM. If your company is using both Employee Hub and Quinyx, using the WFM organization hierarchy is required for customers working within the Quinyx setup.
If you're using both Quinyx WFM and EH, the Quinyx WFM hierarchy is still the master in terms of how and where a client creates users, defines groups, roles, and establishes the permissions schema for their organization.
From an Employee Hub perspective, there are some technical limitations of the WFM organization hierarchy, which, if you're coming from only using Employee Hub, might make it unsuitable for clients wishing to use both Quinyx WFM and Employee Hub.
As an example, EH gives users the option to distribute resources by ‘group type’, but there is no such concept in WFM etc.
And so these Collaboration Groups are - again - only to be utilized for all-in-one (AIO) customers as a way to create more complex hierarchical setups than what the Quinyx WFM org. solution currently support.
