A toggle in System Settings governing whether the ERP supports multiple legal entities. When enabled, the system exposes the Companies module (registry, creation wizard, company switcher) and allows selecting multiple companies to work with. When disabled, the system is hard-locked to a single active company and all multi-company UI is hidden — matching today's system, which has no Company entity at all.

Replaces today's flat, hardcoded 'Company: Pentavalue' text field on the User form (see Users screen) with two fields — Allowed Companies (multi-select) and Default Company (single-select) — plus an in-session Multi-Company Selector in the top navigation bar, available only when Multi-Company Mode is enabled.

A per-company configuration layer so the product can be sold as a SaaS across industries and countries without hardcoding schedule assumptions. This reuses and extends the existing Weekend Days and Attendance Settings/Shifts screens already in the system — the only change is that these become company-scoped instead of global. Attendance, Payroll and Leave epics read this configuration at calculation time.

There is currently no Company entity or creation flow in the system at all — 'Company' is a static text field pre-filled on the User form. This story introduces the Company as a real master-data entity via a 6-step wizard (General Info → Legal & Tax → Address & Contact → Financial & Localization → Admin & Users → Review & Activate), the mechanism that produces the records US-001's parent_company_id and US-002's Allowed/Default Companies point to.

Corrected scope: the source didn't specify whether HR ID uniqueness is global (across the whole SaaS platform) or per-company. For a multi-tenant SaaS, HR ID must be unique per Company, not globally — a platform-global counter would leak information across tenants (e.g. revealing how many total employees exist platform-wide) and doesn't match how any single customer thinks about their own numbering.