Skip to main content

Network

This guide covers how to narrow where people can reach the tenant from, and traffic going out from this service.

Coming in: four restrictions​

There are four restrictions on the way in, and each works on its own. Turning one on does not narrow the other entry points.

RestrictionEntry point it narrowsScreen
Allowed IPsThe admin console, and the chat (including self sign-up)“Sign-in and Access Sources” > “Access Source Restrictions” > the “Allowed IPs” tab
External API Allowed IPsThe external integration API (/api/v1)“Sign-in and Access Sources” > “Access Source Restrictions” > the “External API Allowed IPs” tab
Country RestrictionsConnections to sign-in, the chat and the admin console. Does not apply to the external integration API or the LLM Gateway“Sign-in and Access Sources” > “Access Source Restrictions” > the “Country Restrictions” tab
LLM Gateway Allowed IPsThe LLM Gateway (/llm)“LLM Gateway Management” > “LLM Gateway Allowed IPs” (Setup Guide)

Allowed IPs​

The restrictions for the admin console (ADMIN) and for the chat (WEB) are turned on separately. The allow list is shared by the two, and for each allowed IP address you choose whether it can reach the admin console, the chat, or both. With the WEB restriction on, people at IP addresses that are not allowed cannot use the chat, and cannot sign themselves up from the sign-in page either. The sign-up screen says so and its button cannot be pressed.

Items for one allowed IP

ItemDetails
IP Address (required)IPv4, IPv6 or CIDR (for example 192.168.1.100, 192.168.1.0/24, 2001:db8::/32). No spaces. Values that allow every address (0.0.0.0/0, ::/0) cannot be registered
DescriptionA note on its use or location (for example: head office)
Services (at least one)ADMIN (can reach the admin console) / WEB (can reach the chat and sign themselves up)
ActiveTurned off, the entry stays in the list but no longer allows anything

Turning the restriction on and off

  • At the top of the list, turn the ADMIN and WEB restrictions on or off separately. Turning one off asks for confirmation
  • A restriction cannot be turned on while there is no active allowed IP for that service
  • The ADMIN restriction cannot be turned on unless your own IP address is on the list. This keeps you from locking yourself out. When it cannot be turned on, the screen says so, showing your current IP address
  • Read the state of each row as follows
StateMeaning
Rule onThis allowed IP is in effect
Rule on (not applied)The allowed IP is active, but that service's restriction is off, so nothing is being narrowed yet
Rule offThis allowed IP is not used

When you delete one, the screen shows the impact: how many active allowed IPs remain afterwards, whether it is your current source, and whether it is the last one.

  • If you delete the last active allowed IP while the ADMIN restriction is on, nobody can reach the admin console from outside, and you cannot get back to this screen either. Before deleting, register another allowed IP or turn the ADMIN restriction off
  • If only the WEB restriction is on, the chat can no longer be reached from outside, but the admin console still works
  • If you delete your current source, you cannot get back to the admin console from it unless another allowed IP covers it

External API Allowed IPs​

This narrows where the external integration API (/api/v1) can be called from. It is off by default. Sources for the LLM Gateway (/llm) are decided separately, in “LLM Gateway Allowed IPs”.

  • Each entry has an IP address (IPv4, IPv6 or CIDR), a description and an active switch
  • The restriction cannot be turned on while there is no active allowed IP
  • When it is on, calls from addresses that are not allowed get 403 (error.code is ip_not_allowed)
  • While it is on, the last active allowed IP cannot be disabled or deleted. Turn the restriction off first

Country Restrictions​

A Country Restrictions rule applies to sign-in, the chat and the admin console. It does not apply to the external integration API or the LLM Gateway. It cannot be limited to the admin console only or the chat only.

For each rule, decide the action, priority and countries. Countries that do not fit in one rule go into another rule.

ItemDetails
Rule name (required)Starts with a letter; letters and digits only, up to 128 characters (for example GeoBlockedAllServices)
Priority (required)An integer from 100 to 199. Smaller numbers take effect first. A number already used by another rule cannot be used
ActionBlock (stop connections from the selected countries) / Detect only (record them without stopping)
Blocked countries (at least one)Up to 10 per rule
EnableOn by default. Turned off, the rule has no effect. Turning it off asks for confirmation

Settings can take about an hour to take effect. When applying a creation, change or deletion is taking a while, the screen says so. The list shows, for each rule, the number of detections over the last 30 days.

Order for applying restrictions​

Whether to apply each restriction is up to you. When you do, go in this order so you are not locked out.

  1. First, register the IP addresses of everyone who will use the service — including people working from home or travelling, and administrators
  2. For country restrictions, start with “Detect only (log)” to see what happens, and switch to “Block” only for countries you are happy to stop
  3. Turn each restriction on last

Going out: from this service to your systems​

These are the rules for traffic going out from this service. They apply, for example, when an agent calls an MCP server or one of your APIs.

Source IP addresses​

Allow every IP address shown under “Sign-in and Access Sources” > “Outbound IPs” in your firewall. These are the source addresses of traffic going out from this service.

  • They are the source addresses of traffic going out from this tenant's environment (for example, when an agent calls an MCP server or one of your APIs)
  • The IP addresses are set by the deployment and cannot be changed on this screen
  • They can change if the environment is rebuilt. When they change, the values on this screen change too
  • If it shows “Not configured”, contact SoftBank

Ports you can use​

An agent can connect out on these eight ports:

443, 80, 8080, 8443, 8000, 3000, 5000, 9000

MCP servers and the like that listen on other ports cannot be reached. Make sure your side can accept connections on one of these ports.

Agents can only connect out over HTTP and HTTPS. They cannot connect directly to databases, mail sending (SMTP), SSH and the like. To use an external database, provide something callable over HTTP on your side, such as an MCP server that wraps it.

Destinations​

By default, agents can go out to any destination. Register destinations you want stopped in “Banned URL”. A destination that matches a banned URL is always stopped (Guardrails and Banned URLs).

Outgoing traffic that was allowed or stopped is recorded in “Outbound Communication Records” (Logs and Audit).