Overview
Use Manage Blocklist to stop users from running apps and browser extensions you don't allow, such as Shadow IT apps found on your devices. You choose what to block, choose the devices or device groups, review what will be enforced, and Swif creates the right policy for each operating system.
To block websites and domains instead, see Block Domains and Filter Web Content.
Where to start
You can open Manage Blocklist from several places. The flow is the same everywhere; only what's filled in for you changes.
Start from | How | What's filled in |
Applications page | Device Management > Applications, then Manage Blocklist in the toolbar | Nothing |
An app on the Applications page | Open the app's row, and click Manage Blocklist | The app, which can't be changed |
Shadow IT | Select an app in the Shadow IT report, and click Manage Blocklist | The app's name and main domain |
A device group | Device Management > Device Groups, open a group, select an app in its Applications table, and click Manage Blocklist | The device group, and the app if you started from its row |
A device | Open the device, go to Applications, and click Add to Blocklist next to an app or extension | The app or extension, and the device |
Browser extensions | Shadow IT > Browser Extensions, select an extension, and choose Manage Blocklist | The extension |
You can select several apps on the Applications page, and block them together.
How Manage Blocklist works
Manage Blocklist has four steps:
Step | What you do |
1. Blocklist Queue | Add the apps, extensions, or domains to block |
2. Select Devices | Choose individual devices |
3. Select Device Groups | Choose device groups |
4. Review | Check what will be blocked, and on which devices, before you save |
Step 1: Add apps to the blocklist queue
Under Blocklist Target, select Application. Then choose how to identify the app:
Option | Use when |
Select from known apps | The app is in Swif's app catalog. Start typing to see matches. |
Enter Custom Application Name | The app isn't in the catalog, such as an in-house app. Type its name, and press Enter. Catalog matches appear as suggestions, if there are any. |
Only one option is shown at a time.
How apps are blocked
How Swif blocks an app depends on where the app came from:
App | How it's blocked |
Software catalog apps | Uninstalled from the device. No block policy is created. |
Shadow IT and custom apps | Swif creates or updates a block policy for each operating system, as below |
Each block shows the policy that enforces it, as a link. You can also open these policies in Device Management > Policies.
macOS
Details | |
Policy | |
What to provide | The app's name |
How it's blocked | Any app whose name contains the name you entered can't be opened. Users see a message that the app is restricted. |
Good to know | The app can still be installed, but users can't open it. Use a specific name, since a short one can match other apps too. |
Catalog apps | Uninstalled by Swif |
Windows
Details | |
Policy | |
What to provide | The app's Application path. Swif fills it in for you, as |
How it's blocked | Windows AppLocker Deny rules block |
Good to know | Apps installed somewhere else won't match, so change the path if needed. Windows Store apps aren't covered. See Windows paths below. |
Catalog apps | Uninstalled by Swif |
Windows paths. The Application path is required, and must end in .exe or \*, such as C:\Program Files\TeamViewer\* or C:\Program Files\TeamViewer\TeamViewer.exe. If it's empty, or ends in something else, you see "Application path is required for Windows applications. Please fill in the path field in the table.", and can't continue.
Microsoft Edge is blocked by its known paths, under both
%PROGRAMFILES%and%PROGRAMFILES(x86)%. You don't need to enter a path.Other built-in Microsoft apps get the generated path,
%PROGRAMFILES%\<app name>\*, which may not match where Windows installs them. Check the app's real path, and test on a few devices first.
Linux
Details | |
Policy | |
What to provide | The app's process name |
How it's blocked | The Swif agent closes the app if it's running, about every 20 minutes, and whenever the device checks for policy changes |
Good to know | The app can open, and run until the next check. The name must match the process name exactly, and names with spaces have no effect. |
Catalog apps | Uninstalled by the Swif agent, through the device's package manager |
Find a Linux process name. While the app is running, run ps -e in Terminal, and find the app's name in the CMD column.
Android
Details | |
Policy | Android Application Policy |
What to provide | Nothing for catalog apps. For custom apps, the package name, such as |
How it's blocked | The app is set to Blocked through Android device management. It can't be installed, and it's removed if it was installed through a policy. |
Good to know | Apps users installed themselves may not be removed. If a catalog app has no known package name, enter it yourself, using Enter Custom Application Name. |
Catalog apps | Blocked and disabled |
iPhone and iPad
Manage Blocklist can't block apps on iPhones and iPads. The Review step marks their app rules as Not supported. To block apps on them, use the Apple iOS/iPadOS Application Block Policy instead.
See when users try to open blocked apps
To record each attempt to open a blocked app, turn on app block tracking in the device's tracking policy. Attempts appear in Device Management > Event Logs > Device Events.
Platform | Policy |
macOS | |
Windows |
Block browser extensions
Choose how to identify the extension:
Option | Use when |
Select user-installed extension | The extension is already installed somewhere in your organization |
Enter package ID | It isn't installed yet. Enter its ID, for example from the Chrome Web Store. |
Then choose the browsers: Chrome, Edge, Firefox, or Safari. Package IDs can differ between browsers, so Swif adds a separate entry for each browser you choose.
Swif enforces extension blocks with each browser's extension policy, such as the Windows Google Chrome Extension Deployment and Blocking Policy, or the Apple Safari Extension Policy.
The queue
Each entry in the queue shows the app or extension, its target operating systems or browser, and, for Windows, its path. You can add apps, extensions, and domains to the same queue before saving.
Step 2: Select devices
Choose individual devices from the table. Use search and filters to find them, and select as many as you need. If you started from a device, it's already selected, and can't be deselected.
See what a device already blocks. Click the arrow at the start of a device's row (Show existing blocklist). It lists the apps and domains already blocked on the device. To change them, click Manage Device Blocklist, which opens the device's blocked list in a new tab. A device with no blocks shows No blocked apps or domains.
Step 3: Select device groups
Choose device groups the same way. Smart groups appear with their names. Expand a group to see what's already blocked for it, and click Manage Group Blocklist to open the group's Applications tab in a new tab.
You can select devices, device groups, or both. Each device is counted once in Review, even if it's selected directly and through a group.
Step 4: Review
Before anything is saved, Review shows Your blocklist will apply to [N] devices, and what will be enforced on each.
Device summary
Each selected device is counted once, in one of these:
Summary | Meaning |
Devices ready | Every rule is enforced |
Devices needed action | Something must be installed before every rule can be enforced |
Devices with limited support | Some rules can't apply on these devices |
Devices not supported | No rules can apply on these devices |
What gets blocked
Everything in the queue, with each item's Blocklist Rule and Target OS:
Blocklist Rule | Meaning |
Installation | The app is blocked, as described in How apps are blocked |
Domain | The domain is blocked. See Block Domains and Filter Web Content. |
Domain · Block Sign Up Only | Users can visit the site, but can't sign up or sign in |
Click the pencil icon to go back and change the queue. Your selections are kept.
Device Scope and Device Group Scope
Device Scope lists each selected device, with its Rule Status and Rule Coverage, such as "1 of 4 will be enforced". Device Group Scope lists each selected group, with how many devices it has. Expand a group to see its devices.
Rule Status | Meaning |
Ready to Enforce | Every rule will be enforced |
Action Needed | Something must be installed first |
Limited | Some rules can't apply |
Not Supported | No rules can apply |
Expand a device to see What gets blocked on this device, with each rule's Enforcement:
Enforcement | Meaning | Example |
Ready | The rule will be enforced | — |
Waiting for setup | The rule needs something installed first. Click the button next to it. | "Requires Swif browser extension to be installed", with Deploy Extension |
Not supported | The rule can't work on this device | "App can't be blocked on Android", for a Mac app selected for an Android phone |
When you're done, click Apply to [N] devices. Click Back to change your device selection.
See and manage blocks
Where | What you see |
Device Inventory > [device] > Apps > Blocked | The device's blocks, in separate Blocked Applications and Blocked Domains tables, each with search, Allow All, and Add to Blocklist. Blocked extensions are listed too. Blocks from a device group show the group's name, such as via All Windows Devices. |
The app on the Applications page | The app's blocks, the devices and device groups they apply to, and their policies |
Device Groups > [group] > Applications | The group's blocks, separate from its apps, with target operating systems and, for Windows, the path. The group's apps are grouped into Swif Catalog Applications, Custom Applications, and VPP Applications. |
Each block shows the policy that enforces it, as a link. A chip shows how many rule types the policy has. Hover over it for details.
Unblock an app
To unblock | Where | How |
One app on a device | The device's Apps > Blocked | Click Allow next to the app |
Everything on a device | The device's Apps > Blocked | Click Allow All in Blocked Applications. Blocks from device groups stay. |
A block from a device group | The group's Applications tab | Click Allow on its row. It's removed from every device in the group. |
Blocks from a device group can't be removed on a device. Click the group's name, in via [group name], to open the group, and remove the block there.
Troubleshooting
An app isn't blocked on a Windows device
Check the app's Application path. Swif fills in
%PROGRAMFILES%\<app name>\*, which won't match an app installed somewhere else, such as in the user'sAppDatafolder. Enter the path where it's installed.Windows Store apps aren't covered by AppLocker blocks.
I see "Application path is required for Windows applications"
The Application path is empty, or doesn't end in .exe or \*. Enter the app's folder, ending in \*, or the full path to its .exe file.
An app still opens on a Linux device
This can be expected. On Linux, Swif closes blocked apps when the device next checks, about every 20 minutes, so the app can run until then. If it isn't closed at all, check that the name matches the app's process name exactly, with no spaces.
A macOS block affects other apps
On macOS, the block applies to every app whose name contains the name you entered. Use a more specific name.
An app isn't blocked on an Android device
Check the package name. For custom apps, it must match the app's package name exactly, such as
com.example.myapp.If the user installed the app themselves, it may stay on the device. Android removes blocked apps only if they were installed through a policy.
Review shows "App can't be blocked" for a device
The app's block doesn't apply to that device's operating system. For example, a Mac app can't be blocked on an iPad. For iPhone and iPad, use the Apple iOS/iPadOS Application Block Policy.
A blocked extension still works in one browser
Check that you chose that browser when adding the extension. Each browser has its own entry.
There's no Allow button for a block on a device
The block comes from a device group. Remove it from the group's Applications tab.
Blocked devices don't match my selection
Check the device and device group counts in Review. If they still don't match after saving, contact Swif support.
Related resources

