Assignar Pay Product Release – March 30, 2026

A summary of what's new, why it matters, and how to get started.

Assignar Pay Product Release – March 30, 2026

TL;DR

  • New Public API scopes and Cost Code endpoints – Granular, least-privilege access for integrations plus the ability to pull cost codes into your ERP and BI tools
  • Day rules now take priority over shift rules – The correct payroll rule applies every time, preventing overtime surprises and reducing disputes
  • Edit Shift Rule modal no longer overflows – Confident editing on tablets, laptops, and smaller screens
  • Allowance edits save reliably – Pay runs stay accurate without manual workarounds
  • Clearer labels and better API docs – Consistent terminology across the platform and upgraded API key documentation for faster, safer setup

What's new

Public API – Reference Data Scopes

Integrations can now request only the data they need. New granular scopes for reference data endpoints follow the least-privilege principle, reducing exposure and supporting compliance-ready connections with your ERP, BI, or custom tools.

What it does:

  • Introduces fine-grained API scopes for reference data access
  • Allows API keys to be restricted to only the endpoints an integration actually uses
  • Reduces the risk surface for third-party connections
  • Supports compliance requirements that mandate least-privilege access controls

Where you'll find it: Navigate to Settings -> API Keys. When creating or editing an API key, you can now assign reference data scopes individually.

Who benefits: IT administrators and integration developers gain tighter control over what external systems can access. Compliance teams can verify that API keys follow least-privilege policies.

Public API – GET Cost Code Endpoints

Pull your cost code hierarchy directly into external tools for job costing, reporting, and reconciliation—no more manual exports or copy-paste.

What it does:

  • Exposes cost codes, categories, and subcategories via the Public API
  • Enables external ERP, accounting, and BI tools to read cost code data programmatically
  • Supports filtering and pagination for efficient data retrieval
  • Keeps your cost code structure in sync across systems without manual effort

Where you'll find it: Available via the Public API. See the updated API Keys documentation for endpoint details, authentication, and example requests.

Who benefits: Finance teams integrating Assignar Pay with accounting software eliminate manual cost code entry. Project managers using BI dashboards get live cost code data without exports. Integration developers save hours of custom mapping work.

Day Rule Precedence Over Shift Rules

Day-level payroll rules now correctly override shift-level rules, and overtime prevention logic ensures the right rate applies every time—fewer disputes, less rework.

What it does:

  • Ensures day-based rules take priority when both day and shift rules could apply to the same timesheet entry
  • Prevents unintended overtime calculations caused by conflicting rule layers
  • Eliminates ambiguity in payroll processing when multiple rule types overlap
  • Reduces the need for manual payroll corrections after processing

Where you'll find it: This improvement applies automatically during payroll processing. No configuration changes are needed—existing day rules and shift rules continue to work, with day rules now correctly taking precedence.

Who benefits: Payroll administrators processing complex rosters see fewer unexpected overtime charges. Workers receive correct pay without disputes caused by rule conflicts. Finance teams spend less time on post-run corrections.

Edit Shift Rule Modal – Responsive Fix

The Edit Shift Rule modal no longer overflows horizontally on smaller screens, so you can configure shift rules confidently on any device.

What it does:

  • Fixes horizontal overflow in the Edit Shift Rule modal on tablets and smaller laptop screens
  • Ensures all fields and actions remain visible and accessible without side-scrolling
  • Improves the editing experience for payroll administrators working on the go

Where you'll find it: Navigate to Pay Rates -> open a pay rate document -> Shift Rules. The modal now fits within the viewport on all supported screen sizes.

Who benefits: Payroll administrators editing shift rules on smaller displays no longer need to scroll horizontally or resize their browser.

Allowance Updates Save Reliably

Edits to allowances now persist as expected, eliminating a bug where changes could be lost and pay runs could process with stale data.

What it does:

  • Fixes a reliability issue where allowance edits did not save correctly under certain conditions
  • Ensures pay runs use the latest allowance values without manual workarounds
  • Reduces the risk of incorrect pay caused by outdated allowance data

Where you'll find it: This fix applies automatically. Allowance edits in pay rate documents now save reliably.

Who benefits: Payroll administrators updating allowance values can trust that changes are saved and reflected in the next pay run. Workers receive correct allowance amounts without delays.

Stronger Form Submission Validation

Behind-the-scenes validation improvements harden form submissions, keeping workflows stable and preventing edge-case submission failures.

