Skip to content

Commit 42d0954

Browse files
defguard-communitygitbook-bot
authored andcommitted
GITBOOK-383: ACL allowed users vs location allowed users clarification
1 parent b2b8c5e commit 42d0954

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

  • enterprise/all-enteprise-features/access-control-list

enterprise/all-enteprise-features/access-control-list/README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -106,6 +106,12 @@ In Defguard, sources can be defined as one of three object types:
106106

107107
Each ACL rule in Defguard is intended to fully define access to a specific resource, you must therefore always include at least one allowed source.
108108

109+
{% hint style="warning" %}
110+
This setting is independent from the default location-level [**Allowed groups**](../../../admin-and-features/features-and-configuration/wireguard/create-your-vpn-network.md#allowed-groups) configuration. 
111+
112+
If you give a user access to some resource through an ACL rule, but they do not have access to a given location, they still won't be able to access it, because they'll be unable to establish a VPN connection with the gateway.
113+
{% endhint %}
114+
109115
### How to define your ACL ruleset
110116

111117
Access Control List (ACL) rules in Defguard are used to manage **who can access specific resources** across your network. Think of each rule as a clear instruction that says: _“These users or devices are allowed to reach this resource - and optionally, these others are not.”_

0 commit comments

Comments
 (0)