# Share API credentials with your team (/connect/use-your-own-keys/share-api-credentials)



## What are workspace API credentials? [#what-are-workspace-api-credentials]

API credentials are workspace-level provider keys for AI teammates. Inviting a human teammate does not import that person's personal OpenAI, Anthropic, or DeepSeek key.

## How to Share API Credentials [#how-to-share-api-credentials]

<Steps>
  <Step>
    ### Open Models [#open-models]

    Go to **Settings → Workspace → Models**. This page lists the provider keys available to AI teammates in this workspace. If you only see a read-only list, ask a workspace admin to add or change credentials.

    <LivePreview component="ModelsSettings" />
  </Step>

  <Step>
    ### Add a workspace credential [#add-a-workspace-credential]

    Workspace admins click **Add provider**. Use one credential for a shared provider budget, or create separate credentials when different teams, customers, or projects need separate billing.

    <LivePreview component="ModelsSettings" scenario="{ dialog: &#x22;provider&#x22; }" />
  </Step>

  <Step>
    ### Fill the credential form [#fill-the-credential-form]

    Choose the provider, enter a clear label, paste the API key, and save. Use labels like `prod-anthropic`, `growth-openai`, or `support-deepseek` so teammates can pick the right credential later. Helio stores the secret and does not show the raw key again after submit.

    <LivePreview component="ModelsSettings" scenario="{ dialog: &#x22;provider&#x22; }" />
  </Step>

  <Step>
    ### Check who uses the credential [#check-who-uses-the-credential]

    Open the AI teammate's **Teammate Settings → Profile → Models** before deleting or rotating a provider source. If the model is in use, switch that teammate to another source first.

    <LivePreview component="AssistantProfile" />
  </Step>
</Steps>

<Callout type="info">
  Workspace API credentials are for AI teammate execution. They do not reveal a human teammate's secret to other humans, and inviting a member does not copy their personal API account into Helio.
</Callout>

## Common choices [#common-choices]

| If you want...                            | Do this                                                                                               |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| One shared AI-provider budget             | Add one workspace credential and assign multiple AI teammates to models from it.                      |
| Separate budgets                          | Add multiple credentials with clear labels, then choose the right credential per AI teammate.         |
| A new human teammate to use their own key | Ask an admin to add that key as a workspace credential, or keep the teammate on Helio-managed access. |
| To stop using a key                       | Reassign AI teammates first, then rotate or delete the credential.                                    |

<Cards>
  <Card title="Use your own keys" href="/connect/use-your-own-keys" description="Understand BYOK and supported providers." />

  <Card title="Invite teammates" href="/get-started/invite-teammates-to-workspace" description="Invite humans and manage channel access separately." />

  <Card title="Anthropic API key" href="/connect/use-your-own-keys/connect-anthropic-api-key" description="Add an Anthropic provider key." />

  <Card title="OpenAI API key" href="/connect/use-your-own-keys/connect-openai-api-key" description="Add an OpenAI provider key." />
</Cards>