Explore practical examples of how to deploy MANAGED INFO for different use cases. These serve as inspiration when defining your own managed configuration.
Goal: Provide IT support, contact details, and a helpful message.
Recommended config:
“If you need assistance, please contact IT Support via the details below. We're here to help with any device or access issues.”
Ideal for: Front-line staff, field engineers, hybrid employees.
Goal: Show device asset ID, organisation details, and support info only.
Recommended config:
“Asset # '$variable$'”
Ideal for: Shared tablets, unmanned kiosks, digital signage requiring declaration of ownership.
Goal: Present a grid of approved applications with friendly labels.
Recommended config:
,,
Ideal for: Company devices, training tablets, role-based deployments, logistics, warehousing
Goal: Highlight an app with an explainer or warning.
Recommended config:
Example:
“Use Google Drive to access shared documents. You’ll need your work email address.”
Ideal for: New user onboarding, app-based workflows, policy comms.
Goal: Prevent access to all but minimum required apps outside of permitted times.
Recommended config:
# Time's up \n\n It's time to take a break, little man. \n\n Pop the device on charge and find something else to do. \n\n *The below apps are available, if needed*
"Ideal for: Provisioning context, lost device info, device setup testing.
Goal: Provide only a single message or action.
Recommended config:
Ideal for: Provisioning context, lost device info, device setup testing.
Have your own configuration or use case you'd like featured? Contribute to the tracker or join the BAYTON Discord to share and explore others.
Are you in need of further help, or would you like to raise a feature request? You can: