# Employee creation and onboarding

Employees opens the paginated directory. Add employee opens a separate page at `/t/{company}/employees/create`. Saved filters, exports and record permissions continue to apply.

Select nationality from the searchable country list. Company administrators can narrow new selections in **Company settings → People & policies → Countries & nationalities**. All countries and territories are available initially. Existing nationality strings remain editable without forcing a replacement, even if removed from the company's active choices. New selections, including CSV imports, follow the company list.

Emergency contact name, relationship, calling-code country and telephone number are separate encrypted fields. Phone selectors include worldwide calling codes independently of nationality preferences. Enter the phone number without repeating the calling code. Old emergency contact notes remain retained and visible to authorized private-profile viewers; the upgrade does not attempt to guess phone numbers from historical prose.

For a manual hire, record the joining date, hiring source, initial position and reporting manager. The position provides organizational placement and still enforces approved headcount and scoped HR responsibility. When Career is enabled, an optional probation review date creates the existing probation lifecycle task. Confirmation and later extensions continue through the existing lifecycle approval process. Hiring through Recruitment retains the approved offer, contract, onboarding tasks and probation date.

After creation, a dialog offers to add documents now. The same action remains on Employee 360. It opens an employee-specific document form with the owner preselected; category ownership, subscription and authorization checks remain enforced. Create the document record, upload the evidence into the private vault, then scan and verify its metadata using the existing flow.

Employee creation does not automatically grant login access. An administrator with both employee-edit and user-management permissions can create and link an Employee-role account from **Workspace access & password**, subject to company user capacity. Set a strong initial password and share it privately, or request an expiring password setup email. Setup email requires Super Admin's outgoing account mail to be enabled. Failed email delivery leaves the linked account available for retry and never displays a reset token. Existing company accounts can be linked by an authorized user administrator. MFA remains optional.

## Upgrade

Back up the database and private storage, then run `php artisan migrate --force` for the additive onboarding columns. Do not seed or reset populated databases. The migration retains all legacy contacts and employee records and is forward-only. Rebuild browser assets and clear compiled views with the normal deployment process.

Country names come from the installed [ICU/Unicode territory data](https://github.com/unicode-org/icu). Calling codes are derived from [Google libphonenumber metadata](https://github.com/google/libphonenumber/blob/master/resources/PhoneNumberMetadata.xml), licensed under Apache 2.0. The generated reference data is bundled locally; no employee information is sent to either source and no external lookup is needed when using the form.