Add a Data Session Policy to a Network Feature

The policy events in a data session policy are evaluated whenever there is a network transition event or when the optionally defined trigger occurs.

1. Click Add Policy > New Data Session.
2. Click on the policy name to change it from the default name. (Give it a meaningful name. This will help you find the policy when you are choosing from lists of policies.)
3. If you want to add exceptions to the blocking rule that would allow data sessions, select one or more as criteria in the Default Policy Event:
   • Screen On & Internet App in Foreground
   • Screen On
   • Streaming Media
   • Downloading

   To add any of these to the Default Policy Event, click Criteria, then click the one you want to add. If you did not already change it, the policy event action becomes Allow. If you add multiple criteria, any one must be true when the policy is evaluated to open a data session.

   Screen On & Internet App in Foreground and Screen On are mutually exclusive options. If you add one of these to the Default Policy Event, the other is no longer available to be added.
4. Add a Network Group. 

   In Block Network Groups, click Add  , then click From Library to use an already defined network group (the recommended option) or New to create a new network group.

   • From Library (preferred): In the Network Group list, select a network group, and then click Add.
   • New: See Add a Network Group for details on creating new network groups. (Too many ad hoc network groups can be difficult to manage. Use existing network groups whenever possible.)
   You cannot add network groups to the In section that are already in the Not In section, and vice versa.
5. Optionally select a Trigger in Policy Settings. A trigger is a user-initiated event that causes the policy event to be evaluated. Choose from:
   • Screen Turn On (least cost savings): Policy is evaluated when the device screen is turned on.
   • Device Unlock: Policy is evaluated when the device is unlocked.
   • Internet App Brought to Foreground: Policy is evaluated when any app that can access the Internet is brought to the foreground.
   • None (most cost savings): Policy will always be evaluated.
   Note that there is an inverse relationship between cost savings and customer experience, specifically, the availability and readiness of the device's data connection.