Skip to main content

Team IP Allowlist

The IP allowlist lets the owner of a team account limit where the team can use TestingBot from. Once it is enforced, the dashboard and the REST API only accept requests from the IPv4 and IPv6 addresses and CIDR ranges on the list, for every member of the team, the owner included.

The allowlist is off by default. It is available on paid plans and is managed by the account owner from the Authentication tab of the team pages. Team admins can see the list but cannot change it.

What is checked

Access Checked
Signing in to the dashboard (password, SSO, Google/GitHub sign-in) and every dashboard page afterwards Yes
REST API calls with your key and secret, including those made by the CLI and CI integrations Yes
Starting a TestingBot Tunnel (the tunnel client creates the tunnel through the REST API) Yes
Automated test sessions sent to the grid (Selenium, Appium, Playwright, Puppeteer, Cypress and others) No
The tunnel's own connection once it is running, and the stream of a Live session that has already started No
Public links you shared, such as a shared build or test page No

Because REST API calls are checked, add the outgoing addresses of your CI runners if your pipelines upload apps, start tunnels or read results through the API.

Set up the list

  • Open Team → Authentication in the dashboard and scroll to IP allowlist. The card shows your current IP address and whether it is on the list.
  • Enter one address or CIDR range per line, for example 203.0.113.0/24, 2001:db8::/48 or 198.51.100.7. Add # and a label after an entry to remember what it is for. Up to 100 entries are allowed.
  • Pick a mode and click Save IP allowlist.

If you save an enforced list that does not include the address you are using right now, the save is refused and the page tells you your current address. Add it, or tick the confirmation box if you really mean to save the list without it.

Modes

  • Off: nothing is checked. The list is kept, so you can turn it back on later.
  • Monitor: requests from outside the list are allowed, and recorded in your team's audit log as "Request from outside the team IP allowlist". Use this to find addresses you forgot before you enforce the list.
  • Enforce: dashboard and API requests from outside the list are refused, and recorded in the audit log.

Changes to the list are recorded in the audit log too. Repeated refusals from the same address are summarised rather than recorded one by one.

When a request is refused

  • Dashboard: the member is signed out and sees a page explaining that the team only allows approved addresses, with the address the request came from. A member who moves to a network outside the list is refused on their next page load, not only at their next sign-in.
  • REST API: the API answers with HTTP 403 and a JSON body with "code": "ip_not_allowed". A wrong key or secret still returns 401, so you can tell the two apart.

Locked out

If the owner can no longer reach the dashboard because of the list, connect from an address on the list (for example your company VPN) and update it. If that is not possible, contact support from the account owner's email address. Support can turn the allowlist off for your team; the list itself is kept so you can correct it, and the change appears in your audit log as made by TestingBot support.

Was this page helpful?
Last updated