Study guide

8.4 Employee and Manager Self-Service Permissions

SAP Certified - SAP SuccessFactors Employee Central Core and Position Management C_THR81

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: C_THR81 Exam and SAP SuccessFactors Platform Foundations

1.1 C_THR81 Exam Format, Logistics, and Preparation Plan 1.2 SAP SuccessFactors Suite, Platform Capabilities, and Employee Central Core 1.3 Instances, Provisioning, and Company Settings 1.4 Administrator Types, Super Admin Access, and Admin Center Navigation 1.5 Release Management, Upgrade Center, Release Center, and Consultant Resources

2 Chapter 2: Security, Proxy, and System Administration

2.1 Role-Based Permissions: Groups, Roles, and Target Populations 2.2 RBP Troubleshooting, Reports, and Governance Best Practices 2.3 Proxy Management, Company System and Logo Settings, and Platform Feature Settings 2.4 Admin Alerts, Check Tool, and System Access Settings 2.5 Scheduled Job Manager, Provisioning Job Scheduler, and Execution Manager

3 Chapter 3: User Experience Configuration

3.1 People Search, Action Search, Custom Navigation, Org Chart, and Built-In Support 3.2 Home Page Configuration and Mobile Settings 3.3 E-mail Notifications, Themes, and Company Logo 3.4 Text Replacement, Manage Languages, and Translations

4 Chapter 4: People Profile, Picklists, User Data, and the Metadata Framework

4.1 Latest People Profile, Categories, Cards, and Custom MDF Cards 4.2 Manage Business Configuration and Succession Data Model XML Fundamentals 4.3 Picklist Center, Cascading Picklists, and the Employee Central Master Picklist 4.4 User Data File, Employee Import, and User Management Tools 4.5 Metadata Framework Enablement and Object Definition Settings 4.6 MDF Fields, Associations, Search, and Security

5 Chapter 5: Business Rules

5.1 Rules Engine Fundamentals: Scenarios, Base Objects, MDF Rule Events, and the Execution Log 5.2 Employee Central Rule Events, Rule Scenarios, and Model Base Objects 5.3 Propagation Rules and Hire/Rehire Rules 5.4 Cross-Entity Rules, Rule Context, and Rule Design Practices

6 Chapter 6: Foundation Objects and Corporate Data Models

6.1 The Four Employee Central Data Models, DTDs, and Upload Sequence 6.2 Foundation Objects: Organization, Pay, and Job Structures 6.3 Configuring Legacy and MDF Foundation Object Definitions 6.4 Foundation Object Associations and Field Criteria 6.5 Country-Specific Fields for Foundation Objects

7 Chapter 7: Employee Data Structures and Permissions

7.1 Person and Employment Objects, Effective Dating, and Employee Identifiers 7.2 Configuring the Succession Data Model with BCUI and XML 7.3 Country-Specific Succession Data Model: National ID, Addresses, Global Information, and Job Data 7.4 HRIS Synchronization and Sync Mappings 7.5 Employee Central Permissions for Administrators

8 Chapter 8: Employee Transactions and Data Maintenance

8.1 Hire, Rehire, Termination, and No-Show Transactions 8.2 Importing New Employees and Updating Employee Data by Import 8.3 Mass Data Management for Job Information, Job Relationships, and Positions 8.4 Employee and Manager Self-Service Permissions

9 Chapter 9: Workflows, Alerts, and Event Reasons

9.1 Workflow Configuration, Participants, Dynamic Roles, and Dynamic Groups 9.2 Managing Workflows: Approvals, Delegation, Reminders, Escalation, and Auto-Approval 9.3 Employee Central Alerts and Notifications 9.4 Events, Event Reasons, and Event Reason Derivation 9.5 Workflow Derivation Rules and How They Work with Event Reason Derivation

10 Chapter 10: Optional Employee Central Configurations

10.1 Employee Central Quick Actions and Internal Job History 10.2 Custom Hire Templates, the Diagnostic Tool, and Joule in Employee Central

11 Chapter 11: Position Management Setup

11.1 Position Management Overview: Positions, Jobs, and the Leading Hierarchy 11.2 Enabling Position Management and Setting Role-Based Permissions 11.3 Navigating and Configuring the Position Organization Chart 11.4 Configuring the Position Object 11.5 Position Management Settings 11.6 Creating, Maintaining, Importing, and Mass-Changing Positions

12 Chapter 12: Position Management in the Employee Lifecycle

12.1 Position Fields in Job Information and Hiring Employees to Positions 12.2 Maintaining Incumbents: Transfers, Reclassification, Global Assignments, and Right to Return 12.3 Manager Self-Service with My Team Positions and Quick Actions for Positions 12.4 Terminations with Position Management and Position Workflows

13 Chapter 13: Position Management Rules, Integrations, and Company Structure

13.1 Position Management Rule Scenarios and Rules for Position Data Entry 13.2 Synchronization Rules and Mass Change Runs for Positions 13.3 Position Code Generation, Position Workflows, Right to Return Setup, and Rule Functions 13.4 Integrating Position Management with Recruiting and Succession 13.5 Building the Company Structure Overview

