Drıftstack docs
Docs

Only the team owner and admins can launch through the team’s proxies

You might be here because: “only the team owner and admins can launch through the team’s proxies” · “I can see the team proxies but can’t use them” · “proxy writes on a team owner require admin role” · “team member can’t start a session” · “the quick session was not started, only the team owner and admins” · “member_view proxies”

Short answer

In a team workspace, a team member can only see the team’s proxies by name — not their address, username, or whether a password is stored — and cannot launch through them. A team admin and the owner can. To launch through the team’s proxies, ask the team owner to make you an admin.

Check first

  • Which workspace are you in — your own, or the team’s? The rule applies only in the team’s.
  • What is your role on the team (member vs admin)?

Likely causes and fixes

  1. Launch from Profiles refused: “Only the team owner and admins can launch through the team’s proxies.”. Ask the owner for the admin role, or work in your own workspace with your own proxies.
  2. Chat: “Only the team owner and admins can start a chat through the team’s proxies.” Same rule.
  3. Quick session: “The quick session was not started: only the team owner and admins can start sessions through the team’s proxies.”.
  4. API: “Proxy writes on a team owner require admin role on that team.” Adding, editing or deleting a proxy in the owner’s workspace needs the admin role.
  5. Cap and VPN entitlement are the owner’s plan, whoever makes the request.
  6. A proxy the admin saved on their own account. The owner cannot list it or launch through it; a proxy on any other account is a 404.

If it still fails

Role changes are made by the team owner, not by support. If you are an admin (or the owner) and are still refused, press Talk to a person in this chat (or open Help) and include the workspace, your role and the exact sentence — a person should look.