Use Context-Aware Access with configuration groups

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

You can use configuration groups instead of organizational units in Context-Aware Access policies. Configuration groups can include users from any organizational unit in your business. For example, you can set up a policy to let a team of contractors access Gmail only on your corporate network.

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

How configuration groups work

  • Configuration groups can contain any users in your organization. You can use configuration groups in policies to target specific sets of users across organizational units.
  • A user can belong to multiple configuration groups, unlike organizational units. You set the priority of the configuration groups, and the user gets the setting of the highest priority group they belong to.
  • A configuration group in a policy always overrides an organizational unit in a policy.
  • If you don't use a configuration group in a policy, then the app uses the policy set for the user's organizational unit.

Design configuration groups for Context-Aware Access

Configuration groups work a little differently for Context-Aware Access compared to other Google Workspace settings. As you design your groups and policies, follow this information and the tips:

Options for configuration groups

You usually apply organizational units to policies and then apply configuration groups to policies for custom access. For example, you might have configuration groups for "Open access" or "Lockdown access" so you can quickly grant or limit specific users' access.

Typically, you'll use a combination of configuration groups:

Use your existing user groups

You apply your existing user groups to policies for each app, such as Gmail or Google Drive. If a user belongs to multiple groups, you set which group determines the user's settings, as described later on this page in the Priority section.

Applying existing user groups to policies is a good option for:

  • Testing Context-Aware Access.
  • Managing access for specific groups of users, such as IT staff or a team on remote assignment.
  • Managing access for organizations with fewer than 50 users or a small number of context conditions. You don't need to create more groups, and you can finely tune settings for each user group.

Create configuration groups based on policies

You create dedicated configuration groups and apply them to policies for one or more apps. Then, you add user groups as members of the configuration group.

Larger organizations might find this approach useful for managing access group policies and priorities, as described later on this page.

How priority works with policies

When a user belongs to multiple configuration groups, you set which configuration group has priority in determining the user's app access for the policy.

In the Google Admin console, you can view and edit the group priority list:

  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. In the Policies section, click View all policies.
  3. At the top, next to Create policy, click the Down arrow and select Edit group priority.
  4. Select an app to display its corresponding group priority list.

Groups are listed from highest to lowest priority. A new configuration group always has the lowest priority and is added to the bottom of the list.

Priority for Context-Aware Access

A user gets the app settings of the highest priority group they belong to. If the group is not included in a policy for a particular app, then the user's next highest priority group is evaluated, and so on.

In the Admin console, you can check which group or organizational unit determined a user's app policy. In the following example, the group Drive Security set the user's Drive access.

User's apps Context conditions applied Inherited from
Google Calendar Company network Organizational unit: Sales
Drive Company network, Device security Group: Drive Security
Gmail Device security Organizational unit: Sales
Google Vault <none> <none>

For fine-grained control, you can use groups to customize policies for each app. For example:

User's apps Context conditions applied Inherited from
Calendar Company network Organizational unit: Sales
Drive Company network, Device security Group: Drive Security
Gmail Device security, Geo Canada Group: North America
Vault Device restricted, Company network Group: Vault Investigator

Apply priority to configuration groups

  • Consider placing critical or sensitive configuration groups at high priority. For example, your top priority group might be an "Urgent Access" group that overrides any groups limiting access.
  • Policies aren't combined across a user's groups. In this example, a user belongs to 3 user groups, but only their highest priority configuration group, Device, determines their app access.

Planning and designing configuration groups

Planning your configuration group structure is likely the step that takes the most time and review.

Naming and searching for groups

Set a group naming standard for easier searching, prioritizing, and auditing. For example, add a prefix, such as caa, to indicate context-aware configuration groups. Also, use a decimal place to avoid editing your existing group names when you add a configuration group.

  • Search for a group—You might want to set up a naming standard that includes the setting name and priority number, for example:

caa_p0.0_unrestricted_access@example.com
caa_p1.0_lockdown_access@example.com
caa_p3.0_Gmail_IP_Device@example.com
caa_p3.1_Gmail_IP@example.com

  • View the groups—The Groups panel displays up to 37 characters of the group name in priority order. Pointing to a group shows the full name. For example:

CAA p0.0 - Unrestricted access all apps
CAA p1.0 - Lockdown access
CAA p3.0 - Gmail IP corp & device security
CAA p3.1 - Gmail IP corp

Ordering groups

To keep track of priority and settings:

  • You might place groups that apply to the fewest users or define critical policies, such as "Lockdown access" or "All access", at the highest priority.
  • Consider priority in your group structure and watch for deeply nested groups, which might be challenging to trace to settings.

Creating groups

You must use groups created in the Admin console, Directory API, or Google Cloud Directory Sync. Groups created in Google Groups can't be used as configuration groups. The Admin console doesn't show whether a group was created in Google Groups.

You can manage the configuration group in any tool. You might set strict permissions to add or delete users, turn off posting to the group, or use the Groups API to prevent users from leaving the group.

Set up configuration groups

Before you begin: Define the Context-Aware Access context conditions and create your configuration groups, preferably with one or 2 test accounts.

