Use case: Device policy enforcement

Supported editions for this feature: Frontline Standard and Frontline Plus; Enterprise Standard and Enterprise Plus; Education Standard and Education Plus; Enterprise Essentials Plus; Cloud Identity Premium. Compare your edition

This example shows you how to create a Context-Aware Access context condition for device requirements and then enforce it across your apps using a policy.

Note: Context conditions were previously referred to as access levels in the Google Admin console.

Before you begin

  • For Workspace-only users—We recommend that you do not add or modify Context-Aware Access context conditions using the Google Cloud console. Doing so can cause this error: Unsupported attributes are being used on Google Workspace and block users.
  • For users on Windows—To improve the security of Chrome data, ensure that the Google Chrome Elevation Service remains turned on for App-Bound Encryption.

Configure device policy enforcement

  1. In the Google Admin console, go to Menu and then Security and then Access and data control and then Context-Aware Access.

    Requires the Data security access level and rule management privileges and the Admin API groups and users read privileges.

  2. For Policies, click View all policies.
  3. At the top, next to Create policy, click the Down arrow and select Create context condition.
  4. For Details, enter a Context condition name, such as Device policy for Finance, and an optional description.
  5. On the Basic tab, click Add condition.
  6. Add the following attributes:
    • Device—Screen password protected
    • Device OS—iOS 9.10.0
    • Device OS—Android 8.0.0
  7. Click Create condition. You return to the Context conditions tab on the Policies page.
  8. Click Create policy.
  9. For Policy status, at the top of the page, choose an option:
    • To assess a policy's impact on users before implementing the policy, select Monitor.
    • To enforce the policy immediately, select Active and then for Action, select Block or Warn.
  10. For User conditions, select the organizational unit or group you want to apply the policy to.
  11. Click Save.
  12. For Context conditions, click Edit and select the context condition you created earlier, such as Device policy for Finance.
  13. Click Save.
  14. For Apps, click Edit and select the apps for users to access. Do not assign the policy to the Google Admin console.
  15. Click Save.
  16. For What will this policy do?, review the policy summary generated by your selections.
  17. (Optional) To update components, next to a section, click Edit.
  18. Click Create policy.

Verify policy assignment

To verify that your policy is properly configured:

  1. In the Google Admin console, go to Menu and then Security and then Access and data control and then Context-Aware Access.

    Requires the Data security access level and rule management privileges and the Admin API groups and users read privileges.

  2. Click View all policies.
  3. Confirm that your policy has the following settings:
    • The correct organizational unit or group for User conditions.
    • The assigned Apps and Context conditions.
    • A Status set to Active or Monitor.

Customize user remediation messages

To customize the messages users receive when app access is blocked:

  1. In the Google Admin console, go to Menu and then Security and then Access and data control and then Context-Aware Access.

    Requires the Data security access level and rule management privileges and the Admin API groups and users read privileges.

  2. For General settings, click View settings.
  3. Configure your message preferences:
    • Remediation messages—System-generated messages corresponding to the specific policy violation that blocked access. These offer self-serve options so users can unblock themselves.
    • Custom messages—Specific guidance or help links provided by your organization.
    • Default message—Displays if no remediation or custom message is configured.

For more details, go to Allow users to unblock apps with remediation messages in Context-Aware Access.