Tej strony nie ma jeszcze w Twoim języku. Czytasz tekst angielski.
Knowledge base
Share a proxy with the team
One pool per workspace
The proxy library lives in the account rather than on one computer, and there is a single pool for the whole workspace.
A manager and above pull that pool down to their own machine, so the same list is there. An operator or a member gets no pull at all: for them the addresses stay in the cabinet on the site.
Adding, editing, deleting an address and asking the seller for a new one belong to a manager and above. Someone below that is told plainly that their role does not allow it.
Put an address into the pool
Nothing here is a separate team feature: the pool is the same library you already use.
- 1
Open the proxy library
The Proxies tab in the left column.
- 2
Add the address
The Add proxy button above the list.
- 3
Press Refresh from account
The button on the same tab, for a manager and above.
- 4
Attach it to a profile
The proxy picker inside that profile's window.
- 5
Open the profile to a colleague
Share with the team, in the profile's own menu.
The list carries no password
What comes back in the ordinary list of proxies is the address, the label and a plain statement that a password is set. The password itself is not in that answer.
The seller's IP change link is held back the same way, for the same reason: walking it costs money at the seller.
A password is handed out one at a time
Who gets a password at all
Below manager a password is handed over only for a proxy that sits behind a profile actually opened to that person. A profile they created themselves does not count, or the rule would come down to knowing an identifier.
A manager and above refresh the whole library in one signed in pull, and that pull is recorded as a single line with a count.
What a teammate can still do
Checking an address is open to everyone in the workspace, because a profile could not be launched otherwise.
Asking the seller for a new address is not: on a shared mobile proxy that one press would cut every colleague's live session and spend the seller's paid limit.
When someone leaves
Profiles a departing person takes with them lose the pool address that stood behind them, matched by host, port and login.
So the working keys stay with the workspace that paid for them, and the person walks out with their own profiles rather than your traffic.
What this does not do
- It does not sell traffic. The pool holds addresses the workspace bought elsewhere.
- It does not hide that a password exists. The list says a password is set, so a teammate knows why the field is not empty.
- It does not give a junior role the whole pool. A refusal comes back rather than a shortened list pretending to be complete.
Where this is decided
Each claim above is one place in the code and one stand.
- The list has no password, a separate request hands one over, and the handover lands in the log
- apps/server/test/proxy-secret.js
- A junior role does not receive the passwords of the whole pool, and the change link stays out of the list
- apps/server/test/proxy-delivery.js
- A teammate who does not run the pool sends nothing up to it
- apps/desktop/test/proxy-library-sync.js
- The corporate address does not leave with a dismissed person's profiles
- apps/server/test/team-money-seats.js
Questions
- Can a teammate read the proxy password?
- Not from the list. It reaches their computer only for a proxy behind a profile opened to them, and the fact is written into the history log.
- Where do I see who took a password?
- On the History screen, under the line that says a proxy password was taken.
- Why can a colleague not change the IP of a shared proxy?
- Because it is one modem behind many windows. One press would drop every colleague's session and eat the seller's paid limit.
- Is the password kept in plain text on the server?
- No. It is sealed at rest, and the ordinary list never carries it out.
Try it on one address
The free plan gives two profiles, with no time limit and no card.