Version 0243

Updated by Victor Jespersen

Release summary

Release date August 19, 2026

Short on time and want a high-level summary?  🚀

Quinyx web app Version 0243

New functionality

  • None at this time.

New functionality requiring configuration updates

  • We have made updates to how you can switch on the Cross-Unit Scheduling feature.
  • Previously, when an employee punched in via the Mobile app, any new device needed manual approval from a manager before the employee could punch in. You can now turn off manual approval and let new devices get approved automatically – reducing the manual work for your managers. This is an org-wide setting, available to users with access to Account settings.

Updates and performance improvements

  • None at this time.

Bug fixes

  • None at this time.

Mobile app

New functionality

  • Want to know more about the new mobile app version? Click here to check the mobile release notes.

Employee Hub Version 0243

New functionality

  • None at this time.

New functionality requiring configuration updates

  • None at this time.

Updates and performance improvements

  • None at this time.

Bug fixes

  • None at this time.

REST API / Web service updates

  • None at this time.

Important information

📣 Join us for the next Quinyx Unlocked: Introducing audits in Employee Hub

9 September 2026 | 16:30 CEST / 10:30 EDT | 30 minutes

See how Quinyx helps you standardise, execute, and follow up on Audits — all in one place.

Keeping every store running to the same standard is harder than it sounds. Most teams rely on spreadsheets, PDFs, and email chains to run audits — and by the time findings are collected, shared, and acted on, the moment to fix things has often passed. We built Audits in Employee Hub to change that.

Join us for a live walkthrough of Quinyx's new audit capability: what it does, how it works, and how it can help your operations, retail, and field teams run consistent, accountable audits across every location — without the admin.

What we'll cover:

  • What audits are and why they matter for multi-location organisations
  • The problems teams face today when running audits manually
  • How Audits in Employee Hub works — from template to follow-up
  • A live product demo

This webinar is for you if you work in:

  • Retail operations or store excellence
  • Field management or area/district management
  • HR, compliance, or quality assurance
  • Any role responsible for keeping standards consistent across multiple locations

Quinyx web app Version 0243

New functionality

None at this time.

New functionality requiring configuration updates

How to switch on Cross-Unit Scheduling

We have made updates to how you can switch on the Cross-Unit Scheduling feature. Two settings control this feature:

Permissions - who can use it

Set per role in Role Management. Controls what an individual manager can do.

Access level: What they can do

Off: No cross-unit scheduling access

Read: See cross-unit shifts and details, but not edit them

Write: See, create, edit, and delete cross-unit shifts

Unit enablement - where it can be used

Set per unit in Account Settings > Group Management > Select Unit > Advanced Settings > Functionality. Controls whether a unit can be scheduled into by other managers.

If a unit has the feature switched off, it won't appear in the Unit dropdown within a shift panel — no one can schedule into it, regardless of their permissions.

If a unit has the feature switched on, managers with the right permissions can schedule into it.

Permissions control who can cross-schedule. Unit enablement controls which units can be scheduled into. Both need to be in place for a manager to schedule a shared employee into another unit.

For customers who currently have the Cross-Unit-Scheduling module enabled:

The module is being phased out and replaced by the new permissions and unit settings. Until the transition is complete, the module will remain in control. The feature will continue to work as it does today, and any changes made to the new permissions or unit settings will not take effect yet.

Automatic approval of new devices is now possible

Previously, when an employee punched in via the Mobile app, any new device needed manual approval from a manager before the employee could punch in.

You can now turn off manual approval and let new devices get approved automatically – reducing the manual work for your managers. This is an org-wide setting, available to users with access to Account settings.

Where to find it: Account settings > Mobile account settings > Approval of devices for punching

Manual approval is enabled by default. If disabled and later re-enabled, previously approved devices remain approved.

Disabling manual device approval removes the manager checkpoint that helps prevent buddy punching (an employee punching in or out using a device not previously verified for them). Consider this trade-off before disabling it org-wide.
Automatic approval only applies to new devices. If a device is already registered but hasn't been approved, it still needs manual approval.

Updates and performance improvements

None at this time.

Bug fixes

  • None at this time.
  • New HelpDocs content

  • None at this time.

Mobile app 3.57

Want to know more about the new mobile app version? Click here to check the mobile release notes.

Employee Hub web app Version 0243

New functionality

  • None at this time.

New functionality requiring configuration updates

  • None at this time.

Updates and performance improvements

  • None at this time.

Bug fixes

  • None at this time.

New HelpDocs content

  • None at this time.

REST API / Web service updates

None at this time.

Please make sure to forward this information to the party within your company responsible for integrations.

We encourage all of our customers to make use of our APIs to maintain data and to make sure that information is up-to-date. To ensure the scalability of our APIs while growing our customer and user base, we've decided to add restrictions on the usage of our SOAP APIs. These restrictions will be enforced programmatically, which means we will enforce a limit on concurrent calls per customer to 10. You should expect response code 429 if you happen to exceed this limit, and you are recommended to implement a backoff retry mechanism to handle the limit. Note that the limit applies to SOAP only. When moving from SOAP to REST over the coming years, any limits will be built into the API. 


How Did We Do?