Skip to content

Commit f9950bf

Browse files
committed
Add section
1 parent 4923ba8 commit f9950bf

File tree

1 file changed

+3
-7
lines changed
  • src/content/docs/cloudflare-one/policies/gateway/tiered-policies

1 file changed

+3
-7
lines changed

src/content/docs/cloudflare-one/policies/gateway/tiered-policies/index.mdx

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,17 +13,11 @@ Gateway supports using [Cloudflare Organizations](/fundamentals/organizations/)
1313

1414
## Get started
1515

16-
{/* Don't need to surface much of the policy creation flow here */}
17-
1816
To set up Cloudflare Organizations, refer to [Create an Organization](/fundamentals/organizations/#create-an-organization). Once you have provisioned and configured your organization's accounts, you can create [Gateway policies](/cloudflare-one/policies/gateway/).
1917

2018
## Account types
2119

22-
Tiered policies support tiered and siloed account configurations.
23-
24-
### Tiered accounts
25-
26-
{/* TODO: Rename this section and check if siloed accounts are relevant (potentially fix H2 preamble above). Fix the flow to match Orgs config. */}
20+
Accounts in organizations include source accounts and recipient accounts.
2721

2822
In a tiered account configuration, a top-level source account enforces global security policies that apply to all of its recipient accounts. Recipient accounts can add policies as needed while still being managed by the source account. Organization owners can also configure recipient accounts independently from the source account, including:
2923

@@ -70,3 +64,5 @@ flowchart TD
7064
:::caution[Limitations]
7165
Tiered policies do not support egress policies, device posture selectors, private apps, or virtual networks.
7266
:::
67+
68+
## Share policy

0 commit comments

Comments
 (0)