Manage HR Groups Best Practice

[Kohei Tominaga1]

Hello,

My situation:

I am a HR admin and have enough role to manage groups from Manage HR Group module.

But it is not permitted to change anything in Prod. Changes need to be done in a non-Prod and migrate it to Prod by XML to have the same configuration and data so that the non-Prod can be best instance for troubleshooting.

So, I need to raise a request to Dev team for this purpose.

Question:

What is the best practice for managing HR groups?

- HR Admin to make change in both instance manually?

- HR Admin to make change in non-Prod and request IT Admin to migrate?
- Any other way to give permission to migrate for HR Admin?

[John Zhang1]

Hi Kohei

As best of managing HR Group, you (HR admin) can manage HR groups via Manage HR Groups under Manage Roles.   We usually export group record (sys_user_group), group role record (sys_group_has_role) or group member(sys_user_grmember) record as xml files and import each fille to sub production instance (DEV-->TEST-->Production).  As HR admin, you can perform this action. 

[Kohei Tominaga1]

In my PDI, HR Admin cannot export xml file though it has HR admin role.......

[Suzanne H]

@Kohei Tominaga1 

It looks like you need the user_admin role.

user_admin

Can administer users, groups, locations, and companies.

[Markus Nilsson · Accepted solution]

Hi @Kohei Tominaga1,
The whole point with HR Admin and their access to Manage HR Groups are for those to actually managing the HR groups without involving IT. Biggest argument in my point of view is that sometimes adding/removing user to HR group and with that add or restricted access needs to be quick from a legal/security perspective and should be managed by HR Admins.
Don't agree that the members of the groups needs to look exactly the same in all instance either. Could also be a question of access rights.
Best of luck to you!

/Markus

[Kass3m]

Can this be automated as a catalog item by a user and fulfilled?