GoLogin Shared Workspaces: One US Mobile Line per Profile
Published
GoLogin is the second profile browser we recommend, and for teams its workspace sharing is the feature that matters. A workspace lets several people run the same set of profiles from different machines while each profile stays pinned to one proxy. Paired with a fleet of Mobile Proxies USA lines, the result is a tidy grid: one line per profile, profiles grouped by client, people invited to the groups they need. This guide is about building that grid and keeping it straight as the fleet grows.
Workspace first, then profiles
Create a workspace for the team before creating profiles, and invite members with the role that fits them. Running profiles is a lower role than editing proxies; most of the team only needs the former. Inside the workspace, use folders per client or project. The structure should mirror the labelling you use in the dashboard at lines.mobileproxiesusa.com, so that a folder name and a line label mean the same thing in both places.
GoLogin keeps profiles in its cloud, so a profile started by one person on Monday can be continued by another on Tuesday with the same cookies and the same line. The line does not care which machine connects; the credentials work from anywhere.
One line per profile, entered once
In each profile's proxy settings, choose SOCKS5 and enter the line's host, SOCKS5 port, username and password from its dashboard row. GoLogin tests the connection and shows the exit country and city; it should read United States and a city in the line's state. Set the profile's time zone, language and geolocation to follow the proxy. Name the profile with the account name and the line label.
GoLogin also keeps a saved proxy list you can reuse across profiles. Save each line once, named by its label, and pick from the list when creating profiles for the same client. That prevents the slow drift where one profile has a typo in a port and nobody notices until an account looks odd.
- Open the line's row in the dashboard and copy host, SOCKS5 port, username and password.
- In GoLogin, create or edit a profile, choose SOCKS5 and paste the values; save the proxy to the list under the line's label.
- Run the connection test and confirm the state matches the line's metro.
- Set locale, time zone and geolocation to follow the proxy; name the profile after the account and the line.
- Place the profile in the client's folder and share the folder with the people who run that client.
How many profiles per line
The clean answer is as many as belong to one client and one operator, and no more. A line serving one client can hold that client's handful of accounts in a handful of profiles. The moment a second client's profile would land on the same line, order another line instead. The price per line is flat, so the decision is about separation rather than cost, and separation is why you are running dedicated lines at all.
Teams that hold one line per seat rather than per client work the same way: each person's profiles sit on that person's line, and the line label carries the seat name.
Rotation etiquette in a shared workspace
Because several people can open profiles on the same line, rotation needs a rule. The one that works: only the folder lead rotates, and only between sessions. The rotation link for each line is on its dashboard row; calling it gives the SIM a fresh address from the same carrier in the same metro. If a profile is open while the address changes, the open session simply continues on the new address, but it is cleaner not to do that mid-task.
For lines that should rotate on a schedule, set the timer on the dashboard row and note the interval in the folder description so everyone knows when addresses change. For lines that should stay put, leave the timer off; the address holds as long as the carrier keeps it.
Moves, renewals and the folder description
Use each GoLogin folder's description field as the operational note for that client's line: metro, carrier, term, renewal date, rotation rule. When a line is moved to another metro from the dashboard (free, remaining time kept), update the description and re-check the saved proxy, since credentials can change. When a monthly line renews, nothing in GoLogin changes.
Renewals are per line and auto-renew is optional per row. For a client fleet, switch auto-renew on for permanent lines and keep the account balance ahead of the renewal dates; the dashboard shows the sum due by date.
When someone leaves
Remove the member from the workspace. Then, for each line they ran profiles on, reset the credentials from the dashboard row and update the saved proxy in GoLogin. Profiles pick up the new proxy settings on next launch. Nobody else's lines are touched. The whole routine is short enough to run the same day, and it is the single most effective thing a team can do to keep its fleet its own.
If something about a line itself misbehaves, support is at [email protected] and on the Telegram bot at t.me/usamobileproxies_bot, any hour. Quote the line's label or its host and port.
Frequently asked
Can two team members run the same profile at once?
GoLogin locks a running profile so only one person has it open at a time. That is a feature; it also prevents two sessions on one account from the same line.
Why SOCKS5 rather than HTTP in GoLogin?
Both work on our lines. SOCKS5 also carries UDP and avoids some edge cases, so it is the default we suggest for profile browsers.
The test shows a different city than the line's metro. Is that wrong?
Check the state. Verizon can resolve to a regional hub; AT&T in Boston reads as New York. State and country are what you should expect to match.
Do I need the dashboard login for my team?
No. Keep the dashboard with the fleet owner. Team members only need the shared workspace; the proxy settings inside each profile carry the line.