Video summary

SAP SuccessFactors Tutorial | SAP SuccessFactors course | SAP SuccessFactors Training | CyberBrainer

Main summary

Key takeaways

Educational

Main ideas & lessons from the tutorial (Settings in SAP SuccessFactors)

1) End-user tabs vs. consultant/admin configuration

  • The left-side End User tabs are what users interact with.
  • Some tabs/actions are driven by hidden background configurations.
  • Consultants must know where those configurations live to troubleshoot user issues—i.e., trace a user problem in a tab back to the correct admin/consultant setting.

2) Password tab (password expiration + password policy management)

What users experience

  • Users receive notifications that their password expires (described as every 60 days in the video).
  • Users reset passwords themselves.
  • Reset must comply with the active password policy.

What consultants/admins must manage

  • Password policies define rules such as:
    • required character count/length
    • whether it is case-sensitive
    • whether capital letters are required
    • whether special characters are required
  • Password policies should be updated by the customer/admin at least yearly once (not frequently).
  • After updating the policy:
    • Admin/consultant must send internal communication email(s) to users that the policy changed.
    • Users must follow the new policy when they receive the next “reset password” notification.

Environment context (who needs to reset/update policies)

  • Different environments exist:
    • Development / Preview: used by consultants for configuration/testing.
    • Production (Live): used by actual employees.
  • The video implies:
    • Consultants configure in dev/preview, then deploy to production.
    • Key users / live employees also require policy updates communicated so they reset using the current rules.

3) Start page tab (default landing page)

Goal

  • Control where a user is redirected after login.

Examples shown

  • If Start page = Home, login redirects to Home.
  • If Start page/subtab is set to a specific module (e.g., Compensation), login redirects directly there.

Subtab behavior

  • Tabs can contain subtabs (e.g., Compensation sub-options like):
    • Compensation Review
    • Budget Approval
    • Budget Assignment, etc. (depending on what is selected)
  • Selecting different subtabs changes the post-login landing page accordingly.

Method demonstrated (test before reverting)

  • After changing start page settings:
    • do testing
    • then (best practice shown) revert back to the prior “normal” configuration once testing is complete.

4) Notification tab (end-user notifications + admin configuration)

Types of notifications described (examples)

  • Password reset notification
  • Performance/goal notifications (goal setup early in year + manager coordination)
  • Notifications to finalize/freeze goals (manager-side)
  • Annual performance review notifications:
    • self-assessment (employee)
    • manager assessment (manager)
  • Contract end notifications (contract employees):
    • communication to extend or close contract
  • Tax/investment declaration notification:
    • submit investment declaration for income tax

How notification delivery is configured

  • End users may receive notifications via email or in-system, but configuration is stored in the Admin Center.
  • The video points to: Admin Center → Tools → Email Notification Template.

Email Notification Template configuration concept

  • Standard templates are pre-provided by SAP:
    • not custom-created from scratch in the described flow
    • enabled/disabled via template settings
  • Templates have:
    • Email subject
    • Email body content
  • Content uses tokens (placeholders in inverted brackets):
    • tokens are standard SAP placeholders
    • tokens are replaced at runtime by values fetched from the system/employee directory
    • the video emphasizes: use tokens instead of hardcoding variable data to avoid errors or missing values.

Token example behavior

  • Token like employee_name is replaced with the actual employee name (e.g., “Alex”).
  • The video contrasts:
    • writing a generic sentence without tokens (can break/fail)
    • using tokens so the system substitutes correct values automatically.

Troubleshooting workflow described

  • When customers report notification issues:
    • open Email Notification Template
    • search for the relevant notification template
    • verify tokens used are correct and match expected behavior
    • apply modifications (save)
    • optionally download and reuse templates via import later.

5) Change Language tab (enable languages for the customer)

  • The UI shows multiple languages in a demo, but in real life:
    • only customer-relevant languages should appear.
  • Languages are enabled via the provisioning system (backend).
  • Once enabled in provisioning, they appear in Change Language for users.

6) Proxy (proxy management + what it solves)

