2087940 - User Roles & Role Usage in Forms & Routing Maps within SuccessFactors Modules

• This KB article provides information on role names commonly used in form templates, route maps, goal plan templates, etc
• As well as information on what roles are used in Recruiting, and what roles are used in Job Description Manager (JDM 1.0)

• SAP SuccessFactors HXM Suite
• SAP SuccessFactors Career Development Plan
• SAP SuccessFactors Recruiting
• SAP SuccessFactors Employee Profile
• SAP SuccessFactors Performance & Goals Management

General Role Codes used in SuccessFactors

• *(asterisk) = everyone
• cascader = person who is cascading a goal

E = employee/owner
EA = employee's second manager
EB = employee's direct report of second manager
EC = employee's custom manager
ED = employee's direct report
EDD = employee's second level direct report
EDDD = employee's third level direct report
ED+ = any level of employee's direct reports below in the reporting hierarchy
EH = employee's HR representative
EHM = employee's HR representative's manager
EHM+ = employee's HR representative's manager and levels above in the reporting hierarchy
EM = employee's manager
EMD = employee's manager's direct reports, i.e. coworkers/peers (only supported for TGM and CDP)
EMH = employee's manager's HR representative
EMM = employee's second level manager (manager's manager)
EMMM = employee's third level manager
EM+ = employee's manager and levels above in the reporting hierarchy
EP = all employee's matrix managers
ER = direct report of custom manager
ET = Calibration Facilitator: The relationship only applies to facilitators (not to owner or participant).
EX = employee's matrix manager
EY = direct report of matrix manager
F = form reviewer (goal access restricted through a form only)
F = F is also used in JDM and means "Job Family Expert" when applied in JDM
G = hiring manager in recruiting
GM = hiring manager's manager
J = super user (recruiting)
O = originator when relative to JDM or Performance
O = For Employee Central Users O can also refer to Other Role - A role to be used in the workflow only. Cannot be pre-defined. Is selected by using the “search” function.
OM = originator's manager
OP = originator parent (for use when aligning private goals)
OC = originator child (for use when aligning private goals)
R = recruiter in recruiting
S = sourcer in recruiting
T = recruiting Co-ordinator
U = specific user (requires username) - workflow only
V = approver

Step Roles Available for a Route Map

C / EM / E = collaborative step between employee and their manager
C / E / EM / EP = collaborative step among employee, their manager and all employee's matrix managers
E = employee
EH = employee's HR Rep.
EHM = employee's HR Rep's manager
EM = employee's manager
EP = all employee's matrix managers
EX = employee's first matrix manager
G = Hiring Manager in Recruiting
I / F = Job Family Expert (used by Health Care)
I / EM / E = iteration step between employee and their manager
I / E / EM / EP = iteration step among employee, their manager and all employee's matrix managers
O = Originator (only supported in PMv11, not above - PMU-1254 )
OM = Originator's manager (only supported in PMv11, not above - PMU-1254 )
R = Recruiter in Recruiting
S = Sourcer in Recruiting
T = Primary Coordinator in Recruiting
U = specific user

Roles for Recruiting - Used for Permissions

J = Super User (recruiting)
R = Recruiter in Recruiting
T = Primary Coordinator in Recruiting
G = Hiring Manager in Recruiting
S = Sourcer in Recruiting
O = Originator
Q = vpOFStaffingName
W = Second Recruiter in Recruiting

Roles Exclusive to GM

cascader = person who is cascading a goal

Roles Exclusively for JDM

F = Job Family Expert
O = Originator

Note: JDM also uses all other standard roles for forms

• The role-name element in action-permission, field-permission and button-permission elements specifies a role
• The following role-name values are allowed:

* = all users
F = form reviewer (applicable on form views only)
E = employee/owner
Exxx = employee/owner relative role (see below)

Employee/Owner Relative Roles

"E" may be followed by any combination of "M", "D", and "H" with optional modifiers "+", "*", "?" to specify complex employee relative roles.

M = employee's manager
D = employee's direct report
H = employee's HR representative

On the below scenario, "X" is one of "M", "D", or "H", as defined above:

• X? = X is optional (zero or one of X)
• X* = zero or more of X
• X+ = one or more of X

As an example, here are a few common roles:

EM = employee's manager
EX = employee's matrix manager
EA = employee's 2nd manager
ED = employee's direct report
EB = employee 2nd manager's direct report
EH = employee's HR rep
EM+ = employee's manager, manager's manager, etc...
ED+ = employee's direct and indirect reports
EMM = employee's manager's manager (only)
EMD = employee's manager's direct reports (coworkers) including the employee

Note: The time it takes to resolve a role is relative to it's length. The modifiers can drastically increase the time to resolve an access right. Although using more than one modifier in a role name is supported, it can seriously hinder performance.

For a visual demonstration of roles & relationships, review the document attached to this article.

sf, success factors, bizx, biz x, administrative, domain, permission access to role employee, CDP, PMGM, PM, GM, RCM, EP, JDMv1.0, v1.0 , KBA , sf bizx system/platform , sf bizx performance management , sf bizx compensation , LOD-SF-PM , Performance Management , LOD-SF-CDP , Career Development Planning , LOD-SF-GM , Goal Management , How To