What it does:

  • Adds additional server-side validation checks to form submissions
  • Prevents edge-case submission failures that could interrupt automated workflows
  • Improves the reliability of form-based processes across the platform

Where you'll find it: This improvement applies automatically to all form submissions. No action required.

Who benefits: Site supervisors and foremen submitting forms in the field experience fewer unexpected errors. Teams relying on form-triggered workflows see more consistent execution.

Consistent Terminology Across the Platform

Labels and terms have been updated for consistency, so what you see in the UI matches how your team talks about the work.

What it does:

  • Standardises terminology across navigation, buttons, and descriptions
  • Aligns UI labels with construction industry language
  • Reduces confusion when navigating between different sections of the platform

Where you'll find it: Terminology updates appear across the platform automatically.

Who benefits: All users benefit from clearer, more intuitive labels that match the way construction teams work.

API Keys Documentation – Enhanced Examples and Scope Details

Updated API key documentation with better examples, scope explanations, and setup guidance so your team can integrate faster and more securely.

What it does:

  • Adds detailed examples for common API key setup scenarios
  • Documents all available scopes with clear descriptions of what each scope grants
  • Includes guidance on key rotation, least-privilege configuration, and security best practices
  • Makes it easier for new integrations to get started without trial and error

Where you'll find it: Navigate to Settings -> API Keys -> Documentation, or access the API documentation directly.

Who benefits: Integration developers and IT administrators setting up new API connections get started faster with clear, practical examples. Security-conscious teams can follow documented best practices for key management.

Why it matters for construction teams

For payroll administrators: Day rule precedence eliminates one of the most common sources of payroll disputes—conflicting rule layers that produce unexpected overtime. Combined with reliable allowance saves, your pay runs are more accurate out of the box. The responsive shift rule modal means you can make last-minute rule adjustments on any device without fighting the UI.

For IT and integration teams: Granular API scopes and Cost Code GET endpoints open the door to tighter, more secure integrations with your ERP and accounting tools. Instead of broad access keys, you can now issue keys scoped to exactly what each integration needs. The improved API documentation cuts setup time and reduces back-and-forth with support.

For site supervisors and foremen: Stronger form submission validation means fewer failed submissions when you're on-site with limited connectivity. Consistent terminology across the platform makes navigation intuitive without needing a manual.

For finance and accounting teams: Cost codes flowing directly into your external tools via the API eliminates manual exports and copy-paste errors. Day rule precedence and reliable allowance saves reduce the corrections you need to make after each pay run.

Real-world impact:

  • Fewer payroll disputes: Day rules correctly override shift rules, preventing overtime surprises
  • Faster integrations: Granular API scopes and cost code endpoints reduce setup time from days to hours
  • More accurate pay runs: Allowance edits save reliably, eliminating stale-data errors
  • Confident editing on any device: Shift rule modal works properly on smaller screens

Getting started

Public API – Reference Data Scopes and Cost Code Endpoints:

  1. Navigate to Settings -> API Keys
  2. Create a new API key or edit an existing one
  3. Assign the specific reference data and cost code scopes your integration requires
  4. Use the updated documentation for endpoint details and example requests

Permissions: Requires API key management permissions.

Day Rule Precedence, Allowance Reliability, Form Validation, and Terminology Updates:

These improvements are active automatically. No setup or configuration changes required.

Edit Shift Rule Modal Fix:

The responsive fix is applied automatically. Open any shift rule for editing and the modal will fit your screen correctly.

API Keys Documentation:

Navigate to Settings -> API Keys -> Documentation to access the updated guides and examples.

Release details

Rollout: All features and fixes in this release are available to all Assignar Pay accounts immediately. Public API scope changes apply to newly created or edited API keys. Day rule precedence, allowance reliability, form validation, terminology updates, and the shift rule modal fix are active automatically with no configuration required.

Changelog

Added:

  • Granular reference data scopes for Public API keys enabling least-privilege access
  • GET Cost Code endpoints exposing cost codes, categories, and subcategories via the Public API
  • Enhanced API key documentation with detailed examples, scope descriptions, and security guidance

Improved:

  • Day rules now correctly take precedence over shift rules with overtime prevention
  • Terminology standardised across the platform for consistency with construction industry language
  • API key documentation expanded with practical examples and scope details

Fixed:

  • Horizontal overflow in the Edit Shift Rule modal on smaller screens
  • Allowance edits now save reliably, preventing stale data in pay runs
  • Form submission validation hardened to prevent edge-case failures