# One account, multiple organizations


Use one developer account across the teams you work with. You can belong to your company's organization and an open-source project's organization at the same time.

Your **account** is your sign-in identity. Each **organization** is a separate workspace. Switching organizations changes which workspace you are using.

## Example: company work and an open-source project

Alice uses Humanbased for two projects:

| Organization | Alice's role | Work managed there |
| --- | --- | --- |
| Acme Labs | Admin | The company's customer-support data Campaigns |
| Open Speech | Member | A community speech dataset |
| Alice's Lab | Owner | Independent experiments |

These are example names. Alice signs in once and switches organizations when moving between projects. Being an Admin at Acme Labs does not make Alice an Admin at Open Speech.



## Join a team or create a workspace?

**To work on an existing team's Campaign, join that team's organization.** Ask an Owner or Admin for an invitation, complete the joining process, and check that the organization appears in your account menu. Creating an organization with a similar name does not give you access to the original team's work.

**Create an organization when you need a separate workspace.** For example, you might create Alice's Lab for projects you run yourself. A new Campaign within the same team can use the organization's existing workspace.

Follow [Developer organizations](/collaboration/organization) for invitation, approval, and creation steps. Accept an email invitation with the account it was addressed to; a shared invite link can require approval before membership begins.

## Switch organizations

1. Select the account row at the bottom left of the Developer portal to open its menu.
2. Select an organization from your memberships. Each entry shows your role; a check mark marks the active organization.
3. Wait for the portal to reload, then confirm the organization name before continuing.

## What changes when you switch?

Your sign-in account stays the same. The Campaigns, keys, billing, and permissions you see are those of the selected organization. Switching does not move a Campaign or combine the organizations' resources.

An API key remains scoped to the organization that issued it. Selecting another workspace in the portal does not retarget a running integration. Use the correct organization's credential for your program.

## If something is missing

- **Organization missing?** Check that you signed in with the invited account and completed the invitation or approval process.
- **Organization visible, Campaign unavailable?** Ask its manager to check your Campaign access as well as your organization membership.
- **Switch failed?** Confirm the active organization before retrying; the portal may still be in the previous workspace.

Return to [Start with a data need](/start/developer-start) when your workspace and access are correct.
