Skip to main content

Joining and Onboarding

Summary​

Employee joining is confirmed as creation of a tenant-scoped Active employee with identity, contact, optional employment dates, and optional organization assignment. A complete onboarding process and automatic Recruitment or Identity handoff are not confirmed.

Audience​

  • HR managers, HR executives, and HR administrators
  • Business analysts, Customer Success, product owners, solution architects, and QA engineers

Purpose​

Clarify what the Employee module establishes at joining and which onboarding responsibilities remain outside or unresolved.

Confirmed joining setup​

An employee requires a tenant context, employee code, first name, and email. The employee code and email must be unique within the tenant. Last name and display name are normalized into the employee's business name. The employee starts Active and receives an initial history entry.

The initial record may include:

  • Contact phone and gender.
  • Employment type, work location, joining date, confirmation date, and date of birth.
  • Active department and active designation.
  • An active reporting manager other than the employee.

When both a department and department-specific designation are supplied at creation, they must agree.

Onboarding boundary​

ActivityConfirmed ownership or behavior
Candidate, offer, and recruitment onboardingRecruitment owns these concepts; conversion into Employee Requires confirmation.
Employee record creationConfirmed in Employee.
Department, designation, and manager assignmentConfirmed and optional at creation.
Identity account provisioningRequires confirmation; no automatic one-to-one provisioning was established.
Profile completion checklistRequires confirmation.
Document collection and verificationEmployee stores document references; end-to-end onboarding document workflow Requires confirmation.
Attendance, leave, and payroll activationDownstream handling and timing Require confirmation.
Workflow tasks and approvalsRequires confirmation.

Business rules requiring approval​

Required onboarding documents, mandatory assignments, joining-date validation, backdated/future joining, duplicate-person handling, profile completeness, approval roles, and cancellation of a planned join all require confirmation.

Evidence basis​

The Employee creation model and validators confirm initial record requirements. The backend inventory confirms Recruitment and Identity as separate boundaries but does not establish a complete automated onboarding handoff.

See Also​

Keywords​

  • New joiner
  • Initial employee setup
  • Onboarding boundary

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-15
  • Review cycle: Quarterly