Organizations

An organization is the top-level container for your API keys, baselines, and jobs in RegressionBot. Every account belongs to exactly one organization at a time. Multiple team members can share the same org — each member gets a role that determines what they can do.

Creating your organization

The first time you log in after signing up, you land on an onboarding screen with two options:

Create a new organization

Enter a name for your organization (up to 100 characters).
Click Create Organization.
Your account is set as the owner. You are redirected to the dashboard and can start creating API keys immediately.

Join an existing organization

If a team member has already created an org and sent you an invite, open the invite link from your email instead of creating a new org. See Accepting an invite below.

Inviting team members

Admins and owners can invite new members from the Team tab in the dashboard. An invite is sent by email and is tied to the specific email address — a different account cannot claim it.

How to send an invite

Open the Team tab in the dashboard.
Click Invite member.
Enter the recipient's email address and choose a role: admin or member. The owner role cannot be assigned via invite.
Click Send invite. An email is dispatched with an acceptance link. The invite also appears in the pending list so you can revoke it before it is accepted.

Invite expiry: Invites expire after 7 days. Expired invites cannot be claimed. To re-invite someone after expiry, revoke the existing invite from the Team tab and send a new one.

Accepting an invite

Open the invite email and click the acceptance link. The page shows the organization name, your assigned role, and who invited you.
If you do not have an account yet, click Create account. Register with the exact email address the invite was sent to, then verify your email.
If you already have an account, log in with the account whose email matches the invite.
Click Accept invite. You join the organization immediately and are redirected to the dashboard.

You can only belong to one organization.

If you already have an account that belongs to another organization, you must leave that organization before you can accept a new invite. Owners cannot leave — they must delete their org first. See Leaving an organization below.

Roles

Every member has one of three roles. The table below shows what each role can do.

Permission	Member	Admin	Owner
View org details and usage	✓	✓	✓
Manage API keys	—	✓	✓
View team members	✓	✓	✓
Invite members	—	✓	✓
Revoke pending invites	—	✓	✓
Remove members (non-admin only)	—	✓	✓
Change member roles	—	—	✓
Rename organization	—	—	✓
Delete organization	—	—	✓
Leave organization	✓	✓	— (must delete)

Note: The member role cannot view, create, or delete API keys in the dashboard. If a team member needs to manage keys for CI/CD pipelines, invite them as admin. Existing CI jobs keep working because API keys are organization-scoped.

Leaving an organization

Members and admins

Go to Account Settings in the dashboard and click Leave organization. Your membership is removed immediately. The org, its projects, and baselines are not affected. After leaving, you will need to create a new org or accept a new invite before you can use the dashboard again.

Owners

Owners cannot leave. The only exit path is to delete the organization. Deleting permanently removes all projects, baselines, API keys, and members. This cannot be undone.

Ownership transfer is not yet supported. If you need to leave while keeping the org intact, contact support.

API keys and organizations

API keys are scoped to the organization, not to the individual user who created them. When a request arrives using an API key, the org context is resolved automatically from the key — your code never needs to pass an org ID. All jobs, project lookups, and status queries run in the scope of the key's organization.

Adding or removing team members has no effect on existing API keys or how programmatic integrations work. A CI pipeline that runs:

Terminal

export REGRESSIONBOT_API_KEY="your_api_key_here"
npx regressionbot@latest https://staging.myapp.com \
  --against https://myapp.com

This continues to work identically after a new team member joins. No code changes, no reconfiguration. The key carries all the org context needed — the team structure is invisible to the API.

If a key stops working after joining an org: The key was likely generated under a different org (for example, a legacy single-user org before the team was set up). Have the key's owner create a new key from the dashboard while their account is in the correct org, then update the value in the CI environment variable.

Troubleshooting

Invite link shows "not found or expired"

The invite is more than 7 days old or was revoked by an admin. Ask an admin or owner to revoke the old invite and send a new one.

403 — "Invite was sent to a different email address"

The account you are logged in with does not match the email the invite was sent to. Log out and sign in with the correct account, or register a new account using the exact invited email address.

403 — "Email address must be verified"

Your account's email is not yet verified. Check your inbox for the verification email from RegressionBot, click the link, and then try accepting the invite again.

409 — "Already a member of an org"

Your account is already in an organization. Leave your current org from Account Settings first, then accept the invite. If you are the owner, you must delete the current org before you can join another.

Dashboard shows "needs onboarding" after login

Your account is not yet associated with an organization. Refresh the page — you will be redirected to the onboarding screen to create a new org or accept a pending invite.