Organization restrictions let you prevent data exfiltration from
Google Cloud through phishing or insider attacks. For managed
devices in your organization, this feature restricts access only to resources in
authorized Google Cloud organizations.

## How organization restrictions works

In Google Cloud, Identity and Access Management (IAM) governs access to resources.
Administrators use allow and deny policies to control who can access the
resources within their organization. There is a need in organizations to
restrict access of their employees only to resources in authorized Google Cloud
organizations. Google Cloud administrators who administer Google Cloud, and
egress proxy administrators, who configure the egress proxy, engage together to
set up organization restrictions.

The following diagram illustrates how the different components work to enforce organization restrictions:

![Organization restrictions workflow](https://docs.cloud.google.com/static/resource-manager/docs/organization-restrictions/images/org-restrictions-diagram.svg)

The architecture diagram shows the following components:

- **Managed device**: A device that is governed by the organization policies of
  a company. Employees of an organization use a managed device to access the organization
  resources.

- **Egress proxy**: An egress proxy administrator configures
  the proxy to add organization restrictions headers to any requests originating
  from a managed device. This proxy configuration prevents
  users from accessing any Google Cloud resources in non-authorized Google Cloud organizations.

- **Google Cloud**: The organization restrictions feature in Google Cloud inspects all requests
  for organization restrictions header, and allows or denies the requests based on
  the organization being accessed.

## Common use cases

Here are some common organization restrictions use cases:

- Restrict access to employees in your organization so that employees can
  [access resources only in your Google Cloud organization](https://docs.cloud.google.com/resource-manager/docs/organization-restrictions/examples-org-restrictions.md.txt#access-your-org)
  and not other organizations.

- [Allow your employees to read from Cloud Storage resources](https://docs.cloud.google.com/resource-manager/docs/organization-restrictions/examples-org-restrictions.md.txt#access-read-org)
  but restrict employee access only to resources in your Google Cloud organization.

- [Allow your employees to access a vendor Google Cloud organization](https://docs.cloud.google.com/resource-manager/docs/organization-restrictions/examples-org-restrictions.md.txt#access-vendor-org) in addition
  to your Google Cloud organization.

Implementing these use cases require engagement between Google Cloud administrators,
who administer Google Cloud, and egress proxy administrators who configure the egress proxy.

## What's next

- Learn about [organization restrictions configuration](https://docs.cloud.google.com/resource-manager/docs/organization-restrictions/configure-organization-restrictions.md.txt).
- Learn about the [services supported by organization restrictions](https://docs.cloud.google.com/resource-manager/docs/organization-restrictions/supported-services.md.txt).