# Personnel data access and support controls

This page provides information about personnel data access in
Assured Workloads, which provides control over Google personnel's
access to Customer Data and support case assignments. Assured Workloads
provides the following controls based on the
[control package](https://docs.cloud.google.com/assured-workloads/docs/control-packages.md.txt) you choose:

- [Personnel data access controls](https://docs.cloud.google.com/assured-workloads/docs/personnel-access-data-controls.md.txt#data-access)
- [Personnel support case ownership controls based on attributes](https://docs.cloud.google.com/assured-workloads/docs/personnel-access-data-controls.md.txt#ownership-attributes)
- [Organization-level personnel controls](https://docs.cloud.google.com/assured-workloads/docs/personnel-access-data-controls.md.txt#olpc) ([Preview](https://cloud.google.com/products#product-launch-stages))

> [!IMPORTANT]
> **Important:** Don't include confidential, sensitive, or personally identifiable information in project names, project IDs, resource names, or other resource fields. Unless otherwise noted in the documentation or [service specific terms](https://cloud.google.com/terms/service-terms) for a supported product or service, data included in these fields doesn't constitute Customer Data, and is out of scope for Assured Workloads' personnel data access controls.

### Personnel data access controls

Personnel data access controls ensure that only Google personnel who are able to
satisfy certain physical location and background check requirements are able to
access customer data in the course of a support action. For example, Impact
Level 4 (IL4) requires US Persons to have completed an ADP-1 Single Scope
Background Investigation (SSBI) background investigation before they can access
data in an approved IL4 environment.

### Personnel support case ownership controls based on attributes

Personnel support case ownership controls based on attributes ensures that only
Google support personnel who satisfy certain requirements are assigned to
support cases for Assured Workloads customers.

### Organization-level personnel controls

> [!WARNING]
>
> **Preview**
>
>
> This product or feature is
>
> subject to the "Pre-GA Offerings Terms" in the General Service Terms section
> of the [Service Specific
> Terms](https://docs.cloud.google.com/terms/service-terms#1).
>
> Pre-GA products and features are available "as is" and might have limited support.
>
> For more information, see the
> [launch stage descriptions](https://cloud.google.com/products/#product-launch-stages).

While Assured Workloads folders and Assured Workloads frameworks enforce personnel controls
on folders and projects, some Google Cloud services maintain resources at the
organization root, such as Security Command Center and Workforce Identity Federation. For
[Data Boundary for Impact Level 5 (IL5)](https://docs.cloud.google.com/assured-workloads/docs/control-packages/il5.md.txt),
you configure an
[organization-level personnel control (OLPC) mode](https://docs.cloud.google.com/assured-workloads/docs/olpc-mode.md.txt)
to apply US Persons administrative access and support routing controls to
organization-level resources and to define which workloads can be created in
your organization.

## What's next

- Learn how to [configure organization-level personnel controls (OLPC)](https://docs.cloud.google.com/assured-workloads/docs/olpc-mode.md.txt).
- Learn how to [create an Assured Workloads folder](https://docs.cloud.google.com/assured-workloads/docs/create-folder.md.txt).
- Learn which [products are supported](https://docs.cloud.google.com/assured-workloads/docs/supported-products.md.txt) for each control package.