Skip to main content
To work as a team on boat, create an organization. It has one plan, one wallet, and members who run sandboxes on it.
  • The organization pays the plan price once per seat. A 5-seat organization on the $20 plan pays $100 a month.
  • Each seat adds the plan’s included time. It adds the full limits on the $2000 plan, and 20% of them below. Read Seats, limits and caps.
  • Organizations get no free trial.
  • The API and the CLI also call an organization org, and some fields call it team (teamId, team_… ids). All three name the same thing.
For everyone who can reach a sandbox, in and out of the team, read Security and isolation.

Members and invites

The owner invites people by email.
  1. The person opens the link in the email.
  2. The person signs in with any sign-in method.
  3. The organization shows in their boat org list and in the Viewing dropdown of the dashboard.
To remove a member, change roles or set per-member caps, use the Organization tab of the dashboard. When a member leaves, the sandboxes that they created go back to their personal billing.

Rename an organization

Only the owner can rename the organization.
  1. Open the Organization tab and select the organization in the sidebar.
  2. Select Rename, type the new name, and select Save.
  3. Read the warning and select Rename to confirm.
The id (team_…) does not change. After the rename, --org, ?org= and X-Boat-Org accept the new name only. Update the scripts that use the old name, or use the id. New invoices show the new name when the billing name is still the organization name. A billing name that you entered at checkout does not change. Invoices that already exist keep their name.

Limit who can use an environment or profile

By default, every member can use each organization environment and each organization credential profile. An owner or admin can limit an environment to a list of members. An owner can do the same for a profile. A member who is not on the list:
  • Does not see the environment or the profile in lists.
  • Cannot create, resume or fork a sandbox in the environment. boat returns 403 environment_forbidden.
  • Cannot pick the profile. When an environment that they can use names the profile, their sandboxes get their own default profile.
Other rules:
  • An API key acts as the person who created it. It never reaches more than that person can. The environment scope of a key limits it more.
  • A change to the list does not change sandboxes that are already running.
  • Teammates already cannot use a sandbox that holds another person’s secrets. Read Shared sandboxes.
  • members takes member ids or the emails of active members. It replaces the full list.
  • The environment and the profile objects return access: { restricted, members }, with member ids.
  • A bad list returns 400 invalid_access.
On the dashboard, open the environment page or the AI credentials page. The Who can use this environment or Who can use this profile panel has two choices: Everyone in <org> or Only the people ticked below.

Where to do what

* The account API is the one that the dashboard uses. Its base is https://boat.dev/api/boat, not $BOAT_API_BASE. Organization routes are under /teams/{org}/… and billing routes under /billing/… with teamId in the body. These routes are not in the v1 API reference and can change. The plan, the wallet and running out work the same on an organization as on a personal account. Read Plan, wallet and running out.

Learn more

Which wallet a sandbox bills

Set the active wallet, or bill one sandbox to another wallet.

Shared sandboxes

What each member can do with a sandbox. Share a sandbox or make it private.

Seats, limits and caps

Buy seats, share start and concurrency limits, and cap each member.

Move a personal plan in

Move your personal sandboxes and plan to the organization.

Card, invoices and plan changes

Cancel, downgrade, refunds, and move an organization plan back to personal.