on 2022 Oct 28 9:33 PM
Hello Team,
SuccessFactors understands the Word Manager as a position that has subordinates. So every time we choose a permission role with the option Manager, we are referring those people who have people below the in the Orch Chart. Here is when the problem comes with my client because, when reviewing the permissions for every group of permissions, they told me that they consider a "Manager" the person in green in the photo below, but they do not consider a Manager, but a Team Leader, the person in Yellow.

So then i cannot just grant the same permissions to all "Managers" in the Add permission roles screen

I would like to know if there is any other way to differentiate these people than just putting all their positions in one group as is a Huge company with branches worlwide. Is there any other way to differentiate this with standard options?
Regards
Request clarification before answering.
RBP looks at Managers as anyone who has at least one direct report. That's the beauty of it - minimizes manual work and monitoring.
It is dynamic when the reporting line is on the record. There is no way to create the different permissions within the same role in RBP setup.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, but that is exactly the problem here, they don´t want every person with a direct report to be a Manager, they call that Team lead and want different permissions for team lead and Manager, Team Lead shall not see Compensation info of the report and Manager Can. So if i have to do a group to select those Manager, the problem is that in the roles screen i cannot choose to view the salary of the reports only, as i choose a group not a role "Manager"
Hope i am explaining myself
regards
I would create permission groups using another field for granting the permissions. For example, use Manager role for all permissions pertaining to both Supervisors and Managers. Then, use Job Code, or Job Family or another custom field to create a Permission Group for those permissions that are only for Managers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello!
I think i would do that. but meanwhile i was creating the role i realized that in the Manage Permission Roles you can only choose Target population " On Whom" you have the permissions, ig you choose Grant role to "Managers" then system lets you choose Direct Reports and levels

But if you choose a Permission Group, you cannot choose reports so if i let this group see compensation info, then they will see also their superior´s compensation info which is not good. Do you know a way to let them only see things over their subordinates but not superiors? The filters are things like Department, but it still woule let you see your superior´s compensation

Any idea?
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
thanks!
the issue here is that i can do that for what they call "team leaders· (employees with subordinates in the org chart)
but what they call Managers, is only the superior person of a group, then with that employees i cannot use the Manager Grant Role To option
They don´t want the Team Leaders to see compensation info but they want the Managers to see the compensation
Hope i have explained myself
Regards
You should create a permission group to identify the real "managers" and exclude the "team leaders". To do that you can use any of your attributes (in example the pay grade). Then, you can assign the role just to managers in this group as in my scrennshot so just to your desidered granted population.
The option might be to use the job classification field "Job Level" and have your supervisors identified as well as upper managers and then create permission roles on the job level field with different permissions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi!
These are certainly good ideas, in case there is no standard solution for choosing incumbents.
The problem I still have is that if I choose a group to give role permissions instead of selecting "manager" I will not be able to say that they can only see the subordinates, they can also see the data of their superiors, can I filter that somehow by choosing groups? The filters I see are Department, Company etc but I understand that they all refer to the whole company including superiors.
Thanks,
Regards
Hi Jasper,
yes the option of making a group with all of them is possible, but cumbersome because i have to select one by one all the positions of these people or their job titles as you say.
I guess manager has nothing to do with position but at the same time it coincides with the person in the higher level position and the supervisor in the job info, if the system and the data are correctly synchronized, they should be the same person, right? even if there is some difference in the technical technology. Am i correct?
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I reckon you may not understand the meaning of that manager option 100% correctly. It takes data from the manager field in the User Data File (hence doesn't per se care about position).
Manager unfortunately is not a field that can be affected and I don't recommend manipulating the user data file for this either (that will be quite the burden). You may consider maintaining custom manager or matrix manager, but that may be a bit cumbersome in terms of work (as you do that per employee).
The only alternative is using a permission group in which you have steady criteria to identify the (back-up) managers (i.e. job title/job code or something like that), otherwise the custom/matrix manager would really be the 'best' option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 7 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.