Skip to content

Claude Team Plan Members in Different Cities: IP Policy

What the platform looks at, a scenario table for distributed teams, and a four-step IP policy you can write down.

What Claude says it uses location for

Anthropic describes two levels for commercial products such as the Team plan. City or region level is optional: it is estimated from the IP address for features like local web search results, and admins and members can turn it off.

Country or region level is mandatory. Anthropic estimates it from IP and other signals to protect against abuse, comply with its terms and show the features available in a region, and it cannot be switched off. Separately, its supported-countries policy says people physically in an unsupported area are restricted, even if they work for a company in a supported one.

Scenarios for a distributed team

Scenarios for a distributed team
ItemWhat the rules point toWhat to do
Members in several cities of one supported countryCountry level is the same; city level is optional and can be disabledEach member works from their own normal connection; turn off city-level location if you prefer
A member in another supported countryAccess follows where the person physically is, and that country must be supportedCheck the country against Anthropic's list before they start
A member travels to an unsupported placeAccess is restricted for people physically thereDo not use the seat there; a proxy does not change where the person is
A shared office behind one outgoing addressNothing special: it is one networkNothing to change; use a fixed IP only if your own systems need to allowlist it
Servers or CI calling the API or Claude CodeNot a person-location questionA static IP gives a stable address for your own allowlists
One seat used by two peopleSeats are per member; the Team plan needs at least two membersGive each person their own seat instead

Sources: Anthropic Privacy Center, Anthropic supported-countries policy and Claude Help Center, read on 17 November 2026. The rows describe what those pages say, not a guarantee about how any account is treated.

Seats, accounts and the one-IP rule

The Team plan has admin tools for access and billing and needs at least two members. Treat each seat as one person's account. If a person has several accounts of their own, keep one fixed, clean IP per account and do not use one account from several machines in different countries.

Where a person subscribes on their own, the AI-subscription ISP guide shows how to match an IP to one account. The same four rules apply: one account on one fixed IP, no sharing of accounts, follow the platform's terms and supported regions, and complete verification when it is requested.

Where a fixed IP does help a team

A fixed address is useful when your own systems care about it: a build server or an agent that calls the API or Claude Code, a partner that allowlists your address, or a monitoring job that should always come from one place. A static ISP IP stays the same for the whole lease, so you can note it once.

It does not decide where a person is, and it does not turn an unsupported location into a supported one. For ChatGPT, check OpenAI's own list of supported countries in the guide above; each platform sets its own rules.

Write a team IP policy in four steps

  1. Step 1: list where members work

    Write down each member's country and check each one against Anthropic's supported countries and regions.

  2. Step 2: one seat, one person

    Give every member their own seat, and keep each personal account on its own connection or its own fixed IP.

  3. Step 3: decide what needs a fixed address

    Servers, CI and partner allowlists get a static IP that you record. People work from their normal networks.

  4. Step 4: write a travel rule

    Before anyone uses the seat abroad, check the country against the list. If a verification step appears, complete it as asked.

When a member hits an error

A region or "unsupported" message

Check The country the person is physically in, and the country shown by their IP.

Fix Compare both with the supported list. If they are in a supported country and the IP shows another, check the connection or the proxy first.

Stop when If the person is physically in an unsupported place, stop using the seat there.

The organisation or an account is disabled

Check The message text and the account's activity.

Fix Follow the platform's appeal process and see the guide on that message.

Stop when Do not open new accounts to get around a disabled one.

Verification keeps appearing

Check Your network and the IP itself with an IP check.

Fix Complete verification as asked; if the IP looks wrong, open a ticket with the order number.

With Proxy302

For a server or a single member's own subscription, a static ISP IP costs US$0.50 for 1 day or US$7.99 for 30 days in any country and stays the same for the lease. Choose HTTP (port 2222) or SOCKS5 (port 3333) when you buy. There is no free trial.

Auto-renew is optional and set per IP. The AI-subscription ISP is a separate product for people who need an IP for one AI account; its page has the tiers.

FAQ

Can Team plan members work from different cities?

Anthropic does not document different cities in one supported country as a problem. It estimates country or region from IP and other signals, and city level is optional.

Does Claude check each team member's location?

It estimates country or region from IP and other signals, which cannot be turned off, and city level only for features such as local search, which can.

What if a member travels abroad?

Access is restricted for people physically in an unsupported area. Check the country against the supported list before using the seat there.

Should the whole team use one proxy IP?

No. It does not change where people physically are, and one seat should belong to one person. Use a fixed IP for servers and allowlists.

Do two members need to share one account?

No. The Team plan is built around separate members, and it needs at least two.

Reference links

4
  1. Proxy302 product facts and price list

    Product observation · Confirmed on:

    Product facts checked on 10 November 2026 against the console, backend and price list: lease terms, prices (US$, 1 PTC = US$1), protocols and ports, no free trial.

  2. Anthropic Privacy Center: Does Claude use my team members' location?

    Official documentation · Confirmed on:

    Read on 17 November 2026: optional city or region level, estimated from IP for features such as local web search results, which admins and members can turn off; mandatory country or region level, estimated from IP and other signals, for abuse protection, terms compliance and regional feature availability, which cannot be turned off. It covers commercial products such as Claude for Work and the API.

  3. Anthropic: Supported countries and regions

    Official documentation · Confirmed on:

    Read on 17 November 2026: any country or region not listed is unsupported; access is also restricted for people physically located in an unsupported area, even if they work for a supported company; organisations incorporated or headquartered in an unsupported region are excluded. The policy page states an effective date of 12 November 2026.

  4. Claude Help Center: What is the Team plan?

    Official documentation · Confirmed on:

    Read on 17 November 2026: the Team plan needs at least two members, has admin tools for access and billing, and is available in certain supported locations with a link to the list.

Ready to try it?

Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.