Skip to main content
HR settings is where you switch on the automated reminders Hitaji 360 sends about your people — upcoming birthdays, work anniversaries, contracts about to expire, employee documents about to expire, and public holidays — and decide how many days’ notice you want for the expiry reminders. It also hosts the Employment Contracts card, where you configure the template and signatory behind the employment contract e-signature flow. The heavier HR configuration (leave policies, attendance/geofencing, overtime types) lives in its own sibling sections, which this page links you across to. You’ll find this at: /settings/erp/people/hr-general — the HR General & Reminders card under the People group of ERP Settings (/settings/erp).
📷 Screenshot: HR General & Reminders settings — the toggle rows with the “days in advance” inputs and the Save Changes button — to be added.

​
How these settings are scoped

⚠️ Important — these settings are per-tenant, not per-business. Unlike employees, contracts and payroll (which are isolated per business), the reminder toggles on this page are stored as a single record for your whole organisation (tenant). Changing a toggle here changes it for every business under your account, not just the one currently selected in the business switcher. The first time anyone opens the page, a settings record is created with sensible defaults. Keep this in mind if you run several businesses and expected per-business reminder control — that is not how this screen works today.
The leave and attendance configuration reached from the same People group is managed separately (per the rules of those areas); only the reminder settings on this page are the shared, tenant-wide record.

​
What you can configure

The page is a list of toggle rows. Each reminder can be switched on or off; the two expiry reminders also let you set how many days in advance you want to be warned. For the two expiry reminders, the Days in advance box only becomes editable once the reminder itself is switched on. The value must be between 1 and 365 days.
⚠️ Current state — Holiday reminders are disabled. The Holiday reminders toggle is greyed out on the page with the tooltip “Requires a holiday calendar to be configured.” Even though the underlying setting exists, you cannot turn it on from this screen until holiday-calendar support is wired up. Configure your public holidays under Holiday lists in the meantime.
After changing any toggle or lead-day value, press Save Changes. You’ll get a confirmation toast; if a value didn’t take, the page tells you so rather than silently failing.

​
Employment Contracts

⚠️ Unlike the reminders above, this card is per-business, not per-tenant. Each business configures its own employment-contract template and signatory; switching business shows that business’s own settings.
This card configures the employment contract e-signature flow — the agreement that’s auto-sent for signature every time a new employment record is created for this business (via Add Employment or by accepting a job offer). Press Save Changes once the default template and the signatory are set. Until they are, new contracts for this business show “Not sent” rather than actually going out.

​
Why a template per employment type

An intern agreement and a senior full-time contract differ in their clauses, not just their dates — merge variables can’t express that, so each needs its own document. Set only the types that genuinely differ; the rest fall through to the default. At send time the template is resolved most-specific-first: the override for that contract’s employment type, then the default, then (only if neither is set) the tenant’s single Active employment template if there is exactly one.
A business that has only ever set the default template keeps working exactly as before — the per-type pickers all start on “Same as default”.

​
Templates are validated when you save

An employment contract is always addressed to two signers, employee and employer_rep, and signature blocks bind to them by exact role name. Selecting a template whose signer roles differ is rejected, with an error naming the roles it actually has. The same check runs again when a contract is sent, so a template edited after selection can’t quietly produce an unsignable contract. See Signer roles are fixed. Send contracts for signature — below the two fields, a one-off action that runs Generate & Send for every Active contract in this business that doesn’t already have a current envelope — useful for employees hired before this feature existed, or before you’d configured it. Confirm in the dialog, and you’ll get a summary of how many were Sent, already had one (Already sent), or are still Not configured (if you ran it before setting the template/signatory).

​
Permissions

So a manager with hr:read can open the page and see the current settings, but needs hr:write to save changes. (These coarse hr:* slugs are deliberate: the finer hr-settings:* slugs are only granted to full-admin role templates, so gating on hr:* lets ordinary HR-admin roles use the page.) The Employment Contracts card is gated separately on hr-employment:config.
The same People group in ERP Settings holds the other HR configuration areas — these are separate sections, each with its own permissions:
  • Leave Policies (/settings/erp/people/leave) — leave types, policies, entitlements, periods and block lists. See Leave types & settings. (Requires hr-leave:config.)
  • Attendance & Geofencing (/settings/erp/people/attendance) — clock-in rules and geofences. See Attendance.
  • Overtime Types (/settings/erp/people/overtime-types) — overtime multipliers and their salary-component mapping. See Overtime. (Read hr:read, write hr:admin.)