Sideload an app into a work profile
Sideload an app into a work profile. Explain how to set up an Android work profile and install an APK exclusively inside it.
A work profile creates a separate, encrypted space on your Android device for specific apps. When you sideload an app into the work profile, its data, permissions, and notifications remain isolated from your personal profile. Setting up the profile, transferring an APK into it, and completing the sideload takes a few deliberate steps, and removing the profile cleanly is straightforward when it is no longer needed.
Sideload an app into a work profile: Before you start: Requirements
Your device must be running Android 5.0 (API level 21) or higher (Android Developers, 2026). The work profile feature is built into stock Android and most manufacturer skins (Samsung, Pixel, Motorola, OnePlus). Some manufacturers (Xiaomi, Oppo, vivo) may hide the option or require a work profile to be created via an MDM app; check your Settings app for “Work profile” or “Work” under Accounts.
You need the APK file you want to install. The source of the APK determines the risk. Only download from the developer’s official website or a trusted repository that verifies signatures (such as F-Droid). Do not use random forums or unofficial aggregators.
Step 1: Create a work profile
- Open Settings > Accounts (or Users & accounts).
- Tap Add account or Add work profile (exact wording varies).
- Follow the on-screen prompts to set up a work profile. You will be asked to allow a Device Policy Controller (DPC) app. On most devices, Android itself acts as the DPC. Accept the policies.
- The work profile appears in your app drawer with a briefcase icon badge on work apps (Android Developers, 2026). A persistent notification may show “Work profile is turned on.”
If your device does not show a “Work profile” option, you can install a DPC app from Google Play (such as “TestDPC” or “Managed Work Profile”) and use it to create the profile. On Android 8.0+, you can also create a work profile through Settings > Security > Work profile.
Step 2: Enable APK installation inside the work profile
The work profile has its own “Install unknown apps” permission list, separate from the personal profile (Android Developers, 2026). You must grant this permission to a file manager app that runs inside the work profile.
- Open the Play Store inside the work profile (you can find it by the briefcase badge). Install a file manager app (e.g., “Files by Google” or “Solid Explorer”) if one is not already present.
- Go to Settings > Apps > Work apps (or Work profile > App management). Find the file manager app.
- Tap Install unknown apps (or Allow from this source) and toggle it on.
If you plan to install the APK via ADB (Android Debug Bridge), you do not need to enable this permission. The ADB method bypasses the unknown sources prompt.
Step 3: Transfer the APK to the work profile
You have two reliable methods.
Method A: Using a file manager inside the work profile
- On a computer, download the APK file.
- Connect your phone via USB and enable File Transfer (MTP). Your computer should show two storage volumes: “Internal shared storage” and “Work” (or the work profile user name). Copy the APK into the “Work” volume.
- Disconnect the phone. Open the file manager app inside the work profile (the briefcase-badged version). Navigate to the APK file and tap it to begin installation.
Method B: Using ADB (Android Debug Bridge)
This method works without enabling unknown sources and is useful if the file manager approach fails.
- Enable Developer options on your phone: go to Settings > About phone > tap Build number 7 times.
- In Developer options, enable USB debugging.
- On your computer, install ADB (part of the Android SDK platform tools). Open a terminal or command prompt.
- Connect your phone via USB and authorize the ADB connection.
- The work profile runs as a separate user. On most devices, the work profile user ID is 10 (Android Developers, 2026). To confirm, run:
adb shell pm list users. Look for a user with “profile” or “work” in the description. - Install the APK into the work profile:
adb install –user 10 path/to/app.apk - The app appears in the work profile app drawer. You can verify by checking the briefcase badge.
Step 4: Verify isolation
- Data separation: The app’s files reside in
/storage/emulated/10/(or equivalent work profile user directory), which is encrypted with a separate key (Android Developers, 2026). - Permissions: Runtime permissions granted to the work app do not apply to personal apps, and vice versa (Android Developers, 2026). For example, if you grant camera access to the work app, it will not give camera access to personal apps.
- Notifications: Work app notifications appear in a dedicated “Work” section of the notification shade (Android Developers, 2026). You can mute them independently.
- VPN and network: A VPN configured inside the work profile applies only to work apps (Android Developers, 2026). Personal traffic remains unaffected.
- Clipboard: By default, the clipboard is shared between profiles. The DPC can restrict this; if your DPC supports it, you can enable clipboard isolation.
Step 5: Update the sideloaded app
Sideloaded apps inside a work profile do not receive automatic updates from Google Play. To update, you must repeat the sideload process with a new APK that has a higher versionCode (Android Developers, 2026). If the APK signature of the update does not match the original, the install will fail with “App not installed.”
Step 6: Remove the work profile
Removing the work profile deletes all apps, data, accounts, and settings inside it. The personal profile is unaffected (Android Developers, 2026).
- Go to Settings > Accounts > Work profile (or Remove work profile).
- Tap Remove work profile (or Delete). Confirm.
- All work profile data is wiped. No residual files remain in personal storage (Android Developers, 2026).
Alternatively, you can pause the work profile without removing it: Settings > Accounts > Work profile > Pause work apps (Android Developers, 2026). Pausing disables all work apps and notifications temporarily.
Decision checklist
| Situation | Recommended method |
|---|---|
| APK from developer’s site, one-time install | File manager inside work profile |
| Multiple APKs, automate installs | ADB with –user flag |
| No work profile option in Settings | Install a DPC app from Play Store |
| App not installing (signature error) | APK must match the original signer; download from official source |
| Want to keep work profile but stop apps | Pause work profile instead of removing it |
What isolation does not guarantee
A work profile isolates app data and permissions from the personal profile, but it does not protect against all threats. The APK itself must be from a trusted source. If the APK contains malware, that malware runs inside the work profile and can still access the internet, send data, or abuse granted permissions within the work profile. The Android Open Source Project (AOSP) documentation notes that the work profile provides separation, not a security sandbox for malicious code (Android Developers, 2026). Always verify the APK signature and source before installing.
How to install an APK in a work profile and keep it isolated
The core technique for an Android managed profile sideload is straightforward once the profile exists: place the APK file where only the work profile can see it, then launch the package installer from inside that profile. Every method that follows respects the same isolation boundary.
Choose a transfer method that respects the profile boundary
Copying the APK into the “Work” volume via MTP or pushing it with ADB using the –user flag both place the file inside the work profile’s encrypted storage. Avoid downloading the APK in the personal profile and then moving it across, because that briefly exposes the file outside the work boundary and may leave copies in personal storage.
Grant the install permission to exactly one work-profile file manager
The “Install unknown apps” toggle is per-app and per-profile. Grant it only to the file manager you will use to launch the APK, and revoke the permission afterward if the device is shared or managed by an organization. This keeps the attack surface small.
Confirm the briefcase badge before you open the app
After any sideload, open the work-profile app drawer and check that the new app carries the briefcase badge. If the badge is missing, the app may have landed in the personal profile. Uninstall it immediately and repeat the sideload, double-checking the target user or storage volume.
Understand what “isolate sideloaded app Android” actually means
Isolation operates at the kernel level. The work profile runs as a separate Linux user ID, with its own filesystem mount, app data directories, and permission grants. A sideloaded app inside that profile cannot read personal contacts, photos, or files unless you explicitly copy them across the boundary. It also cannot see the list of personal apps or intercept their intents. This is the same mechanism that enterprise device management relies on, and it is documented in the Android compatibility definition (Android Developers, 2026).
Install and update safely without Play Store automation
Because the Play Store inside the work profile will not manage sideloaded apps, you need a repeatable update habit. Subscribe to the publisher’s release feed or repository changelog, download each new APK to a computer, verify its signature against the installed version, and push it with the same method you used for the initial sideload. Keeping a small text file with the current versionCode and SHA-256 fingerprint inside the work profile makes verification quick.
Decide between a persistent work profile and a temporary sandbox
Some people use the work profile as a permanent home for a handful of trusted apps. Others create it, sideload one app for a short-term task, and remove the profile when the task ends. Either pattern works. If you choose the temporary approach, pause the profile first to confirm no work app is still needed, then remove it. The pause step catches overlooked dependencies before data is wiped.
Frequently Asked Questions
Can I use ADB without enabling unknown sources?
Yes. ADB installation uses a developer command and does not require the "Install unknown apps" toggle to be on. You must enable USB debugging in Developer options.
What happens to work profile apps when I factory reset the phone?
A factory reset removes the work profile and all its data. The work profile is not protected by Factory Reset Protection (FRP) (Android Developers, 2026).
Can I install an APK that targets an older Android version?
Android 14 blocks installation of APKs with targetSdkVersion below 23 (Android Developers, 2023). Android 15 is expected to require targetSDK 24 minimum (Android Developers, 2024). If the APK is too old, you must find a newer version.
How do I know the work profile is active?
Work apps display a briefcase icon badge in the app drawer (Android Developers, 2026). A persistent notification may also show "Work profile is turned on." You can check the status in Settings > Accounts > Work profile.
Read next
-
How to install an APK safely
Installing an APK outside your device’s default app store is called sideloading.
-
Split APK installation explained
Modern Android apps rarely arrive as a single APK file. Since 2021, Google Play has required new apps and app updates to use the Android App Bundle (AAB) format.
-
Update a sideloaded app
When you add an app from outside the Google Play Store, keeping it current works differently from tapping "Update” in the Play Store.
-
Uninstall and clean up
Uninstalling an Android app and cleaning up what it leaves behind are separate tasks.
-
Permissions and privacy
Android controls what every app can reach. By default an app cannot read your contacts, see your location or open your files.