This article explains the key capabilities of the Shadow IT → Manage Blocklist experience in Swif, based on the consolidated blocking flow introduced in the “Shadow IT – Manage Blocklist” update.
Use this when you want to quickly block risky applications or domains discovered in Shadow IT across specific devices or device groups.
1. Launching the Manage Blocklist modal
From the Shadow IT report or Device Details → Applications:
Select an application.
Click Manage Blocklist.
What happens:
The Manage Blocklist modal opens with:
The selected application pre‑filled.
Application name and primary domain pre‑filled when coming from Shadow IT (e.g., selecting TeamViewer pre-fills
TeamViewerandteamviewer.com).
You can still adjust other options (devices, device groups, domains, etc.) and add multiple entries to a blocklist queue.
2. OS‑aware blocking: Windows vs macOS/Linux
Windows – block by application path
For Windows devices, application blocking is enforced by file path.
When the target OS includes Windows:
The UI shows an Application path (or
appPath) input.Placeholder text clearly indicates a Windows path format (e.g.
C:\Program Files\App\app.exe).
Result:
Windows devices in scope will be blocked using the configured path.
macOS / Linux – block by application name
For macOS and Linux devices:
You can block by application name only, no path required.
The name you enter (or that’s pre-filled) is used directly by the policy.
3. Choosing the application: Known apps vs Custom app
The Manage Blocklist modal supports two ways of specifying apps:
a. Select from Known Apps
Use this when the app exists in Swif’s Applications Catalog.
As you type, you’ll see matching apps.
This is typically what you get when starting from a Shadow IT entry.
b. Enter Custom Application Name
Use this when the app is not in the catalog.
You see a simple input box (not an always-open dropdown).
Placeholder / guidance text:
“Type an Application Name / Domain and Press Enter”
The dropdown only appears after you type and there is a match, avoiding confusion with the known app selector.
c. Smart hide/show behavior
To keep the UI focused and reduce clutter:
When Select from Known Apps is chosen:
The custom application name input is hidden.
When Enter Custom Application Name is chosen:
The known-app dropdown is hidden.
Only one input method is visible at a time, making it clear which mode you’re using.
4. Blocking by domain – manual entry or file upload (web filtering)
You can also block usage at the domain level.
a. Domain input vs file upload
When you choose Domain as the block type:
Option 1: Enter Domain
Use the same guided placeholder:
“Type an Application Name / Domain and Press Enter”
Option 2: Upload a file of domains
Upload a file containing multiple domains.
The interface shows:
The file name
The number of domains in the file (instead of listing thousands of domains).
A visual “OR” spacer sits between manual domain entry and file upload, making it clear you’re choosing one method or the other.
b. Smart hide/show behavior for domains
To keep the domain flow clean:
If you select Enter Domain:
The file upload option is hidden.
If you select Upload file:
The manual domain input is hidden.
Again, only one domain input method is shown at a time.
5. Device and device group selection
You can target your blocklist to:
Specific devices
Specific device groups
(Depending on your setup) all devices matching your criteria
Key behaviors:
The device selection dropdown includes all enrolled devices (per QA scenarios).
Device groups can be created/selected with arbitrary names, which are displayed correctly.
Bulk selection is supported for quickly applying policies across many endpoints.
6. Blocklist queue and bulk actions
As you configure blocks, entries are added to a blocklist queue in the modal.
Capabilities:
Add multiple apps and domains before saving:
e.g., block an app by name on macOS and by path on Windows, plus relevant domains.
Perform bulk actions:
Select multiple apps/domains and apply blocking in one go.
The queue reflects:
App name or domain
Target OS and devices/device groups
Path (for Windows app blocking)
Block type (app name vs domain, etc.)
7. Blocklist display on Device Details → Applications
After saving, you can see how blocklists apply at the device level in Device Details → Applications.
a. How domain entries are shown
For domains added via file upload:
The UI shows the file name and a count of domains.
Individual domains are not all listed when there are large numbers, to keep the view readable.
b. Policy block type and usage
Each block entry includes:
Application Name
The string you typed or selected as the app name.Block Type
Indicates how the block is applied (by app name, domain, etc.), and:Shows usage via Policy Name.
The policy name is a link to the specific policy, so you can jump directly to it.
c. Rule type chip and tooltip
In blocklist/usage tables:
A chip shows how many rule types (e.g., app, domain, OS variants) a policy has.
Hovering over the chip opens a tooltip with rule-type details.
This gives quick insight into how broad or granular a policy is without having to open it.
8. Consistent behavior across entry points
The Manage Blocklist flow is designed to behave the same from multiple starting points:
From Shadow IT → Manage Blocklist
From Device Details → Applications → Manage Blocklist
In all entry points:
The modal layout and steps are consistent.
The pre-selection reflects your context (e.g., app from Shadow IT vs app on a specific device).
All features described above (OS handling, known/custom app, domains, bulk actions, tooltips) work in the same way.