Manual entry by an administrator
Handles ad-hoc hires and contractors that never appear in the HR feed.
Automated feed (SuccessFactors / HR event)
Payload fields are mapped and normalized; a malformed or partial event falls back to manual review instead of creating a user.
Required name fields present
Rejects single-character or whitespace-only names from bad feed data.
Email / username well-formed
The email doubles as the IAS login name, so format failures block creation.
Login name not already taken in tenant
Prevents duplicate identities when a rehire reuses a former address.
Employee ID present and unique
Enforced only when the client requires it; a collision points to an existing identity rather than a new hire.
No access
User is created dormant; entitlements arrive later from a separate process.
Assign standard default group
Baseline SSO access without an admin decision on every request.
Manual role/group selection
Admin picks per request when departments map to different entitlements.
Safeguard: administrator role blocking
When the client enables it, the agent can never grant the privileged IAS Administrator role — the option is removed, not merely warned about.
Send activation email immediately
Standard path for same-day starters.
Delay / manual activation trigger
Future-dated start dates: the account exists but stays unusable until an admin releases it.
SAP Cloud Identity Services
Direct connection to the client's IAS/IPS tenant for live user provisioning.
Generic SCIM 2.0 Endpoint
Fallback connector for any identity system that exposes a standard SCIM 2.0 API.
Certification requires all 4 logic blocks and 2 connectors to be approved (0/4 blocks, 0/2 connectors).
Certification is logic-level and applies to every tenant, not to a single client.