Overview
The Swif Desktop App runs on employees' macOS, Windows, and Linux computers. It's how end users see company notifications, browse and install approved apps, and get their device assigned to them automatically when they sign in. This article covers what the app does, how it behaves on each platform, and how to check that it's installed.
Supported platforms
The Swif Desktop App is installed on a device when it enrolls in Swif. If you onboard new hires with automatic enrollment emails, the Application Installer option delivers the desktop installer for macOS and Windows.
👉 Learn more: Onboard New Hires with Swif
Key features
1. In-app notifications
The Desktop App receives notifications that admins send from the Swif Webapp, along with automated system alerts.
Notification tabs
All (default): Every read and unread notification, including system alerts.
Unread: Only unread notifications. An unread badge counter shows on both the sidebar menu and the tab.
Trash: Notifications the user has dismissed or deleted.
System vs. admin notifications
Admin notifications are messages created in the Swif Webapp. Users can mark them as read or move them to Trash.
System notifications are automated alerts, such as
FILEVAULT_KEY_REGENERATE. They're pinned to the top of the All tab, start with a [SYSTEM] label, and can't be marked as read or trashed.
Deep links
An admin can attach a deep link to a notification so the user goes straight to a page in the Desktop App. Supported pages:
Overview
Installed apps (
AppInstalled)App Store (
AppStore)
If the admin leaves the button label blank, it defaults to "Open [Page Name]", for example "Open Overview".
Avoiding notification fatigue
The app checks for notifications every 5 minutes.
It only pops up for new notifications that haven't been shown yet. Older unread notifications don't trigger the pop-up again.
If the user quits and restarts the app, this alert logic resets.
Status sync and privacy
When a user reads, dismisses, or deletes a notification, that status syncs back to Swif, so the Webapp's Sent, Read, and Failed counts stay accurate.
Notifications are scoped to the right organization, device, and employee. One organization never receives another's notifications.
👉 Learn more: Swif In-App Notification System
2. Windows system tray support
On Windows, the app keeps running in the system tray so it can keep receiving notifications.
Clicking Close (X) minimizes the app to the tray. It doesn't quit.
Right-clicking the tray icon opens a menu where users can quit the app completely.
The app can also be minimized and pinned to the Windows taskbar.
💡 Tip: If users think the app has "disappeared" on Windows, ask them to check the system tray. Click the ^ arrow on the taskbar to show hidden icons.
3. Automatic device assignment on sign-in
Devices sometimes enroll without an owner. This happens when they're deployed in bulk, pre-provisioned from an inventory pool, or enrolled with a generic zero-touch installer. The Desktop App can find these unassigned devices, ask the user to sign in, and assign the device to that user automatically.
Turn on auto-assignment (admin)
Log in to the Swif Console as an admin.
Go to Settings → General.
Find Prompt Sign-In and Auto-Assign Device.
Turn the toggle ON.
What the end user sees
Ownership check: When the app launches, it checks whether the device has an owner.
Sign-in prompt: If there's no owner, the app asks the user to sign in so Swif knows who they are.
Automatic assignment: After sign-in, the app checks in with Swif in the background until the device is assigned to the user's employee record. If that user doesn't have an employee record yet, Swif creates one.
Check-ins stop: Once the device is assigned, the background check-ins stop.
Policies apply: Role-based Smart Device Groups, department policies, and required software apply to the device automatically.
How it behaves in different cases
Scenario | Desktop App behavior |
Feature turned off | No sign-in prompt and no auto-assignment check-ins |
Device has no owner | Asks the user to sign in, then assigns the device |
Device already has an owner | No sign-in prompt and no auto-assignment check-ins |
The new owner shows up in both the Desktop App and the device's details page in the Swif Webapp. Auto-assignment works the same way on macOS, Windows, and Linux (x86 and ARM64).
4. Customize resources & links
Admins can configure organization‑wide settings and company resources for the Swif desktop app and browser extension from the Swif web app.
Learn more at Managing Swif's Desktop App UI and Company Resources.
Check whether the Desktop App is installed
If a device enrolled successfully but the user can't find the Swif Desktop App, check whether it's actually installed.
Option A: Swif Webapp (easiest)
Open the device in the Swif Webapp and look for the Swif Desktop App in its installed applications.
Option B: Live Terminal
If Live Terminal is turned on for the device, for example, on windows, run:
Get-AppxPackage com.swifteam.app
If the command returns package details, the app is installed. Ask the user to check the system tray (see the Windows section above).
If it returns nothing, the app isn't installed on the device. Contact Swif Support and include the device's serial number so we can investigate.
FAQ
Why does the Desktop App keep running after I close it on Windows?
Closing the window minimizes the app to the system tray so it can keep receiving notifications. To quit it completely, right-click the tray icon and choose quit.
Why is the app asking me to sign in?
Your organization has turned on automatic device assignment, and your device doesn't have an owner yet. Once you sign in, Swif links the device to you.
Can I dismiss system notifications?
No. System notifications such as the FileVault recovery key alert stay pinned until the underlying issue is resolved.
Will I get the same notification pop-up over and over?
No. The app only pops up for new notifications. Restarting the app resets this.
Related articles