Manage apps and extensions

Use Business+ → Apps & Extensions for signed-in users and managed guest sessions. Use Kiosk → Apps for kiosk auto-launch and kiosk apps.

Choose the correct scope

Target	Console location
Managed users and browsers	Business+ → Apps & Extensions → Users & Browsers
Managed guest sessions	Business+ → Apps & Extensions → Managed Guest Sessions
Kiosk devices	Kiosk → Apps
Private APK library	Private Android Apps

The Kiosk tab under Business+ is a pointer to Kiosk → Apps; it is not a separate app list.

Add an app for users or managed guest sessions

1. Open Business+ → Apps & Extensions.
2. Select Users & Browsers or Managed Guest Sessions.
3. Select the target Organisational Unit.
4. Click Add.
5. Choose Chrome app or extension, IWA app, Web app, or Android app.
6. Select the app and set its Installation Policy.
7. Review the list and click Save.

The current console includes policies such as:

• Allow Installation
• Block
• Force install + pin to taskbar
• Force install + pin to toolbar

Available choices depend on the app type and target.

Change or remove an app

1. Select the correct tab and organisational unit.
2. Change the Installation Policy, or click Delete for the app row.
3. Review Unsaved Changes.
4. Click Save.
5. Verify removal or policy change on a pilot device.

Deleting a row removes its managed configuration from that scope. Whether an already installed app remains depends on its installation policy and device state; test before broad rollout.

Add a kiosk app

1. Open Kiosk → Apps.
2. Select the target organisational unit.
3. Click Add.
4. Choose:
   • Chrome app or extension
   • Add web apps
   • Add Android kiosk from private apps
   • Add recommended apps
5. Add the app.
6. In the Auto-Launch App row, select the one app that should launch when the kiosk starts.

Upload a private Android app

1. Open the top-level Private Android Apps page.
2. Click Upload App.
3. Select or drag an APK file. The current uploader accepts APK files up to 1 GB.
4. Continue to App Information, review the detected metadata, and finish the upload.
5. Return to the relevant app policy page and add the private app to users or kiosks.

Use Update to upload a newer build of an existing private app. Confirm package identity and version before updating; changing the package name creates a different app.

Manage global app permissions

Click Other Settings on the Users & Browsers tab to configure:

• Chromium and Android allow/block mode.
• Allowed app and extension types.
• App and extension installation source URL patterns.
• Insecure or external extension handling.
• Permissions extensions are not allowed to request.
• Runtime blocked and allowed hosts.
• Whether the Chrome Web Store icon is shown.

These settings can affect many apps at once. See Manage App Permissions and Sources before changing them.

Verify deployment

1. Use a pilot organisational unit.
2. Keep the test device online.
3. Confirm that the app appears and its installation policy is correct.
4. For a kiosk, restart the device and confirm that the selected auto-launch app opens.
5. Expand the policy only after the pilot succeeds.

If an app does not appear

• Confirm the correct tab and organisational unit.
• Confirm that you clicked Save where the page requires it.
• Check that the device and user are in the expected units.
• Check app compatibility with the device and FydeOS version.
• For a private APK, confirm that upload completed and the expected package/version is listed.
• Check Other Settings for an allow/block mode, app type, source, permission, or runtime-host rule that prevents the app from operating.

What's next

• App permissions and sources, control what managed apps can install or access.
• Configure user policies, apply related browser settings.