MDM Configuration

The app can be centrally configured through any Mobile Device Management (MDM) provider — Microsoft Intune, Workspace ONE, Jamf, SOTI, MobileIron, and others. This lets an organization pre-set certain app behaviour for its devices, rather than leaving it to each user.

No special setup is needed in the app itself: it reads whatever configuration your MDM provider pushes to the device, using the standard mechanism each platform already provides (Android Managed Configurations and Apple Managed App Configuration). Configure the app the same way you would configure any other managed app in your MDM console.

Configuration is read when the app starts. A setting pushed to a device while the app is already running takes effect the next time it is launched.

What can be configured

All settings below are optional — anything left unset stays under the end user’s own control.

Setting	Effect
Enforced project	Pins a specific project as the one the device always opens, and prevents that project from being removed from the app. Useful for organizations that want every device to be tied to a single, known project.
Anonymous mode	Forces the "Anonymous mode" conversation setting on or off for every user.
Conversation mode	Forces how the user talks to the avatar: Natural (always listening), Take Turns (microphone mutes automatically while the avatar is speaking), or Push to Talk (the user holds a button to speak).

Setting

Effect

Enforced project

Pins a specific project as the one the device always opens, and prevents that project from being removed from the app. Useful for organizations that want every device to be tied to a single, known project.

Anonymous mode

Forces the "Anonymous mode" conversation setting on or off for every user.

Conversation mode

Forces how the user talks to the avatar: Natural (always listening), Take Turns (microphone mutes automatically while the avatar is speaking), or Push to Talk (the user holds a button to speak).

There are also a couple of advanced, support-oriented settings (such as forcing debug log uploads) intended for troubleshooting with your Promethist contact rather than everyday administration.

How it behaves in the app

Any setting you enforce is greyed out on the user’s Settings screen, so it’s visible but can’t be changed.
The enforced project (if configured) appears in the user’s project list as soon as the app is first opened — even before it has a network connection — and its "remove" option is hidden.
If you later remove or change a pushed setting, the app reverts to letting the user control it again on their next launch.
An invalid configuration value (for example, a project link that doesn’t exist) is simply ignored — it will never prevent the app from starting.