Forum Discussion
User Role Permission based on attribute hierarchy
Hi!
I understand that we can provide users with access based on attribute hierarchy.
Using department hierarchy (Divisons > Departments > Sub-Department) as an example and I would like to provide my department heads (new user role created) with access to the respective departments they are tagged to, should I be providing them with
(a) "custom" access and do it manually for each, or
(b) select the department hierarchy to the "department" level- will the departmentheads be given the access to data of all departments or will they be only given access to the department they are tagged to in the attribute report?
Thanks alot!
5 Replies
- alanderfield
Microsoft
Hello Jing_Ying_Choon,
If the attribute that is selected accurately aligns the department heads to their department, then you can use the attribute permission that is setup at the user role level. If this does not show the correct relationship for each user, you can work with the customer to update the attributes as they are received on the user file.
In your example, if a department head is aligned to a specific attribute "department hierarchy", then they would see data only where they are listed as the department head and not across the entire organization. If for some reason the department hierarchy does not show the correct alignment and the customer is unable to update the hierarchy from their HRIS, then you can look into creating custom access for each user. I would try to avoid this as you would have to maintain this as the hierarchy changes.
I hope this helps and let us know if you have any further questions.
- Jing_Ying_ChoonCopper Contributor
Hi alanderfield, thanks so much for your help! Sorry but I seem to have lost you a little there.
Please see below if my understanding of your explantation is correct-
Using Employee A as an employee - he works in the HR division (dept hierarchy level 1) and Recruitment department (dept hierarchy level 2)
Let's say I create a new role with access using 'department hierarchy' and I add him in...
(a) Will be receive data based on his level 1 department hierarchy tag (aka the HR data)
or
(b) he will not receive any data in this case (can you then explain what does providing access with "hierarchy" actually do?)
So in the case where I want employee A to receive the data to the entire HR division, then what I should do is the following-
step 1: create an additional "Department head" attribute and mark him as "Yes"
step 2: create a custom user role and include all employees marked yes under "Department head" and in the "HR" division
Hope this is clear! Thanks again!- Jing_Ying_ChoonCopper Contributorhi alanderfield, appreicate your reply, thanks!