Set up an organization

Organizations are currently in private beta. If you’d like to participate, please contact us at support@cartesia.ai or in your dedicated Cartesia Slack channel.

Please let us know if you have any feedback or suggestions!

We support organizations for customers on the Startup plan and above.

1

Request access to organizations

To request access to organizations, please share an email address for your organization’s admin with us. This email address will go through the organization creation flow and invite your team to join.

2

Create an organization

Once we grant access to organizations, you can create an organization by going to the playground at https://play.cartesia.ai, selecting the organization switcher, and clicking Create organization.

Create organization

This will bring up a dialog where you can name your organization, upload a logo, and invite your team. You can invite unlimited users to your organization at no additional charge.

Organization creation dialog
Invite team members
3

Let team members know to accept the invitation

Once you invite a team member, they will receive an email with a link to accept the invitation. They can also directly go to the playground and select the organization switcher (pictured above) to accept the invitation.

4

Create voices, API keys, and other resources in your organization

Once you create an organization, you can create voices, API keys, and more in the organization. They will be available to all users in the organization. The only exceptions are playground generation history and starred voices, which are per-user in the organization.

Migrating from a single account with multiple linked emails to an organization

This migration path is mainly for users who have already created voices and API keys in a multi-email account and are using them in production. If this does not apply to you, we can directly migrate your voices to your organization.

Prior to organizations, we recommended linking each team member’s email to a single Cartesia account to share resources like voices and API keys. This will continue to be supported, but we recommend migrating to organizations as it makes access control easier.

Because voices from multi-email accounts are not accessible with your organization’s API keys, you cannot simply change your production API key to use your organization’s API key. Instead, we recommend working with us to migrate your voices to your organization. Here’s what the migration process looks like:

1

Follow the guide above to create an organization and invite your team

2

We temporarily allow your voices to be accessible with your organization’s API key

Let us know that you’ve created an organization, and we’ll temporarily allow your voices to be accessible using your organization’s API key.

Note that these voices will not be visible on the playground, but they will be accessible to your organization via the API.

3

Test that you can access your voices using your organization’s API key

We recommend testing that you can access your voices using your organization’s API key using the following script:

1from cartesia import Cartesia # pip install cartesia
2import os
3
4client = Cartesia(api_key=os.getenv("CARTESIA_API_KEY")) # your *organization* API key (not the multi-email account's API key!)
5
6voice_ids = [
7 # list of voice IDs you're using in production
8]
9
10for voice_id in voice_ids:
11 voice = client.voices.get(id=voice_id)
12 print(voice.name)

If this script runs successfully, proceed to the next step.

4

Change your production API key to use your organization’s API key

Once you’ve tested that you can access your voices using your organization’s API key, you can change your production API key to use your organization’s API key.

5

We transfer the voices to your organization

We will fully transfer the voices to your organization, rendering them inaccessible to you via the old multi-email account’s API key.

6

Remove extra emails from the multi-email account

Once the migration is complete, you can remove the extra emails from the multi-email account.

Migrating billing

Billing is per-workspace, so you will need to check out again as the organization in order to migrate billing and tier information.

  1. If you are on the Startup or Scale plan, you will have to check out again through the organization’s “Subscription” page.
  2. If you are on the Enterprise plan, we will send you a new invoice for the organization.

In either case, we will refund your multi-email account and set its subscription to expire at the end of the current period. Note that this means you will have to set your production API key to use your organization’s API key before the end of the current period.