---
title: "Scalefusion May 8th, 2026 Release Notes"
slug: "scalefusion-may-8th-2026-release-notes"
updated: 2026-05-12T10:01:56Z
published: 2026-05-12T10:01:56Z
canonical: "help.scalefusion.com/scalefusion-may-8th-2026-release-notes"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.scalefusion.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Scalefusion May 8th, 2026 Release Notes

## Version Information:

- **Scalefusion Dashboard:** v64.11.0
- **Scalefusion Android Agent:** v20.4.0

## Release Notes:

1. **Holiday Calendar Support for Lock/Unlock Workflows**

Organizations can now create and manage Holiday Calendars from the [**Organization Info**](/docs/updating-organization-information#holiday-calendars) page to simplify [Lock/Unlock](/docs/scheduling-tasks#lockunlock) workflow scheduling. Key highlights:
  1. A single calendar can contain multiple holiday schedules or groups.
  2. Each schedule can include one or more holiday date ranges.
  3. Holiday Calendars can be assigned to Lock/Unlock workflows across Android, iOS, and macOS devices.
  4. When a Holiday Calendar is applied, devices remain unlocked during the configured holiday periods, overriding other schedules.
2. **Android Enhancements & Bug Fixes**
  1. **Faster Android BYOD Enrollment**

Employees enrolling Android BYOD devices using Email and ORG-ID can now skip certain static setup permissions during enrollment and complete setup faster using a simplified permission flow. Remaining permissions can be granted later from **Hamburger Menu > Complete Setup**.
  2. **Automatic Knox SDK Activation for Company Owned Devices**

The Scalefusion agent now attempts to automatically activate the Knox SDK on devices enrolled through Android Enterprise methods, reducing manual steps during setup. If automatic activation fails due to network or other issues, users can still complete activation through the existing manual flow.
  3. **Geofence Compliance Fix**

Fixed an issue where geofence compliance actions could incorrectly trigger even when devices were within the configured geofence boundaries.

## Team:

- Team Scalefusion