Skip to main content

Configuration

Administration → Configuration — organization-wide settings. Requires employee:admin.

Configuration pageConfiguration page
Configuration — Employee ID tab

The page has three tabs — Employee ID, Custom Fields and Tenant Settings — and Export / Import buttons in the header that move all three between environments (see Export and import).

Employee ID format​

Define how employee IDs are generated (prefix, separator, number padding, e.g. EMP-0042). The live preview panel shows exactly what the next generated ID will look like before you save. New employees created in People receive IDs in this format automatically.

Change the format only before bulk-creating employees — existing IDs are never rewritten.

On the tab, Active Configuration shows the published format (or tells you the built-in EMP-0001 style is in use if nothing is published) and Configuration Versions lists every draft and published version. Use New Draft to create a version, then publish it to make it live.

Custom Fields​

Custom fields tabCustom fields tab
Custom Fields — extra attributes on the employee profile

Define additional attributes that appear on the employee profile — text, number, date, yes/no or a pick-list. Each field says whether the employee or only an administrator can edit it.

Tenant Settings​

Tenant settings tabTenant settings tab
Tenant Settings — switches and rules for your organization

Switches and rules for your organization, kept as key / value pairs. Each has a type (text, whole number, true/false or JSON) and a value that must match it. Settings ZapHRMS knows about are shown with a friendly name and a suitable control (a switch, a number, or a list of choices); any other setting is edited as plain text.

GroupSettingWhat it does
ModulesProjects, Timesheets, Appraisals, Tax declarations, PulseSwitch the module on or off for the whole organization. Switched off, its pages disappear from everyone's sidebar.
Attendance requestsAllow work from home / on duty / permissionWhether employees may raise those request types.
Default timezoneThe timezone attendance uses when an employee's work location has none.
Shifts and rosterShift change — attendance handlingWhat happens when a shift assignment is backdated over days whose attendance is already calculated: Block (default, refuse it), Recalculate (allow, and re-derive those days in the background) or Ignore (allow, leave those days on the old shift's timings).
Roster — bulk assignment over pending requestsWhen HR bulk-assigns shifts over days that have an undecided shift change or swap request: Warn (default, assign and list the requests affected, which then can't be approved) or Block (refuse until they are decided or withdrawn).
Attendance locationOffice geofenceOff (default); Record and flag — record where each punch was made and flag those outside every office; or Refuse — refuse any check-in or check-out outside an office geofence. Refuse needs coordinates on at least one location.
Geofence default radius / accuracy limitThe radius (metres) for a location with none of its own (default 200), and the worst device accuracy still accepted as a position (default 200).
Record punch locationAsk the browser where it is at each punch and keep the answer, even with no geofence to check it against.
Track location during the dayAlso record where the employee is between punches (default off), every interval minutes (default 15, minimum 5), optionally only while checked in. A browser reports nothing while its tab is hidden or the screen is locked, so the trail has gaps.
DocumentsDocuments — automatic readingWhether uploaded employee documents are sent to the AI service to be read.

Where a position was recorded it shows on the day's attendance record — see My Attendance.

Export and import​

Export downloads one JSON file holding the Employee ID configuration (the published one, or the draft if nothing is published), every custom field and every tenant setting. It is the quickest way to set up a new environment like an existing one.

Import reads such a file, compares it with what is there now and shows a table of what would change — New, Updated, Deleted and Skipped for each section. Tick the sections you want, optionally choose Delete entries not in the file, and confirm with Import N changes.

  • Employee ID is saved as the draft (replacing any existing draft). Publish it from the Employee ID tab to make it live. Department and location mappings in it refer to ids from the tenant that exported it, so check them.
  • Custom Fields are matched by field name — existing fields are updated and new ones created.
  • Tenant Settings are matched by key — existing keys are updated and new ones created.
  • With Delete entries not in the file on, custom fields and tenant settings missing from the file are deleted, so those sections match the file exactly.

The i icon next to the buttons opens the same explanation in the app.