> For the complete documentation index, see [llms.txt](https://docs.countercyclical.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.countercyclical.io/workspace-settings/network-access.md).

# Network Access

Restrict workspace access to approved IP addresses and network ranges to keep sensitive research and data accessible only from trusted networks.

Network Access lets workspace administrators define which networks can access protected workspace routes or accept workspace invitations. When enabled, members must connect from an approved [IP address](https://en.wikipedia.org/wiki/IP_address) or [CIDR range](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) before they can access the workspace.

See also [Authorized Login Methods](https://docs.countercyclical.io/workspace-settings/authorized-login-methods) and [Enforced Logouts](https://docs.countercyclical.io/workspace-settings/enforced-logouts).

You can manage Network Access from [**Settings › Workspace › Advanced › Access**](https://dashboard.countercyclical.io/settings/workspace/advanced/access).

### How Network Access Works

Network Access acts as a workspace-level network boundary. When enforcement is enabled, Countercyclical evaluates the network a member is connecting from against the workspace’s approved network list.

If the connection originates from an approved network, the member can continue to the workspace subject to their normal permissions. If the network is not approved, protected workspace access is restricted.

Network Access does not replace workspace permissions, roles, or resource-level access controls. A user must satisfy both the network policy and the permissions that normally govern the resource they are trying to access.

### Enable Network Access

Under [**Advanced › Access**](https://dashboard.countercyclical.io/settings/workspace/advanced/access), turn on **Network Access**.

Once enabled, the Network Access configuration appears with a warning that network enforcement is active. Configure at least one approved network so authorized members have a valid path into the workspace.

You can approve either:

* An exact IP address for a specific network endpoint.
* A CIDR range when multiple addresses belonging to the same network should be permitted.

Changes to the approved network list take effect after you select **Save**.

{% hint style="warning" %}
**Verify the Allowlist**

Before enforcing Network Access broadly, verify that the networks required by your organization are included. An incomplete allowlist can prevent members from accessing the workspace.
{% endhint %}

### Add your Current IP

Select **Add Current IP** to add the public IP address associated with your current browser session.

Countercyclical creates an entry for the detected address and identifies it as your current network. You can review or modify the label and description before saving.

This is the quickest way to authorize the network you are currently using without manually entering its IP address.

Keep in mind that many residential, mobile, and some corporate networks use dynamic public IP addresses. If the address changes, the previously approved address may no longer match the member’s connection.

### Add a Network Manually

Select **Add Network** to create an approved network entry manually.

Enter a **Label** that identifies the network, such as `New York Office` or `Corporate VPN`, followed by the permitted **IP Address or CIDR**. You can also add an optional **Description** to record operational context about why the network is approved.

For example, an exact address restricts access to that individual public IP, while a CIDR such as `203.0.113.0/24` represents an address range.

Select **Save** after configuring the network.

### Managing Approved Networks

Approved networks appear directly in the Network Access configuration. Each entry includes its label, IP address or CIDR range, and any description supplied by the administrator.

Use descriptive labels so administrators can identify why an entry exists without having to recognize an IP address. Descriptions can record details such as the office, VPN, environment, or operational purpose associated with the entry.

To revoke an approved network, remove its entry and save the updated configuration. Connections through that network will no longer satisfy the workspace network policy.

### Network Access and Invitations

Network enforcement also applies when a user attempts to accept a workspace invitation.

An invitation establishes that a person has been invited to the workspace; it does not bypass the workspace’s network policy. When Network Access is active, the invited user must connect through an approved network before they can accept the invitation and enter protected workspace routes.

This allows organizations to combine identity and membership controls with a network-level access boundary.

### Recommended Configuration

For organizations using a corporate VPN, office network, or other managed egress infrastructure, add the stable public IP addresses or CIDR ranges used by those environments before enabling enforcement for users.

Avoid approving unnecessarily broad CIDR ranges. Network Access is most effective when the allowlist represents the smallest set of networks genuinely required to access the workspace.

If your organization has multiple offices, VPN gateways, or other trusted environments, create separate labeled entries for each. This makes the allowlist easier to audit and maintain over time.

#### Related Pages

{% content-ref url="/pages/w2eid0bmERSp5NKfoJvq" %}
[Authorized Login Methods](https://docs.countercyclical.io/workspace-settings/authorized-login-methods.md)
{% endcontent-ref %}

{% content-ref url="/pages/fZzkm9Qnz3cS5uVHItQF" %}
[Enforced Logouts](https://docs.countercyclical.io/workspace-settings/enforced-logouts.md)
{% endcontent-ref %}

{% content-ref url="/pages/09gK08hcM2xARMMqNtzQ" %}
[Managing Workspace Members](https://docs.countercyclical.io/workspace-settings/managing-workspace-members.md)
{% endcontent-ref %}
