macOS - Software - Update Slack With Notifications

What the Slack update Worklet does

This Automox Worklet™ updates Slack to the latest version available from Slack's official release repository. The Worklet checks the currently installed version against the latest release published on Slack's website, and if a newer version is available, it downloads the universal DMG installer and applies the update.

The Worklet includes intelligent process management that notifies users before terminating Slack, giving them the option to defer the update or proceed immediately. If Slack is not running, the update applies silently in the background.

dmg", "/Library/Application\", "/usr/bin/id".

The update process includes backup and recovery logic that preserves the previous version during installation, allowing automatic rollback if any step fails. After the update completes, the Worklet automatically attempts to relaunch Slack for the user.

Why keep Slack current on your macOS fleet

Outdated Slack versions expose endpoints to known security vulnerabilities that attackers actively exploit. When users run old versions, they miss critical patches for authentication bypasses, remote code execution flaws, and data exposure vulnerabilities. Organizations face compliance gaps and security audit failures when communication tools remain unpatched, creating risk vectors for credential theft and data breaches through compromised Slack clients.

Maintaining current software versions is a core security practice that reduces your attack surface. Using Automox to manage Slack updates maintains consistency across your macOS endpoints without requiring manual intervention from IT staff or users.

How Slack update and notification works

1. Evaluation phase: The Worklet queries Slack's release notes page to identify the latest available version and compares it to the version installed in the Applications folder. If versions match, the Worklet exits without making changes. If the installed version is older, the Worklet proceeds to remediation.

2. Remediation phase: The Worklet downloads the universal DMG installer from Slack's API endpoint, mounts the disk image, and creates a backup of the existing Slack.app. If Slack is running, the Worklet displays a notification allowing the user to defer or approve the update. The Worklet then moves the new version into place, cleans up temporary files, and relaunches Slack.

Slack update requirements

• macOS 10.15 or later

• Slack must be installed in the standard /Applications/Slack.app location

• Sufficient disk space in /var/tmp for the DMG download (approximately 500 MB)

• Internet connectivity to reach Slack's official release servers

• Administrator privileges to access Applications folder and perform the update

• Automox Notifier application installed for user notification prompts

Expected Slack behavior after update

After the Worklet completes successfully, Slack will be running the latest version available. The version reported in Slack's "About" menu will match the latest release published on Slack's website. Users will have access to any new features, security improvements, and bug fixes included in the latest release.

Verification: Launch Slack and select Slack > About Slack from the menu bar to confirm the version number matches the latest release. Check the Automox Activity Log for successful update messages. If the user deferred the update when prompted, Slack will continue running the previous version until the next evaluation cycle. If the update fails at any point, the Worklet automatically restores the previous version from backup and exits cleanly.

How to validate update slack with notifications changes

1. Run this Worklet on a pilot macOS endpoint and review evaluation output for update slack with notifications.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as exit, else.

4. Validate remediation effects from script operations such as function, launchctl, -title, then rerun evaluation for compliance.