Workforce Onboarding Guide

How existing companies add their workforce to Match Line — from a handful of people to large CSV migrations.

Approaches by size

Tested scale (M26): validation at 10, 100, 1000 rows; commit at 100 rows. 10,000 employees not tested.

Manual employee creation

1. /hrms/people/new
2. Name, email, department, hire date, manager, roles
3. Save — employee appears in directory

Bulk import (available)

Validation-first workflow:

1. Download template — /hrms/migration/workforce/template.csv
2. Upload CSV
3. Validate — errors block commit
4. Preview — review warnings and row summary
5. Confirm — batched commit (50 rows per batch)
6. Audit log at /hrms/migration/workforce/audit

Modes: create_only or create_or_update (match on external_employee_id).

Validation and duplicates

• Duplicate email within file → error
• Existing email in org → error (create_only) or update (create_or_update)
• Unknown department/manager → error or warning per rules

Assignments via import

Columns support: department, location, manager_email, leave_policy_code, holiday_calendar_code, working_pattern_code, opening_balance_days.

HR verification

After import:

1. Spot-check directory /hrms/people
2. Verify manager links on org chart /hrms/people/org-chart
3. Review import audit for failures

Employee activation

Import does not send invites automatically.

1. /hrms/invites — invite by email with role
2. Employee accepts /invite/<token>
3. access_activation_status moves toward active use

Employees with imported status can exist without login until invited.

Opening balances

Use opening_balance_days column for migrated annual leave. Engine calls import_opening_balance() when policy and hire date present.

Help links

• /help/workforce-import
• /help/workforce-onboarding