8.4 Employee and Manager Self-Service Permissions

Key Takeaways Explain This Topic AI

Employee Self-Service uses a permission role granted to all employees with the target population set to the granted users themselves.

Typical ESS changes are marital status or name, home address, dependents, and emergency contacts.

Manager Self-Service lets managers start transactions for their direct reports, usually with approval workflows.

Granting Edit Link Edit/Insert without block-level Edit/Insert lets users edit the current record but not create history records.

Access to inactive employments uses the User Status field (Inactive) in the Grant Access To step, for Employee access only.

Last updated: September 2026

8.4 Employee and Manager Self-Service Permissions

Quick Answer: Employee Self-Service (ESS) lets employees maintain their own personal data. It is granted with a role whose target population is the granted users themselves . Manager Self-Service (MSS) lets managers start job, pay, and organizational transactions for their team, usually with workflows . Fine-grained block and field permissions decide whether users can edit current data, create history records, or see specific fields.

Why Self-Service

SAP's rationale: employees update their personal information, and managers handle employment, compensation, and organizational changes such as new positions or promotions. HR Operations reviews and approves changes and serves as a backup when employees and managers cannot make updates. RBP ensures that each group changes only what is relevant, and approval workflows can act as guardrails even when a user has permission to change data.

Employee Self-Service

An ESS grant has three parts. The granted population is all employees , the role is the permission, for example to view and edit the phone number, and the target population is the employees themselves . Typical ESS options:

  • update marital status or name
  • update home address
  • update dependents
  • update emergency contacts

Employees reach their data through Home > My Employee File , or View My Profile in Quick Actions.

Worked Example: Tuning the ESS Role

THR81 first proxies as an employee (Larry Ye) to test the current state, then changes the Employee Self-Service role:

  • Permission category Section Field Permission
  • Employee Data HR Information National ID Card View and Edit
  • Employee Central Effective Dated Entities Personal Information All fields View Current and View History
  • Employee Central Effective Dated Entities Personal Information Edit Link Edit/Insert

Result: the employee can now add National ID information. In Personal Information, the employee can no longer create a historical record but can edit the current information through the pencil icon, because only the Edit Link has Edit/Insert.

Access to Inactive Employments

Active employees can see their inactive employments through self-service. Examples are rehired employees viewing past employments, and employees back from a global assignment viewing the host assignment.

In the role's Grant Access To step, use the User Status field and choose Inactive .

User Status is available only for the Employee access user type.

Employees need at least one active employment and must be able to log in.

They must belong to the relevant permission groups , otherwise the Inactive option does not work.

SAP recommends separate permission roles for inactive users , for example view but not edit.

Manager Self-Service

MSS lets managers start transactions for their direct reports , typically followed by workflows. Common MSS transactions:

  • update Job Information
  • update salary information
  • initiate transfers

The Actions button (Take Action), in the employee's profile or quick card, is the usual starting point, for example Change Job and Compensation Info . Managers can also start EC Quick Actions from Manage My Team (Section 10.1).

Worked Example: Restricting the Manager Role

ACE's requirements:

Managers can start Job Information updates except Supervisor and Pay Grade .

Managers can start Compensation Information updates except Pay Type and Pay Group .

Managers must not Create (Insert New Record), Correct, or Delete historical records.

Managers can start Job Relationship updates.

  • Category Section Fields Permission
  • EC Effective Dated Entities Job Information all fields View Current and View History

EC Effective Dated Entities Job Information all fields except Job Information Actions, Supervisor, Pay Grade Edit/Insert

EC Effective Dated Entities Compensation Information all fields View Current and View History

EC Effective Dated Entities Compensation Information all fields except Compensation Information Actions, Pay Type, Pay Group Edit/Insert

  • EC Effective Dated Entities Job Relationships all fields View Current and View History
  • EC Effective Dated Entities Job Relationships all fields except Job Relationships Actions Edit/Insert

Because the block-level Actions rows have no Edit/Insert, Correct, or Delete, the History window gives managers no Create, Correct, or Delete buttons. They can still edit the current information through the Edit Link or Take Action, which runs event reason derivation and workflows (Chapter 9). Test by proxying as the manager (Carla Grant) and opening a direct report's Job Details, Job Relationships, and Compensation History.

Why History Access Stays with HR

Changes made from History (Insert New Record, Correct, Delete) do not trigger workflows , even when workflow derivation rules exist. With event reason derivation active, History inserts require choosing the event and reason manually, and the save takes effect immediately. SAP calls this an HR Edit and reserves it for administrators. Managers and employees should work through the pencil icon or Take Action, which apply derivation rules and approvals.

Quick Reference

  • Requirement Configuration
  • Employees edit their own address ESS role with the Addresses permission, target The Granted Users Themselves
  • Employees edit the current record but not history Edit Link Edit/Insert only; no block-level Edit/Insert

Managers change job data for their team MSS role with EC Effective Dated Entities for Job Information, granted for direct reports

Rehired employees view old employment data Role with User Status = Inactive (Employee access user type)

Employees terminate their own employment Permission with target population The Granted Users Themselves (Section 8.1)