# Proxy Users

> URL: https://foura.ai/docs/dashboard/proxy
> Updated: 2026-10-28
> Index: https://foura.ai/llms.txt

The Proxy page (sidebar > Proxy, under **Access**) is where you create proxy users and get the exact connection string to paste into any client that accepts a proxy URL. It fronts the [proxy port](https://foura.ai/docs/api/proxy-port): your traffic leaves from one of FourA's exits, with the network, country, and session behaviour you choose. Tunnels and traffic count against your plan, the same as the API. On a plan sold by credits the port has its own included gigabytes, shown on Usage & Limits and topped up on the Billing page.

## Creating a Proxy User

1. Open **Proxy** in the sidebar.
2. Click **Create proxy user**.
3. Give it a name (up to 60 characters). The name is only for you to tell them apart.
4. Pick an **Owner**. The select appears only if you belong to an organization, and it offers **Personal (me)** plus each organization you're in. Creating from a filtered list defaults to the owner already on screen.
5. Click **Create**.

A dialog shows the generated username and password with a copy button on each. You choose neither: the username has to stay free of dashes, because a dash starts an option in the [username grammar](https://foura.ai/docs/api/proxy-port#options-ride-in-the-username), and the password is a strong random string. Both can be shown again later, so there's nothing to write down. If a proxy user's password can't be shown, the dashboard answers `This password cannot be shown. Rotate it to get a new one.`

## Personal or Organization-Owned

A personal proxy user is yours alone and its traffic counts against your plan. One owned by an organization is shared with everyone in it, and its traffic counts against the plan of whoever owns that organization, exactly as an organization's API key works.

What each role may do with an organization's proxy user:

| Action | Member | Admin | Owner |
|--------|--------|-------|-------|
| Use it, read its password, create new ones | Yes | Yes | Yes |
| New password, disable, delete, change saved targeting | No | Yes | Yes |
| Transfer it out of the organization | No | No | Yes |

Reading is a member's right on purpose: a credential the team can't read is one the team can't use, and the alternative is a personal credential that quietly bills the developer. Rotating a password is not, because it breaks every config file the credential is already pasted into. Transferring out moves the bill onto the taker's own plan, so it sits with the owner alone.

An **Owner** filter appears above the list once you belong to an organization: **Everything**, **Personal**, or one organization. It follows the same choice as the Owner filter on Overview, Metrics, Activity, and API Keys. See [Organizations](https://foura.ai/docs/dashboard/teams-and-orgs).

## The List

| Column | What it shows |
|--------|---------------|
| Name | The name you gave it |
| Owner | Personal, or the organization that owns it |
| Username | The credential half of the proxy username |
| Targeting | In words, what this user answers by default: network, country, and anything saved under Targeting |
| Status | Active or disabled |
| Created | When it was created |
| Last Used | When it last carried traffic, to the minute |

Every row shows only the actions your role allows:

- **Connection string** opens the user's own page (see below).
- **Show password** reveals the password in a dialog.
- **Disable** stops the user authenticating within a minute; **Enable** brings it back.
- The menu holds **New password**, which keeps the username and replaces the password (anything still using the old one stops working immediately), **Transfer**, which moves the user between you and an organization while username, password, and saved targeting all stay the same, and **Delete**, which removes the user for good.

Click a column header to sort Name, Owner, Status, Created, or Last Used. Sorting by Owner on the Everything view groups the personal ones together.

## The Connection String Page

Click **Connection string** on a row and the page shows that user alone, with two tabs.

### Connection string tab

The lines to paste, rewritten live as you change anything under Targeting. Pick the format from the select on the right:

| Format | Shape |
|--------|-------|
| URL | `http://user:password@proxy.foura.ai:34004` |
| host:port:user:pass | `proxy.foura.ai:34004:user:password` |

The password is masked until you click **Show password**; **Copy** on a line always copies the real one. Under the lines, a sentence says what the string will do in words (for example "Premium network, DE, Sofia, 10 min"), and curl, Python, and Node snippets show the first line in use.

With **Sticky** sessions and a count above one, the tab lists one line per address, each with its own generated session name. **New names** regenerates the whole list, which is a fresh set of addresses when a target has soured on the old ones, and **Copy all** copies every line.

### Targeting tab

Two cards, and the settings live inside the one you pick:

- **Shared network**: FourA's own exits, included in your plan. Choose a **Country** (the shared network is chosen by country and nothing finer). Tick **Use a premium exit if the shared network can't carry the request** to arm the fallback; it only fires when your plan includes premium traffic and allowance remains, and it's unticked by default.
- **Premium network**: home addresses, drawn from your plan's premium traffic. **Country** opens **Region** and **Network (ASN)**, and a region opens **City**. **Device** narrows to Windows, Android, iOS, or macOS.

Below both cards, the session controls apply whichever network you picked:

| Control | What it does |
|---------|--------------|
| Session type | **Rotating** gives a new address per connection. **Sticky** keeps one. |
| How many | Sticky only. One line per address, up to 100 on this screen. |
| Session name | Sticky only, for a single address. Connections sharing a name share an address. Left empty, a name is generated. |
| Rotating interval | Sticky on the premium network only. How long one address is held, in minutes or hours, from 3 minutes to 24 hours. |

Country lists come from the exits FourA actually has, so a country that's offered has addresses behind it.

### Saving defaults

Everything on the Targeting tab applies to the connection string on screen only, until you click **Save as defaults**. Saved targeting becomes what the proxy user answers on every connection, the Targeting column on the list says so in words, and the connection string shrinks to the bare credential plus whatever differs from the saved values. Anything you add to the username still wins for that one connection.

A save is refused when the combination can't work, such as a city on the shared network or a fallback on the premium network, so a proxy user can't be stored in a state that refuses every connection.

A saved premium default spends only while your plan's premium traffic lasts. Once it's spent, a connection that relies on the saved default is served from the shared network and the tunnel still opens, while a connection that names `-network-premium` in the username is refused with a 403. The [proxy port reference](https://foura.ai/docs/api/proxy-port) covers both cases.

On an organization's proxy user, saving defaults is an admin or owner action. Re-pointing saved targeting silently re-points the whole organization's traffic, which is why it sits beside the password.

## Where the Numbers Are

The Proxy page creates and configures credentials. It carries no statistics. What each proxy user moved lives on the three reporting pages, with the **Product** switch set to Proxy:

- [Overview](https://foura.ai/docs/dashboard/overview): tunnels, traffic, setup time, and tunnels open at once
- [Metrics](https://foura.ai/docs/dashboard/metrics): the Usage panel by proxy user, target, exit country, client IP, or outcome
- [Activity](https://foura.ai/docs/dashboard/activity-log): one row per tunnel in the last hour
- [Usage & Limits](https://foura.ai/docs/dashboard/quota): a **Proxy users** tab with this billing period per credential

## Tips

- Give each job its own proxy user. A user in daily use shows it in **Last Used**, and a leaked one can be disabled or given a new password without touching the others.
- Driving a browser through the port? Use a sticky session. A page load opens dozens of connections, and without a session each one would leave from a different address.
- The `host:port:user:pass` format is what most proxy managers import. The URL format is what curl and HTTP libraries take.
- A company's downloader belongs on an organization's proxy user, not on one person's. A personal credential stops working the day that person leaves, and it bills them.
- Tunnels open at once and openings a minute come from your plan and are counted for the account, so a second proxy user doesn't buy a second allowance.

## Related

- [Proxy Port](https://foura.ai/docs/api/proxy-port): Host, port, every username option, response codes, and limits
- [Usage & Limits](https://foura.ai/docs/dashboard/quota): Traffic and premium traffic against your plan, per proxy user
- [How Your Plan Is Metered](https://foura.ai/docs/guides/plans-and-metering): Where the port's gigabytes come from
- [Managing API Keys](https://foura.ai/docs/dashboard/api-keys): The other kind of credential, for the JSON API
- [Organizations](https://foura.ai/docs/dashboard/teams-and-orgs): Roles, members, and who the usage bills to