Default vs Custom SDK Profiles

When you configure your application, you select a custom or a default application profile. This action applies an SDK profile to the application, giving deployed Workspace ONE UEM applications additional features.

To ensure your application configuration runs smoothly, it is helpful to:

  • Know the difference between a Custom and Default SDK profile.
  • Determine if a Custom or a Default SDK profile is more appropriate for your application.
  • Ensure you have configured the SDK profile type that you want to apply.

Use the following chart to determine if you want to apply a Default or Custom SDK profile to your application, and to direct you to the configuration instructions for the profile you use.

You can define SDK profiles using two different profile types: Default or a Custom SDK application profile.

  Default Custom
Implementation Share SDK profile settings across all applications set up at a particular organization group (OG) or below. Apply SDK profile settings to a specific application, and override the Default Settings SDK profiles.
Advantage Provides a single point of configuration for all of your apps in a particular OG and its child groups. Offers granular control for specific applications and overrides the Default Settings SDK profiles.
Configure Groups & Settings > All Settings > Apps > Settings and Policies > Security Policies Groups & Settings > All Settings > Apps > Settings and Policies > Profiles
Read More Continue reading this section to learn which default SDK profiles apply to deployed apps. Learn more about custom SDK profile settings in the VMware Workspace ONE UEM Mobile Application Management Guide.