Role-Based Permissions (RBP) is the security model used to manage access within the SAP SuccessFactors HCM Suite. It allows you to control which applications and data employees can view or edit. As a suite-wide authorization model, RBP applies to most SAP SuccessFactors products.
Employee Central Permissions
The Role-Based Permissions (RBP) framework is extensive and covers all SAP SuccessFactors solutions. This course focuses specifically on the common permissions used in SAP SuccessFactors Employee Central. To review general RBP concepts, please refer to the Exploring SAP SuccessFactors Platform learning journey.
Note
In this lesson, we will cover the following permissions:
- Employee Central Effective-Dated Entities
- Employee Data
- Employee Central Import Entities
- Manage Foundation Object Types
- Manage Foundation Objects
- MDF Foundation Objects
When granting permissions, you must consider multiple levels of access. This includes category, card, and field-level permissions.
The latest People Profile categories are also controlled in RBP. To view data in a category, users need permission to access the category and permission to access at least one card in the category.
- If users do not have access to a category, the category and everything inside it are hidden, even if they have card or field permissions.
- If users have access to a category but not to any of its cards, the category appears empty.
- If users have access to a category and to one or more cards, only those permitted cards and fields are shown.
Employee Central Effective-Dated Entities
The Employee Central Effective-Dated Entities permission provides access to elements and fields that track historical and future changes. This permission becomes available once the succession data models are uploaded during the initial implementation. SAP SuccessFactors Employee Central includes several standard effective-dated entities, including the following:
- Personal Information (personalInfo)
- Addresses (homeAddress)
- Dependents (personRelationshipInfo)
- Job Information (jobInfo)
- Compensation Information (compInfo)
- Job Relationships (jobRelationsInfo)
Block Actions Permissions
Block actions control user access levels for effective-dated cards and their associated buttons.

| Permissions | Description |
|---|---|
| (1) View Current | Makes the card visible in the profile category |
| (2) View History | Makes the clock icon appear and allows access to the history window |
| (3) Edit/Insert | Allows the use of the "Create" button in the history window |
| (4) Correct | Allows the use of the "Correct" button in the history window |
| (5) Delete | Allows the use of the "Delete" button in the history window |
Note
The create, correct, and delete actions in history do not trigger workflows, even if workflow derivation rules are implemented.
Edit (Pencil) Link Permission
The Edit Link controls whether the Edit (pencil icon) function is available on the card for the users. The only level of access that matters is the Edit/Insert. The rest are ignored.

The permission allows the users to open and edit the card to initiate transactions in People Profile.
You can also perform the edit action from the Actions Menu in People Profile. Just add the Update Employment Records permission as seen on the screenshot.

Field-Level Permissions

Field-level permissions control each field’s specific ability to be maintained. Each field can be controlled on its level of visibility and editability.
| Permission Level | Description |
|---|---|
| View Current | View current value of the field |
| View History | View historical values of the field if accessed in the History view of the block |
| Edit/Insert | Update the value of the field using "Create" in the History view of the card |
| Correct | Update the value of the field using the "Correct" in the History view |
| Delete | Not applicable to individual fields, entire records are deleted |
Employee Data Permissions
The permissions for non effective-dated entities are in a separate category, the Employee Data permissions.
Use the interaction below to learn the relevant Employee Data permissions used in Employee Central.
Employee Central Import Entities
This allows you to perform or restrict imports to Person and Employment objects and ensure imports are performed for the users within the target population of the logged-in user.
Manage Foundation Object Types
These are admin permissions that define the actions allowed for XML-based corporate data found in Manage Organization, Pay, and Job Structures. This permission is only available when the Corporate Data models have been initially uploaded during implementation.
Manage Foundation Objects
This enables the admin permissions that set the actions for importing foundation data, translations, and corporate data models.
MDF Foundation Objects
This sets the admin permissions that define the actions allowed for MDF-based corporate data.