Step 1. Apply a configuration group to a policy

You need admin privileges for Groups, top-level Organizational Units, and Data Security Access level management and Rule management.

  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. In the Policies section, click View all policies.
  3. On the Policies tab, find the policy that you want to update.
  4. Next to the policy, click Action and then Edit policy.
  5. In the User conditions section, click Edit.
  6. Select Group and search for your configuration group.
  7. Click Save.

    For organizations with multiple types of Google Workspace licenses: Group policies apply only to users assigned a Google Workspace edition that includes Context-Aware Access control.

Step 2. Check the policies for a user

You need admin privileges for Groups, top-level Organizational Units, and Data Security Access level management and Rule management.

  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. In the Policies section, click View all policies.
  3. On the Policies tab, at the top of the table, click the User filter and enter the user's email address, not their name.
  4. Review the policies applied to the user. In the User conditions column, you can review the configuration group or organizational unit that determined the user's settings.
  5. Click Action and then View policy details for more information about the context conditions applied to the user.

Note: When you view an organizational unit, the Inherited levels are based only on an organizational unit's setting, not on configuration groups.

Remove a configuration group from a policy

You need admin privileges for Groups, top-level Organizational Units, and Data Security Access level management and Rule management.

  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. In the Policies section, click View all policies.
  3. On the Policies tab, find the policy assigned to the configuration group.
    Tip: At the top of the table, you can use the Group filter to quickly find the group.
  4. Next to the policy, click Action and select an option:
    • To remove the group but keep the policy—Select Edit policy and in the User conditions section, remove the group.
    • To delete the entire policy—Select Delete policy and confirm the deletion.
  5. Click Save.

The configuration group is removed from the policy. Changes can take up to 24 hours but typically happen more quickly. Learn more

Edit a configuration group in a policy

You need admin privileges for Groups, top-level Organizational Units, and Data Security Access level management and Rule management.

  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. In the Policies section, click View all policies.
  3. On the Policies tab, find the policy that you want to update.
  4. Next to the policy, click Action and then Edit policy.
  5. In the User conditions section, click Edit.
  6. Select Group and search for your configuration group.
  7. Click Save.
Changes can take up to 24 hours but typically happen more quickly. Learn more

Troubleshooting

I don't see the configuration group when searching

  • The group might have been created in Google Groups. Try creating a group in the Admin console.
  • Search for the group's email address rather than the group's name.
  • Try refreshing the setting page. Changes can take up to 24 hours but typically happen more quickly. Learn more
  • Check that you have admin privileges for Groups.

A user doesn't have the correct context condition applied

  • Check a user's group membership. Changes can take up to 24 hours but typically happen more quickly. Learn more
  • Find the configuration group that's determining the user's settings. If the user belongs to multiple configuration groups, you might need to change the group priority or user's group membership.
  • The user might not have the product license for the feature. Context-Aware Access is available with specific editions of Google Workspace.
  • If the user can't access an app, the policy might be referencing a deleted context condition. Check how to remove a deleted context condition.

Review changes in the log events

Review these events in the Admin log events for changes to configuration group settings:

EVENT: Context Aware policy App-specific Assignments Change

Logs when you apply or remove a configuration group in a policy. The event uses the group name, so you might use a similar naming standard for both your group name and address.

The data included in a group event:

Policy assignments have been changed from []
to [context conditions]. (application_name: {app}, group_name: {configuration group})

For example, you apply the configuration group CAA.02 local access to an app:

Policy assignments have been changed from [] to [Company IP, Device].
(application_name: {GMAIL}, group_name: {CAA.02 local access})

When you remove the configuration group from a policy targeting an app:

Policy assignments have been changed from [Company IP, Device] to [].
(application_name: {GMAIL}, group_name: {CAA.02 Local Access})

Understand organizational units and group inheritance

If you make any local policy changes in a child organizational unit or group, it has only the locally applied policies and doesn't inherit any policies from the parent organization.

If you remove all locally assigned policies to restore the originally inherited policies, the child organizational unit has only the inherited policies.

For example, for organizational units, if there are 3 policies assigned to an app in the top-level organizational unit, those same policies are assigned through inheritance to the app in a child organizational unit if the child organizational unit doesn't have a local assignment. If you then add a policy only in the child organizational unit, that's the only policy applied to the child organizational unit.

Override inherited policy assignments with a null policy

Suppose that you want a child organizational unit to have no policy assignments so that user access isn't blocked. You can create a context condition with the advanced expression true and apply it in a policy. For details, go to Define context conditions in Advanced mode.

Override policy assignments with configuration groups

You can use configuration groups in policies to target specific groups of users rather than organizational units. A user's group policy always overrides the user's organizational unit policy. The groups can include users from any organizational unit in your account.

For example, a user belongs to an organizational unit and Group1. The organizational unit is ParentOU, which has access policy X assigned for both Gmail and Calendar. There is no policy assignment for Group1 for Gmail. There is an access policy Y assigned for Group1 for Calendar. In this case, the user gets access policy X for Gmail through inheritance and access policy Y for Calendar because the group policy overrides the organizational unit policy.