This guide is to inform customers of the recommended configurations and settings within Jamf for a successful NavvTrack deployment.
All phones that will be monitored with NavvTrack should be enrolled in your Mobile Device Management (MDM) solution. MDMs extend NavvTrack’s management capabilities with important tools that allow users to get the most value from the system.
Mobile Device Group Setup
All shared mobile devices should be placed into Groups so they can be logically viewed within NavvTrack. These groups typically define the campus and department to which the device belongs, but may also include additional information such as:
• Floor
• Shared Team
• Shared Campus
The MDM Groups will map to Teams in NavvTrack, which allow Team Managers to view assets they are responsible for in real time.
Example naming convention: campus-department i.e. oakgrove-evs
API Requirements
NavvTrack requires access to your Jamf instance’s API to enable Lost Mode and access Team information.
You will need to create an admin or properly privileged user for Navv in your MDM.
App Deployment
NavvTrack will leverage your Apple Business/Apple School Organization ID to make the Navv app available in your private app store. Once the app is available, the Navv team will reach out and provide you with your organization’s App Configuration, which will need to be added in the Jamf App deployment.
The following is a table of recommended configuration preferences for use of NavvTrack with shared devices. Some of these options may not be available for your specific MDM. Bolded Settings are important for ensuring the best performance of the NavvTrack app and platform.
Moving Devices Between Groups
When a device is moved to a new group associated with a NavvTrack team, the NavvTrack application will need to be terminated and relaunched on the device. To terminate the application, swipe up the app to fully close it. Upon relaunching the application, the device will receive the information about its new team and will be ready for use.