You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/docs/content/docs/en/platform/enterprise/ip-access.mdx
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ IP Access lets organization owners and admins on Enterprise plans restrict where
13
13
14
14
Go to **Settings → Security → IP access** in your organization settings.
15
15
16
-
Add one entry per line — individual IPv4/IPv6 addresses or CIDR ranges(for example `203.0.113.7`, `10.0.0.0/16`, `2001:db8::/48`), up to 200 entries — then turn on **Restrict access by IP** and save.
16
+
Add one entry per line — individual IPv4/IPv6 addresses or CIDR ranges, each with an optional label after a `#`(for example `203.0.113.7 # Office`, `10.0.0.0/16 # Frankfurt VPN`), up to 200 entries — then turn on **Restrict access by IP** and save.
17
17
18
18
The settings page shows your current IP. Saving a list that would exclude your own address is rejected, so you cannot lock yourself (and your organization) out in one step.
19
19
@@ -26,7 +26,9 @@ The settings page shows your current IP. Saving a list that would exclude your o
26
26
-**API keys** — personal and workspace API keys belonging to organization members are only accepted from allowed addresses.
27
27
-**Live collaboration** — realtime canvas connections are checked at connect time.
28
28
29
-
Deployed chats, public form shares, webhooks, and scheduled executions are **not** restricted — they are your organization's outward-facing product surfaces and server-side automations, not member access.
29
+
Deployed chats, public form shares, webhooks, and scheduled executions are **not** restricted — they are your organization's outward-facing product surfaces and server-side automations, not member access. This scoping is intentional: those surfaces authenticate by their own means (share tokens, webhook signatures), and gating them on caller IP would break the product for its external audience.
30
+
31
+
Policy changes and denied access attempts are recorded in the [audit log](/platform/enterprise/audit-logs) — denials include the member and the blocked address, throttled per member so a polling client cannot flood the log.
0 commit comments