Teams

A team is a shared identity that multiple people can open tunnels under. Tunnels, reserved subdomains, and worker tunnels created in a team context belong to the team — not to whoever opened them — so they survive offboarding and onboarding without any URL changes.

Creating a team

From the dashboard, pick a slug (3–32 characters, lowercase alphanumerics and hyphens) and a display name. The slug becomes the team:<slug> identity you use in the CLI.

A few things happen at creation time:

• Slug uniqueness is enforced — duplicates return a conflict error.
• The creator gets the owner role and is set as the billing admin.
• A team Stripe subscription is created if you're upgrading from a personal Pro plan; the Pro subscription is cancelled with proration at the same time.

Roles

Three role concepts exist on a team:

Role	Granted to	Powers
Owner	The team creator	Full admin powers. Only the owner can dissolve the team. Transferred separately from billing-admin — see Billing admin.
Admin	Anyone who accepts an invitation, plus the owner	Invite teammates, remove members, manage workers and reserved subdomains.
Billing admin	Tracked separately from role	The user whose Stripe customer the team is billed against. Only one per team. Cannot be removed until the role is transferred — see Billing admin.

In practice this means a team always has at least one human who can pay the bill, and that person cannot be accidentally removed.

Inviting teammates

Team admins send invitations from the dashboard. Each invitation:

• Is valid for 7 days from the time it's sent.
• Is identified by a secure token sent in the invite email.
• Is capped at 20 pending invitations per team — accept or cancel existing invites before creating more.

When the invitee clicks the accept link, they're added as an admin and the team's Stripe subscription seat count is bumped (if the team is on the Team plan).

Removing a member

Admins can remove any member from the team settings page with a couple of guardrails:

• Cannot remove the billing admin. Transfer the billing-admin role first — see Billing admin.
• Cannot remove the sole admin. You can't leave the team without any leadership.

When a member is removed, the server immediately retires any team-scoped worker tunnels they were running, so their workers stop accepting traffic under the team's namespace. Their personal account and personal workers are not affected.

CLI usage

Once invited and accepted, switch into the team context to open tunnels under it:

justtunnel context use team:acme
justtunnel 3000

The tunnel counts against the team's limits, and any reserved subdomain you use stays with the team rather than your personal account. See Contexts for how the context system works.

Related

• Billing admin — transfer billing-admin, transfer ownership, delete a team
• Workers — long-lived team-scoped tunnels
• Plans and limits — team-tier numeric limits
• Contexts — switching identities at the CLI
• justtunnel context — CLI commands for context management