Purpose

  • Proxy allows a person to act in another user/account’s place to perform tasks when the main user (often a manager) is unavailable.
  • Typical scenario:
    • when a manager is absent, they nominate a proxy so work continues.

Example scenario

  • Payroll manager absent:
    • payroll executive acts as proxy for the manager for that week
    • executive can run payroll tasks during manager absence.

Methodology / instructions: Proxy management (4 ways shown)

The video describes four methods to create proxies, grouped as:

  • Admin-managed methods: multiple approaches handled through Admin Center
  • User-managed method: individual proxy creation enabled for managers

A) Method 1: Admin Center → Proxy Management (manual assignment via admin)

Steps described

  1. Admin Center → Tools (proxy management area) → Proxy Management
  2. Use “Grant proxy” / assignment approach:
    • choose account holder (manager whose account will be accessed)
    • choose proxy user (the nominated person)
    • grant the appropriate feature access/permissions
    • save
  3. View existing assignments:
    • Look up existing proxy
    • confirm which proxies are connected to an account holder
  4. If needed:
    • admin can remove the proxy (delete assignment)

Notes stated

  • No restriction that:
    • one account holder can have multiple proxies
    • and one proxy can be linked to multiple account holders

B) Method 2: Enable Proxy Tab for end users → Individual users assign their own proxy

Prerequisites

  • The proxy tab must be enabled/available for managers.

Admin setup

  • Admin Center → Company Settings → Company System and Logo Settings (as shown)
  • Find “Disable proxy access”
    • Uncheck to enable
    • save settings
  • Logout/login to see changes.

End-user behavior

  • When proxy is enabled:
    • managers go to their settings (Proxy tab)
    • use Assign Proxy
    • select a proxy user (e.g., direct reporter like a payroll executive)
    • select which access/feature(s) to grant
    • save
  • Proxy user accesses the manager’s account and sees only granted features (others disabled).

Important restriction

  • Enabling/disabling proxy access applies globally:
    • enabling applies to all employees (no per-department mention as a supported option in the demo)
    • disabling removes it for all employees.

C) Method 3: CSV via Employee Export + Proxy column (using User ID)

Concept

  • Download a user directory CSV, modify proxy info in it, then import.

Steps described

  1. Admin Center → a configuration tool called Employee Export
  2. Choose user directory export (downloadable ZIP/CSV master sheet)
  3. In the CSV:
    • identify User ID fields
    • note: User ID is unique and cannot be changed easily; username can be changed
  4. Edit the CSV to add proxy relationship using the Proxy column (use User IDs, not only usernames)
  5. Import back using Import Employee Data:
    • select Entity = basic input
    • ensure CSV format and encoding UTF-8
    • upload and import
  6. Verify in Proxy Management:
    • search by account holder username
    • confirm proxy relationship exists

Validation notes

  • Keep CSV handling correct:
    • keep CSV format (not Excel)
    • if Excel conversion occurs, re-save back to CSV.

D) Method 4: Use “Download Template” (blank proxy input template) for bulk proxy assignment

Goal

  • Provide a blank CSV template specifically for proxy input.
  • Useful for bulk proxy assignment without editing the full master sheet.

Steps described

  1. In Proxy Management, choose Download Template (blank CSV)
  2. Template columns shown:
    • User ID (account holder user ID)
    • Proxy ID (nominated proxy user ID)
    • permission/grant options (choose which features to enable)
  3. Fill multiple rows for multiple users (bulk scenarios)
  4. Save and import the filled CSV:
    • Import with UTF-8 encoding
    • ensure CSV file extension/format
  5. Verify in Proxy Management search results

Best-practice guidance stated

  • For large-scale cases (e.g., 100+), prefer the proxy input template.
  • Use master sheet CSV editing mainly for broader or all-employee cases vs. smaller specific sets (as differentiated in the video).

Speakers / sources featured

  • No specific individual speakers are clearly identified by name in the subtitle text.
  • Source branding mentioned in the video title: CyberBrainer (channel/source).
  • SAP SuccessFactors / SAP are referenced as product sources (not as individual speakers).

Original video