Device Settings
Overview
Device Settings provide tenant-level options for telemetry storage, live configuration checks, and app update enforcement. In the current portal, the Device Settings sidebar item is shown to Enterprise tenants.
Some settings affect runtime behavior and should be validated in Development and Staging before Production rollout.
Access Device Settings
- Log in to the AppTego Portal.
- Select the correct tenant.
- Choose the intended environment.
- Open Device Settings in the sidebar.
Available Settings
| Setting | Control ID | Plan in control catalog | Platform | Type | Purpose |
|---|---|---|---|---|---|
| Store IP Addresses | StoreIPAddress | Enterprise | Android, iOS | On/off | Store source IP addresses with device telemetry. |
| Store Approximate Location | StoreLocation | Enterprise | Android, iOS | On/off | Store approximate location context derived from IP address, such as country. |
| Store Device Information | StoreDeviceInformation | Enterprise | Android, iOS | On/off | Store basic device and OS information reported by protected apps. |
| Enforce Latest Configuration | EnforceLatestConfiguration | Enterprise | Android, iOS | On/off | Require apps to use the latest available live configuration. |
| Check For Configuration Updates | ConfigurationUpdateFrequency | Enterprise | Android, iOS | On/off | Allow protected apps to check for live configuration updates. |
| Enforce App Updates | EnforceNew | Team | Android, iOS | Response action | Respond when the app must be updated to a newer protected version. |
Although Enforce App Updates is a Team+ catalog control, the current Device Settings page itself is exposed in the Enterprise portal navigation.
Privacy And Telemetry Storage
The telemetry storage settings determine what is stored for future device events and device information records:
| Setting | When Enabled | When Disabled |
|---|---|---|
| Store IP Addresses | Device log records can include the source IP address seen by AppTego. | Device log records store NULL for IP address. |
| Store Approximate Location | Device log records can include approximate location context such as country. | Device log records store NA for country/location context. |
| Store Device Information | Device information records can include OS and version details. | Device information records store unknown for OS/version fields. |
Store Approximate Location depends on Store IP Addresses. If IP address storage is turned off, location storage is also turned off.
Live Configuration
Live configuration settings control how deployed protected apps check for and handle updated configuration:
- Enable Check For Configuration Updates before building and releasing the app.
- Build, test, and release the protected app with live configuration support.
- Update supported runtime settings in the portal.
- Use Push Latest Live Configuration to request that devices pick up the latest configuration.
Live configuration is useful for supported runtime settings. Build-time protection, structural changes, and some prevention behavior still require a new protected build.
App Update Enforcement
Enforce App Updates is a response-action control. Configure it the same way as other response controls: start with Log where appropriate, then move to Message, Redirect, or Terminate only after testing the user experience and operational impact.
Rollout Guidance
- Validate Device Settings in Development with internal devices first.
- Confirm privacy, security, product, and support teams understand the telemetry and user-facing behavior.
- Promote to Staging and run release-candidate testing.
- Promote to Production after testing launch behavior, configuration update behavior, and app update enforcement.
- Monitor Device Logs and support tickets after release.