Study guide
1.3 Instances, Provisioning, and Company Settings
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
1.3 Instances, Provisioning, and Company Settings
Key Takeaways Explain This Topic AI
The instance is the customer-facing front end; users log in with a company ID, username, and password.
Provisioning is the back end for enabling features and modules, creating administrator accounts, uploading templates, and enabling language packs.
Customers never access Provisioning; only trained SAP employees and partners receive Provisioning accounts.
Admins view, grant, and remove Provisioning access with the Manage Provisioning Access tool, separately in each instance.
Changes in Provisioning Company Settings are saved with Save Feature and confirmed by entering the company ID.
Last updated: September 2026
1.3 Instances, Provisioning, and Company Settings
Quick Answer: An instance is the front end of SAP SuccessFactors, identified by a Company ID . Provisioning is the back end, where implementers switch on features and purchased modules, create administrator accounts, upload templates, and enable language packs. Customers never use Provisioning. Customer administrators control who may reach Provisioning for their instance with Manage Provisioning Access in Admin Center.
The Instance
An instance is the customer-facing view of the SAP SuccessFactors platform. Each company has a URL and a Company ID . Each user signs in with the Company ID, a username , and a password . Consultants, administrators, and end users see the same interface. What differs is which tools each person's configuration and permissions expose. The login page offers a question-mark icon that links to a support FAQ for account and login problems.
During implementation, consultants use the Admin Center in the instance to set up basic features. Examples include the look and feel (colors, logo, home page), e-mail notification templates, and text replacement. After go-live, customer administrators use the Admin Center to adjust those features and to run processes: launching forms, importing and updating users, and resetting passwords.
Provisioning
Provisioning is the key configuration tool SAP uses to control many aspects of an instance. It is effectively the system's back end. Implementers, consultants, and support representatives use it to:
- modify company settings , such as enabling new features
- turn purchased modules on or off
- create administrator accounts
- download and upload templates that contain custom configuration
- enable language packs
After logging in, a consultant sees the list of company instances they may access. They select the company name and then Company Settings . The page is long, so SAP suggests using the browser search (Ctrl + F). After changing a section, choose Save Feature . Provisioning then asks for the company ID to confirm. The page has several Save buttons but only one Save Feature button per section.
Instance Versus Provisioning
- Instance Provisioning
- Who has access Implementers, administrators, end users Implementers, SAP SuccessFactors Customer Support
Typical uses Customize tiles, manage permissions, oversee user information, generate reports, run processes and cycles Configure system features, enable purchased modules, upload templates
For example, deciding who can access Compensation is done in the instance through RBP. Turning on the Compensation module is done in Provisioning.
Who Gets Provisioning Access
Provisioning access is strictly controlled. Only SAP employees and partners who have completed the required training receive a Provisioning user account. THR80 also notes that an SAP SuccessFactors certification is required before implementation consultants gain Provisioning access to customer instances.
Customers stay in control through Manage Provisioning Access in Admin Center, which requires the Manage Provisioning Access permission. With it, an administrator can:
view the users who have Provisioning access to the instance, using filters
approve (add) a Provisioning user. Approval alone does not grant access; the user still submits an internal access request in which SAP verifies training and other requirements
remove Provisioning access from one or more users
Provisioning access is instance-specific. A customer with Development, Test, and Production instances must manage access separately in each one. A consultant may have Test access long before Production access is approved.
Creating an Administrator Account in Provisioning
Provisioning can create new administrator accounts. SAP notes that backup admin accounts help if the regular administrator account is locked out. In Company Settings, the consultant scrolls to the admin section (Ctrl + F for "Admin Username") and completes:
- admin username and password (the two must differ, and the username must be unique in the instance)
- first name, last name, and e-mail
the confirmation checkbox that the customer has approved Super Admin user account creation , and the customer contact's e-mail address
Then choose Create Admin and confirm with the company ID. If the username already exists, Provisioning shows an invalid-username error. If the instance uses the single recipient e-mail feature, creating a Super Admin fails with an exception that the e-mail could not be sent. SAP's workaround is to disable that feature temporarily.
Settings Moving Out of Provisioning
SAP is moving settings from Provisioning into Admin Center so customer administrators control more of their own system. Before migrating a setting, SAP checks four things:
Is the action already in Admin Center? If so, SAP removes the Provisioning copy to keep one source of truth.
Is the switch meaningful, or an edge case that should be removed or kept SAP-only?
Does the experience need improving before it moves?
Does the switch control a purchase? License-controlling switches stay out of Admin Center.
You will see this pattern throughout Employee Central. Position Management , for example, can be enabled either in Provisioning Company Settings or in Admin Center under Manage Employee Central Settings . In contrast, importing the Succession Data Model XML still requires Provisioning.