| [ Web Proxy ] |
| Viewing: https://developers.cloudflare.com/cloudflare-one/traffic-policies/tiered-policies/organizations/ | [Back] [Original] |
Note
Only available on Enterprise plans.
Gateway supports using Cloudflare Organizations to share configurations between and apply specific policies to accounts within an Organization. Tiered Gateway policies with Organizations support DNS, network, HTTP, and resolver policies.
For a DNS-only deployment using the Tenant API, refer to Tenant API.
To set up Cloudflare Organizations, refer to Create an Organization. Once you have provisioned and configured your Organization's accounts, you can create Gateway policies.
Zero Trust accounts in Cloudflare Organizations include source accounts and recipient accounts.
In a tiered policy configuration, a top-level source account can share Gateway policies with its recipient accounts. Recipient accounts can add policies as needed while still being managed by the source account. Organization owners can also configure a custom block page for recipient accounts independently from the source account. Gateway will automatically generate a unique root CA for each recipient account in an Organization.
Each recipient account is subject to the default Zero Trust account limits.
Gateway evaluates source account policies before any recipient account policies. Shared policies always take priority in recipient accounts recipient accounts cannot bypass, modify, or reorder shared policies, and cannot move any of their own policies above shared ones. If you update the relative priority of shared policies in the source account, the change will be reflected in recipient accounts within approximately two minutes.
All traffic and corresponding policies, logs, and configurations for a recipient account will be contained to that recipient account. Organization owners can view logs for recipient accounts on a per-account basis, and Logpush jobs must be configured separately. When using DLP policies with payload logging, each recipient account must configure its own encryption public key.
flowchart TD
%% Accessibility
accTitle: How Gateway policies work in a tiered account configuration
accDescr: Flowchart describing the order of precedence Gateway applies policies in a tiered account configuration using Cloudflare Organizations.
%% Flowchart
subgraph s1["Source account"]
n1["Block malware"]
n2["Block spyware"]
n3["Block DNS tunnel"]
end
subgraph s2["Recipient account A"]
n5["Block malware"]
n6["Block spyware"]
n4["Block social media"]
end
subgraph s3["Recipient account B"]
n8["Block malware"]
n9["Block spyware"]
n10["Block DNS tunnel"]
n7["Block instant messaging"]
end
n1 ~~~ n2
n2 ~~~ n3
s1 -- Share policies with --> s2 & s3
n1@{ shape: rect}
n2@{ shape: rect}
n3@{ shape: rect}
n4@{ shape: rect}
n5@{ shape: rect}
n6@{ shape: rect}
n7@{ shape: rect}
n8@{ shape: rect}
n9@{ shape: rect}
n10@{ shape: rect}
n1:::Sky
n2:::Sky
n3:::Peach
n4:::Forest
n5:::Sky
n6:::Sky
n7:::Forest
n8:::Sky
n9:::Sky
n10:::Peach
classDef Sky stroke-width:1px, stroke-dasharray:none, stroke:#374D7C, fill:#E2EBFF, color:#374D7C
classDef Peach stroke-width:1px, stroke-dasharray:none, stroke:#FBB35A, fill:#FFEFDB, color:#8F632D
classDef Forest stroke-width:1px, stroke-dasharray:none, stroke:#2D6A4F, fill:#D8F3DC, color:#2D6A4F
In the diagram above:
Tiered policies with Organizations have the following limitations:
Caution
If a shared policy contains identity-based selectors, ensure that both the source account and recipient accounts have matching identity provider (IdP) configurations. If there is a mismatch in IdPs between the source account and a recipient account, the shared policy will never apply to traffic in that recipient account.
You can create, configure, and share your tiered policies in the source account for your Cloudflare Organization.
To share a Gateway policy from a source account to a recipient account:
A sharing icon will appear next to the policy's name. When sharing is complete, the policy will appear in and apply to the recipient accounts. Shared policies will appear grayed out in the recipient account's list of Gateway policies.
Note
After sharing a policy, it may take up to two minutes before the policy appears in recipient accounts.
If a policy fails to share to recipient accounts, Gateway will retry deploying the policy automatically unless the error is unrecoverable.
To change or remove recipients for a Gateway policy:
When sharing is complete, the policy sharing will update across the configured recipient accounts.
Note
If you selected Select all accounts in org when sharing the policy, you will need to unshare the policy before you can edit its recipient accounts.
To stop sharing a policy with all recipient accounts:
When sharing is complete, Gateway will stop sharing the policy with all recipient accounts and only apply the policy to the source account.
Changes made to shared policies will apply to all recipient accounts. Deleting a shared policy will delete the policy from both the source account and all recipient accounts.
You can share certain Gateway settings - the Gateway block page and extended email address matching - from your source account to recipient accounts in your Cloudflare Organization. Other Gateway settings configured in a source account, such as AV scanning and file sandboxing, will not affect recipient account configurations.
To share your Gateway block page settings from a source account to a recipient account:
A sharing icon will appear next to the setting. When sharing is complete, the setting will appear in and apply to the recipient accounts.
To modify share recipients or unshare the setting, select the three-dot menu and choose Edit shared configuration recipients or Unshare.
To share your extended email address matching settings from a source account to a recipient account:
A sharing icon will appear next to the setting. When sharing is complete, the setting will appear in and apply to the recipient accounts.
To modify share recipients or unshare the setting, select the three-dot menu and choose Edit shared configuration recipients or Unshare.
| Web Proxy Viewer | New URL | Original Page |