Skip to main content

IP Restrictions

Limit Level account access to specific IP addresses to prevent logins from untrusted networks.

Introduction

IP restrictions let you lock Level logins down to a set of trusted IP addresses: your office network, VPN, or specific machines. Anyone trying to log in from outside that list gets blocked, even with valid credentials.


Configuring the IP Allowlist

⚠️ WARNING: Include your current IP address before enabling the allowlist. If you lock yourself out, you'll need to contact Level support to regain access.

  1. Navigate to Settings → Security.

  2. Scroll to the IP Allowlist section at the bottom of the page.

  3. Click Add IP Address.

  4. Enter a trusted IP address or CIDR range (e.g., 68.191.123.208/28).

  5. Optionally, add a description (e.g., "Office," "VPN exit node," "John's home office").

  6. Repeat for each address you want to allow.

  7. Enable the IP Allowlist toggle to start enforcing restrictions.

💡 TIP: Use descriptions on every entry. "VPN" or "Headquarters" is much more useful than a bare IP six months from now when someone asks why a specific address is listed.


How It Works

When the allowlist is active, login attempts from any IP not on the list are blocked at authentication. The technician sees an error; they don't get through even if their credentials are correct.

ℹ️ NOTE: IP restrictions apply to web interface logins. They don't affect the Level agent's connection to Level's backend infrastructure. Managed devices communicate independently of this setting.


Keeping the List Current

Network infrastructure changes. When it does, update the allowlist before the old IP is decommissioned, not after.

Common situations to watch for:

  • VPN IP changes after a provider switch

  • ISP-assigned dynamic IPs at branch offices

  • Adding a new remote technician who works from a fixed home IP

To disable one entry, turn off that row's toggle. To remove an entry, open its three-dot menu and choose Delete.

While the allowlist is enabled, the settings page disables both the row toggle and Delete for the last enabled entry that includes your current IP address. Disabled entries do not count, even if their IP address or CIDR range includes your address.

To change trusted networks without turning off the allowlist:

  1. Add the new trusted IP address or CIDR range before switching networks or decommissioning the old address. Keep the old entry enabled.

  2. Make sure the new entry's toggle is Enabled and the change has saved successfully.

  3. From the new trusted network, sign in to Level in a separate browser session and confirm that you can open Settings → Security.

  4. After confirming access, disable or delete the old entry from that session. Keep any entries still needed by other technicians.

Your current IP can change when you switch VPNs, ISPs, or networks. This safeguard does not guarantee continued access after those changes or protect every technician's access.

To deliberately stop enforcing IP restrictions for the whole organization, turn off the main IP Allowlist toggle. This removes the IP-based restriction organization-wide, rather than disabling a single entry. Do not turn it off just to bypass a locked row while replacing a trusted network.


FAQ

  • Who can manage the IP allowlist? Only Organization Admins can configure IP restrictions under Settings → Security.

  • What happens to technicians who are already logged in when I enable the allowlist? Active sessions aren't terminated immediately. The restriction applies to new login attempts. Technicians on untrusted IPs will be blocked when their current session expires and they try to log back in.

  • Can I add a CIDR range instead of a single IP? Yes. Enter a valid CIDR range (e.g., 198.190.255.208/28) to allow an entire subnet.

  • I enabled the allowlist and now I'm locked out. What do I do? Contact Level support at [email protected]. Support will verify your identity before helping restore access.

  • Does this affect the Level agent on managed devices? No. The agent communicates with Level's backend directly and is not subject to the login IP allowlist. This setting only affects technician logins via the web interface.

Did this answer your question?