SAP Knowledge Base Article - Public

2146691 - RBP Module Coverage


RBP controls the access to most modules. The page permissions (that is, what data and functionality appears on the page) are partly controlled by RBP and partly controlled by other mechanisms, depending on the requirements of the modules. For some modules it is mandatory to use RBP. If several modules are in use and RBP is mandatory for one, you must configure RBP for all modules. You cannot mix RBP with the old permission framework.


If multiple instances are used we recommend using either RBP or the old permission framework on all instances.



The following graphic provides an overview of where RBP is used and where other mechanisms are in place. In the table below, you will find details on RBP coverage for each module.

RBP Coverage.PNG



Is it covered in RBP?

Controlled by RBP

Not controlled by RBP

Admin Tools


Everything within Admin Tools




  • Access to Calibration tab
  • Access to employees whom the user will see within Calibration 

Within Calibration, specific permissions grant read, write, edit, and finalize authorization for individual sessions.



Access to Careers tab and sub-tabs

Once the Career tabs and sub-tabs are permissioned under RBP, all sub tabs, postings, and so on, are visible. There are no deeper permissions available by RBP, the module, or xml.



User Permissions

  • Access to development tab
  • Access to career worksheet tab
  • Access to development plan template, career worksheet template, learning activity template
  • Access to Career Development Plan (CDP) Learning Activity Mass Add  
  • Access to development admin permission

Administrator Permissions

  • Access to Import Development Goals 
  • Access to Manage Learning Activity Catalogs
  • Access to Manage Learning Activity to Competency Mappings
  • Access to Manage Career Path
  • Access to Manage User Relationship for Learning Administrator and Educational Representative
  • Access to Manage Import Learning Activity by Web Service  

Permissions within Goal Plans, such as creating, editing, or cascading goals.

Company Info



Company Info menu is visible for everybody

Compensation/Variable Pay


  • Access to tabs and sub tabs within Compensation and Variable Pay
  • Permission to read and edit executive reviews
  • Permission within compensation forms
  • RBP does not apply to compensation plan level

Employee Central

RBP is mandatory

Access to EC and page permissions


Employee Profile


  • Access to Employee Profile (Live Profile Access)
  • Field level permissions to employee data




  • Access to Goal tab
  • Access to Allow Role to Create Group Goal (Group Goal 2.0)
  • Access to Allow Role to Assign Add Group Goal 2.0 to other Users
  • Access to Execution Map under Goal Execution
  • Access to Meeting Agenda under Goal Execution
  • Access to Status Report under Goal Execution
  • Access to Goal Plan(s)
  • Administrator permissions
  • Access to Import Goals 
  • Access to Import/Export Goals library 
  • Access to Manage Configuration of Goal Execution 

Permissions within Goal Plans, such as creating, editing, or cascading goals. However, for/to whom the employee can create, edit, cascade goals is controlled by the target population of the "Access to Goal Plans" permission item.



Home Page



  • Everyone sees the home page
  • Items visible on the Home Page are based on user’s permissions to those individual items/portlets
  • Administrators can enable or disable out-of-the-box portlets. When an out-of-the-box portlet is enabled, it will appear for all users. Modules control what content will appear in the portlet, so this can be a mix of RBP and non-RBP controls depending on the portlet. Administrators can add custom portlets and use dynamic groups (outside of RBP) to control who sees the custom portlets.



Access to Jam

Permissions within Jam

Job Profile Builder 2.0

RBP is mandatory

Access to Job Profile Builder and page permissions




Access to Learning menu

Permissions within the Learning module

MDF Position Management

RBP is mandatory

Access to MDF Position Management and page permissions




RBP is mandatory

  • For corporate users (that is HR and admins) in 1308 we will pass a group assignment that is created in RBP to onboarding admin. The onboarding admin then reads the group assignment and determines what content in the compliance tool should be exposed to the user.
  • Page permissions are a mixture of manager discretion and RBP. A manager gives new hires access to some information before their first day on the job. That includes looking at the profiles of their future team, buddies (mentors), and other people the manager recommends. However, RBP controls what data from the selected users the new hires can see. The new hires will not be able to see other people or the whole org of the corporation.

Hiring managers automatically gain access to onboarding (it appears in the main menu navigation) if one of their team members is actively being onboarded. This is not through RBP.




  • Access to Performance tab
  • Access to Create Forms

Permissions within forms (that is, required fields)



  • All features under Recruiting Permissions in Permission Settings
  • Administrator permissions (allows the admin to give the user access to certain links in Admin Tools)
  • The permission to create forms and the reports permissions are shared with the other modules – both are covered by RBP. 
  • Recruiting tab
  • Any user with access to a requisition for any reason has irrevocable access to the Recruiting tab.
  • Form template permission grants access, but there are also other ways employees may have access. For example, if a form is routed to them, if they are added as an operator to the form, or if certain feature permissions are granted to them

Reports Menu – Dashboards & Analytics


Controlled by RBP:

  • Access to specific dashboards and reports under Analytics
  • Access to target populations the user will be able to report on

Limited RBP control:

  • For ad hoc reports, the access to specific reporting sub domain schemas is controlled via RBP, but access to specific reports is done via “sharing”, which is not controlled by RBP. Sharing is user based. Though if, for example an RCM report is shared with a user that does not have RCM sub domain schema access, then it will not run.

Cell and field level permissions are not adhered to in ad hoc reports or dashboards, except for Employee Profile (opt-in).

Reports Menu – Workforce Analytics


Access to Workforce Analytics is controlled via the “Inform Reports” permission in RBP.


Permission controls within WFA. There is a concept of RBP in WFA but it is a separate RBP permission page within WFA app and does not link through to BizX RBP.



  • Access to Succession tab
  • Access to Succession Org Chart, Succession Planning, Matrix Grid (9-box) and Talent Search
  • Access to all Succession admin functions, including Succession Management, Position Set-up, Matrix Grid admin tools, Sync Position Model
  • Beyond access to specific succession features, RBP also controls "target population" for users – which users and what details can be viewed by the logged in user. These include:
  • Position details of users, which are controlled by position specific permission
  • Field level details of positions
  • Ability to view users on search results
  • Ability to view users on matrix grid reports
  • Ability to view users on succession org chart and lineage chart

Configuration of the 9 Box and Succession Org Chart. For example, if a client opts to include gender or minority on these as a configuration decision, this will not honor RBP settings that may have excluded visibility of same.

The same is true for talent search. RBP limits who shows up, but does not respect field level permissions set up in RBP.


RBP , KBA , LOD-SF-PLT-RBP , Role Based Permissions , How To


SAP SuccessFactors HCM Core all versions