Skip to main content

Establish first employment and resolve onboarding access

Current browser limitation: A newly created master has no employment or assignment. Employee detail and directory reads require a record linked to an allowed unit. The create screen then navigates to detail, whose read can return Employee not found before the first Employment tab is available. The guide does not claim that this browser-only onboarding sequence is complete.

This follows the current code paths: creation returns the DRAFT master, normal reads apply unit-linked employee visibility, and Employment creation separately validates the proposed employer unit. Treat it as an implementation gap; do not weaken visibility or duplicate the person to work around it.

Supported API/support route​

Arrange an authorised integration/support operator with EMPLOYEE and dependencies, employee.employment.manage, the correct tenant and access to the proposed employer business unit. Use the exact Employee ID returned by creation. No production request is performed by this documentation.

POST /api/v1/employees/201/employments
Content-Type: application/json
{
  "version": null,
  "employmentType": "PERMANENT",
  "startDate": "2026-10-01",
  "endDate": null,
  "contractNumber": "TRAINING-CONTRACT-01",
  "contractSignedDate": "2026-09-25",
  "probationEndDate": "2026-12-31",
  "confirmationDate": null,
  "noticePeriodDays": 30,
  "terminationType": null,
  "terminationReason": null,
  "lastWorkingDate": null,
  "rehireEligible": null,
  "employerBusinessUnitId": 11
}

All IDs/dates are illustrative and must be replaced by verified approved values. Use the established authenticated API mechanism; never put credentials in the request examples or URLs. The start cannot precede original hire; normal date, overlap, tenant and employer-unit validation still applies. Child create ignores a supplied version; update later requires the returned current version.

Verify the result​

  1. Confirm the successful employment response and its employee/employer linkage.
  2. Reload /employees/201 using an authorised user with the relevant unit grant and employee.view.
  3. Search the approved employee number in the directory.
  4. Open Employment and verify the saved period with employee.employment.view.
  5. Add assignment and other authorised records; change status only when its date rules pass.

If the original Employee ID was lost and the draft remains invisible, ask support to investigate the original creation result through approved operational procedures. This guide does not invent an unlinked-draft browser search, recovery endpoint or automatic retry mechanism. Do not assume a failed detail navigation rolled back creation.