Learning administration

/hcm/learning (admin tab) is the HR-admin surface for managing the learning catalog: publishing courses, approving peer-authored content through a 4-eyes SoD, configuring the badge catalog + streak rules + leaderboard, and reviewing learner activity aggregates. The runtime is a real xAPI 1.0.3 LRS + cmi5 launch protocol — see Learning for the employee side.

TL;DR — Open HCM → Learning → Admin. Publish courses, approve peer submissions (4-eyes), configure badges + streak + leaderboard, mark courses as required-by-role.

Before you start

• Decide your catalog structure — sections, required vs optional, role-required courses.
• For peer-authored content: define the workspace's submission + review template (rubric, success criteria).
• For badges: decide which milestones earn badges (course count, compliance set complete, streak threshold).

Publish a course

1. 1

   Click "+ New course"

   Opens the course-creation form.

2. 2

   Title + description + duration estimate

   What learners see in the catalog.

3. 3

   Content source

   Upload a cmi5 package, link to an external cmi5-conformant runtime, or use a workspace-authored quiz/video flow.

4. 4

   Prerequisites + success criteria

   Other courses the learner must complete first; pass/mastery threshold for completion.

5. 5

   Required-by-role flags

   Mark the course required for specific roles (e.g. compliance courses for HR; security training for everyone).

6. 6

   Badge + certificate flags

   On completion, issue a certificate? Award a badge?

7. 7

   Publish

   Audit log records HCM_LEARNING_COURSE_PUBLISHED.

Approve peer-authored content (4-eyes)

Peer-authored courses follow a draft → submitted → approved pattern; approval is 4-eyes (author ≠ approver).

1. 1

   Author drafts a course

   Same surface as admin-published; saved as DRAFT.

2. 2

   Author submits for review

   Status changes to SUBMITTED. Audit log records HCM_LEARNING_PEER_AUTHORED_SUBMITTED. The course enters the admin review queue.

3. 3

   A different admin reviews + approves

   Author can't approve their own. Reviewer reads through, runs a test enrollment, and approves / rejects.

4. 4

   Approve

   Status changes to APPROVED. Audit log records HCM_LEARNING_PEER_AUTHORED_APPROVED. The course publishes to the catalog.

5. 5

   Reject (with feedback)

   Author receives feedback; the course returns to DRAFT.

Badge catalog

Streaks + leaderboard

Required-by-role enforcement

1. 1

   Mark a course required-by-role

   From the course edit form.

2. 2

   Set the deadline

   From hire OR from a recurring date (e.g. annual compliance refresh).

3. 3

   Affected employees see the requirement

   On /hcm/me as an Action Inbox item nearing deadline.

4. 4

   Past-deadline tracking

   Affected employees enter a non-compliant state; HR receives a notification + can chase through the dashboard.

Forums per course

Each course's forum is moderated by workspace admins (delete / pin / lock threads). Common moderation flow:

Every field, explained

Audit codes

For SIEM ingestion + compliance review, this surface emits:

See Reference → Audit codes for the canonical description of each.

Common gotchas

• "Course rejected non-conformant statements." Cmi5 strict validation per § 4.1; the rejected detail names which statement + which validation failed.
• "Required course passed but no badge issued." Verify the badge criteria — single-course badges typically need the course flagged as part of a badge set.
• "Author published their own course." Not in production — 4-eyes SoD enforced. Workspace-curator workflows can deliver admin-published courses without going through peer-author.
• "Streak reset at the wrong time." Workspace timezone, not employee. Verify in Branding.

Troubleshooting