Organizations and regions
Organizations
An organization is a workspace. It owns its agents, phone numbers, documents, credit and members - nothing is shared with another organization.
One account can own or belong to several and switch between them. Use separate organizations for genuinely separate businesses; use projects and environments to separate work inside one.
Members and roles
Invite people by email and give them a role. Roles decide what a member can do - read, build, publish, run calls, manage billing - so a teammate iterating on prompts does not also have to be able to change payment details.
Regions
Each organization is created in a region, which is where its data lives. The region is chosen at creation and is immutable afterwards: moving data between jurisdictions is not something that should happen silently, so it does not happen at all.
If you need an organization in a different region, create one there. The same account can hold both and switch between them.
Model providers process conversation content on their own infrastructure, which may be outside your region. If that matters for your compliance posture, use your own keys with a provider and endpoint you have chosen.
Environments
Agents can be promoted between environments, so what you test is not what your callers are already using. Combined with versions, an edit never reaches production until you publish it.