The IP allowlist limits your workspace to the network addresses you trust, for example your office's public addresses or the outgoing addresses of your corporate VPN. Once you save a list, anyone who opens the workspace from another address is turned away, even with a valid password, session or token.
Use it when your security policy says company data may only be reached from the corporate network.
What it covers
When the list is on, these are refused from any address that is not on it:
- Using the app in the browser. Signing in still works, but the workspace itself doesn't open. People see a page that explains why and shows their current address. If they also belong to other workspaces that this address can reach, the page offers to switch to one of them.
- Personal access tokens, the API and the CLI. A token from a blocked address gets no session, and a session obtained earlier stops working there.
- Download links in reports. Links to files in report emails and Slack messages open only from an allowed address.
These keep working, because they don't come from a person's network:
- Scheduled reports still run and are still delivered by email, Slack and the other destinations.
- Slack. Messages, buttons and the PushMetrics app in Slack work as before. Someone using PushMetrics from Slack is not checked against the list.
- AI agents keep running, including the ones people talk to in Slack.
- Report trigger webhooks, which your own systems call with the webhook's token.
The list applies to one workspace. If your organization has several workspaces, set it in each one that needs it.
Before you start
- You need workspace admin rights. Other members can't see the list, only whether it is on.
- Find out the public addresses your organization's traffic comes from: your office's internet addresses and your VPN's outgoing addresses. Your IT or network team can tell you. Addresses inside your network (such as
10.x.x.xor192.168.x.x) are not what PushMetrics sees. - Save the list while you are connected through one of those networks. PushMetrics won't save a list that leaves out your own current address, so you can't lock yourself out by mistake.
Turn it on
- Go to Account Settings and find the IP access card. It shows your current address.
- Click Add address or range and enter an address or a range in CIDR notation, with an optional label:
- a single address:
203.0.113.7 - a range:
203.0.113.0/24(all addresses from203.0.113.0to203.0.113.255) - IPv6 works the same way:
2001:db8::/48
- a single address:
- Click Add my address if your current address isn't covered yet.
- Click Save.
The change applies right away. Anyone outside the list is turned away within about 30 seconds.
A list can hold up to 100 entries. Ranges wider than /8 (IPv4) or /16 (IPv6) are refused, because they would let almost any address in.
Change or turn it off
Edit or remove entries and click Save, or click Turn off to let every address in again. Turning it off doesn't affect anything else in the workspace.
Every change, and every refused request, is recorded in the workspace's security log.
If you're locked out
If your address changed, for example because your VPN provider moved to new addresses, connect from an address that is still on the list and update it there. If no admin can reach the workspace from an allowed address, contact support via the in-app chat or at support@pushmetrics.io from an admin's email address, and we'll turn the list off for you.
Related
- Security — how PushMetrics protects your data, and the static address PushMetrics uses to connect to your databases (the opposite direction).
- Domain Join — let colleagues with a company email join the workspace.
- CLI — what
pmshows when an address is not allowed.