Organization setup

Provision profile, departments, policies, and invites in order.

Organization Setup Guide

Set up your organisation in dependency order. Skipping steps causes import errors or empty employee records.

Recommended setup order

1. Organisation profile + country  (/hrms/onboarding)
2. Departments (/hrms/organization)
3. Working pattern + holiday calendar (created by onboarding template)
4. Leave policy (country onboarding + display on `/hrms/leave`)
5. Locations (via organisation / employee forms)
6. Managers (as employees) (/hrms/people/new)
7. Workforce import or manual people (/hrms/migration/workforce or /hrms/people)
8. Invites / activation (/hrms/invites)

Organisation profile

Route: /hrms/organization

  • Company name, slug (read-only after creation)
  • Departments: add/edit via organisation page
  • Not supported: legal entities, business units, cost centres as first-class objects

Country configuration

Route: /hrms/onboarding

Sets country_code, locale, currency_code, default_timezone, seeds leave policy and calendar templates.

Departments

Required before assigning employees. Default departments exist after provisioning. Reference by exact name in CSV import.

Job titles

Free text on employee records — no separate job-title master list.

Managers and reporting

  1. Create manager as employee first (/hrms/people/new)
  2. Assign manager role if they need team/leave approval access
  3. Set manager_email on reports (import or edit)

Manager relationships resolve in import pass 2 after all rows exist.

Working patterns

Created by country onboarding (STANDARD 5-day week). Assign via import working_pattern_code or employee form.

Limitation: Leave engine has limited support for non-standard schedules.

Holiday calendars

Shell created at onboarding. Dates are operator-managed — no automatic public-holiday API. Assign holiday_calendar_code on employees.

Leave policies

Route: /hrms/leave (policy summary displayed; template applied at /hrms/onboarding)

One policy per organisation today. Fields: annual entitlement, carry-over cap, approval chain flags (manager → HR → payroll stage labels).

Configure before assigning leave_policy_code on employees.

Employee setup

  • Manual: /hrms/people/new
  • Bulk: /hrms/migration/workforce — see [Workforce Import](06_WORKFORCE_IMPORT_GUIDE.md)

User access

Import creates employee records with access_activation_status=imported. Invites (/hrms/invites) link login accounts. Activation is separate from import.

Dependencies summary

Before You need
Employee department Department exists
Employee manager link Manager employee row exists
Leave balance Policy + hire date (or opening balance)
Holiday calendar on employee Calendar code exists
User login Invite accepted

Help: /help/organization-setup