SAP documents a skills staging gate—and a trusted-source bypass
SAP's 1H 2026 documentation describes a review queue for imported and inferred skills, while trusted sources can write directly to the Attributes Library.
What happened
SAP documents Skills Governance as a generally available, automatically enabled 1H 2026 feature in SuccessFactors Talent Intelligence Hub.
Why it matters
The documented bypass, persistence behaviour and separately described inference path define the questions a controlled tenant test must answer before the screen can be treated as the whole approval boundary.
SAP's 1H 2026 release note describes Skills Governance as generally available and automatically enabled in SuccessFactors Talent Intelligence Hub. The vendor identifies the feature as SIF-1457, document HCM-5F24-20A3, and marks the release information as valid from 15 May 2026. SAP places it under Platform → Talent Intelligence Hub → Attributes Library and lists its enablement as automatically on. These are SAP's product statements, not independent evidence of customer adoption or operating effectiveness.
SAP's workflow documentation shows separate Imported and Inferred tabs. It says a steward can standardise a proposed or alternate name, choose a custom name, or publish a skill to the Attributes Library. Publication also makes the skill available through the Attribute Picker.
The same documentation describes an exception: a source configured as a Trusted Data Source can bypass Skills Governance and add skills directly to the Attributes Library. A separate SAP knowledge-base article says the queue has no delete action, automatic purge, or retention period; an unwanted record can remain unpublished but stays in the queue.
SAP's current AI-Assisted Skills Architecture page separately describes inferred records being added to the Attributes Library with Created Type = INFERRED, followed by bulk confirmation through a scheduled job.
Questions for a tenant test
- Which import and inference routes enter the staging queue, and which bypass it?
- Which permissions control review, standardisation, publication, correction and removal?
- Which source, status and decision fields survive export and downstream matching or assessment?
- What happens downstream when a disputed skill remains in the queue or must be rolled back?