Team collaboration

LoadBolt is built for teams. Here's how to set up your org, invite people, and share results — without per-seat pricing getting in the way.

How LoadBolt is organized

Everything in LoadBolt lives under an org. Here's the hierarchy:

Org — your top-level account. Billing, domains, and members live here.
Teams — optional groupings within an org. Useful if you have multiple squads or departments.
Projects — folders for related tests (e.g. “API v2” or “Checkout flow”).
Tests — individual test configurations with scripts, VU settings, and variables.
Runs — each time you execute a test, it creates a run with its own results.

Creating an org and inviting members

When you sign up, LoadBolt creates a default org for you. To invite teammates, go to Settings → Members and add them by email. They'll get an invite link and can sign in with Google.

No per-seat pricing. Add as many people as you want. Your plan price doesn't change based on team size — it's based on VU-minutes, not headcount.

Roles explained

Every member has a role that controls what they can do:

Role	What they can do
Owner	Full control. Manage billing, delete the org, transfer ownership. One per org.
Admin	Manage members and settings. Add/remove domains. Everything except billing and deleting the org.
Member	Create projects, create tests, run tests, view all results. The default for most teammates.
Guest	View only. Can see projects, tests, and results but can't create or run anything. Good for stakeholders.

Teams

Teams are optional. If you're a small team, you probably don't need them — just put all your projects at the org level. Teams become useful when you have multiple squads who want to organize their projects separately.

Sharing results

All org members can see all projects and all test runs. There's no per-project access control — if someone is in your org, they can see everything. This is intentional: load test results are most useful when everyone on the team can reference them.

Need to share results with someone outside your org? Export them as PDF, CSV, or JSON from the run results page.

Domain verification is org-level

When you verify a domain (via DNS TXT record or HTML file at /.well-known/loadbolt-verify.txt), it's verified for the entire org. Any member can then run tests against that domain — you don't need to verify it per user.

Domain verification is a security feature. It prevents anyone from using LoadBolt to load test domains they don't own. Verify once, and your whole team is good to go.

Set up your team