Network access rules
Keep your organization and its apps to the networks you name — address ranges per rule, optionally per role and per app, where they are checked, what people and apps see when a rule refuses them, and how the lockout warning works.
An organization administrator can name the networks the organization may be used from: the office ranges, the VPN egress, a jump host. The rules are under Settings → Governance → Identity → Authentication → Network access rules. With no rule, any network is allowed, so nothing changes until you add one.
A rule
| Part | What it does |
|---|---|
| Name | Shown in the audit log when the rule refuses someone. Unique within the organization. |
| Allowed address ranges | One IP address or CIDR range per line — IPv4 or IPv6, for example 203.0.113.0/24 or 2001:db8::/32. Up to 64 per rule. 0.0.0.0/0 and ::/0 are refused: they allow every address. |
| Applies to roles | Optional. When set, the rule applies only to members holding one of these roles. |
| Applies to apps | Optional. When set, the rule applies only when a member signs in to one of these apps (OIDC or SAML), not when they open the organization itself. |
A rule with no roles and no apps applies to everyone, everywhere. An organization can hold up to 32 rules.
A member must be inside every rule that applies to them. For example, with a
corp rule of 10.0.0.0/8 for everyone and an admins rule of 10.9.0.0/16
for administrators, a member may work from anywhere in 10.0.0.0/8, while an
administrator must be in 10.9.0.0/16. Adding a rule can only narrow access.
Where the rules are checked
| When | What happens outside the rules |
|---|---|
| A member opens (switches to) the organization | Refused with IDENTITY_NETWORK_NOT_ALLOWED (HTTP 403). |
| A request names the organization or workspace it is for (a link, or the tenant-scope header) | The request is not served in that organization, and the answer says the network is not allowed. |
| A member accepts an invitation to the organization or to one of its workspaces | They join, but the organization is not made active for them from outside the rules. |
| A member signs in and the organization would become their active one | They are signed in, but no organization is active until they open one from an allowed network. |
| An app sends a member to sign in (OIDC authorize) | The app receives error=access_denied. |
| A SAML app asks Scrydon to sign a member in | Refused with network_not_allowed (HTTP 403); nothing is asserted to the app. |
Rules are not checked when an app refreshes a token, because a refresh comes from the app's server, not from the person. A token an app already holds keeps working until it expires, or until the organization's session limits end the sign-in. If you need a member who leaves the network to lose access quickly, set a short maximum session age as well.
The address checked is the one your deployment's own proxies vouch for. An address a client writes into a header itself is never believed. If no address can be established, a request a rule applies to is refused.
The lockout warning
If the rules you are saving would refuse you, from where you are now, the screen says so and asks before saving. Saving anyway is allowed — for example when you are setting up the rules from outside the office — but you will not be able to open the organization from here afterwards. If no administrator can reach an allowed network, your Scrydon operator can remove the rules.
The audit log
| Action | When |
|---|---|
identity.network_access.refused | A request was refused. Records where (surface), the address checked, the rule that refused it, and the app when there was one. |
identity.policy.updated | The rules were changed, with the rules before and after. |
Only organization owners and administrators can change the rules.