> ## Documentation Index
> Fetch the complete documentation index at: https://daily-ms-pcc-self-hosted.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# pipecat cloud organizations

> pipecat cloud organizations manages Pipecat Cloud organizations and API keys: list, select, and manage from the CLI.

export const SelfHostedCliNote = () => <Note>
    Available in <code>pipecatcloud</code> {cliMinVersion} or later, for
    organizations with self-hosted regions enabled. See{" "}
    <a href="/enterprise/overview">Pipecat Enterprise</a>.
  </Note>;

export const cliMinVersion = "1.2.0";

The `organizations` command group helps you manage your Pipecat Cloud organizations and API keys. You can list and select organizations, as well as create, list, and manage API keys for use with the platform.

<Note>
  Organization and user management is not available via the CLI. Please use the
  [Pipecat Cloud Dashboard](https://pipecat.daily.co) to manage organizations
  and users.
</Note>

## list

Lists all organizations that your account has access to, highlighting the currently active one used for CLI operations.

**Usage:**

```shell theme={null}
pipecat cloud organizations list
```

## select

Changes your active organization for CLI operations.

This command either presents an interactive selection menu or directly sets a specified organization as your default. The selection is stored in your local configuration file (defaults to `~/.config/pipecatcloud/pipecatcloud.toml`) and used for all subsequent CLI commands.

**Usage:**

```shell theme={null}
pipecat cloud organizations select [OPTIONS]
```

**Options:**

<ParamField path="--organization / -o" type="string">
  Bypass prompt by directly specifying a namespace / organization string.
</ParamField>

## keys

The `keys` sub-commands manage API keys for authenticating with Pipecat Cloud services.

### keys list

Lists all API keys for the current organization.

**Usage:**

```shell theme={null}
pipecat cloud organizations keys list [OPTIONS]
```

**Options:**

<ParamField path="--organization / -o" type="string">
  Organization ID to list keys for. If not provided, the default organization
  will be used.
</ParamField>

### keys create

Create a new public API key for account / organization. Command will prompt the user to enter
a human-readable name for the key.

**Usage:**

```shell theme={null}
pipecat cloud organizations keys create [OPTIONS]
```

**Options:**

<ParamField path="--name / -n" type="string">
  Human readable name for the new key. Without it the command prompts, so CI
  needs to pass it.
</ParamField>

<ParamField path="--organization / -o" type="string">
  Organization ID to create key for. If not provided, the default organization
  will be used.
</ParamField>

<ParamField path="--default / -d" type="boolean" default="false">
  Set the new key as the active key in your local config.
</ParamField>

### keys revoke

Revoke an API key from your organization. Command will prompt the user to select which key they wish to revoke.

**Usage:**

```shell theme={null}
pipecat cloud organizations keys revoke [OPTIONS]
```

**Options:**

<ParamField path="--organization / -o" type="string">
  Organization ID to revoke key for. If not provided, the default organization
  will be used.
</ParamField>

### keys use

Sets a specific API key as your default for CLI operations.

The selected key is stored in the local configuration file (defaults to `~/.config/pipecatcloud/pipecatcloud.toml`) and will be used for all subsequent requests to the Pipecat Cloud API.

Please note that the key must be associated with the same user account or organization as you are making requests to.

If the public key is revoked or deleted via the dashboard, the user will need to re-run this command to select a new key.

**Usage:**

```shell theme={null}
pipecat cloud organizations keys use [OPTIONS]
```

**Options:**

<ParamField path="--organization / -o" type="string">
  Organization ID to select default key from. If not provided, the default
  organization will be used.
</ParamField>

## registry-keys

<SelfHostedCliNote />

The `registry-keys` sub-commands manage pull-only registry credentials. A registry key lets `helm` on your workstation fetch the region package for a [self-hosted region](/enterprise/setup). Keys are org-scoped, revocable, and shown exactly once at mint.

### registry-keys mint

Mint a registry key and print the matching `helm registry login` command.

**Usage:**

```shell theme={null}
pipecat cloud organizations registry-keys mint --name [NAME] [OPTIONS]
```

**Options:**

<ParamField path="--name" type="string" required>
  A label for the key, e.g. `acme-us-east-workstation`, used to tell keys apart
  in `list` and to revoke the right one. When run interactively without this
  option, the command asks for a name.
</ParamField>

<ParamField path="--organization / -o" type="string">
  Organization to mint the key in. If not provided, uses the current
  organization from your configuration.
</ParamField>

<Tip>
  With `--output json`, the key and the login command are emitted on stdout as
  `key` and `helmLoginCommand`.
</Tip>

### registry-keys list

List registry keys with their lifecycle metadata. Key material is never shown.

**Usage:**

```shell theme={null}
pipecat cloud organizations registry-keys list [OPTIONS]
```

### registry-keys revoke

Revoke a registry key. The command prompts for confirmation; pass `--force` to skip it.

**Usage:**

```shell theme={null}
pipecat cloud organizations registry-keys revoke [KEY_ID] [OPTIONS]
```

**Options:**

<ParamField path="--force / -f" type="boolean" default="false">
  Bypass the confirmation prompt.
</ParamField>

<ParamField path="--organization / -o" type="string">
  Organization the key belongs to. If not provided, uses the current
  organization from your configuration.
</ParamField>

## properties

The `properties` sub-commands manage organization properties such as default region settings.

### properties list

Lists all current property values for your organization.

**Usage:**

```shell theme={null}
pipecat cloud organizations properties list [OPTIONS]
```

**Options:**

<ParamField path="--organization / -o" type="string">
  Organization ID to list properties for. If not provided, the default
  organization will be used.
</ParamField>

### properties schema

Shows available properties with detailed metadata including type information, current values, default values, and available values.

**Usage:**

```shell theme={null}
pipecat cloud organizations properties schema [OPTIONS]
```

**Options:**

<ParamField path="--organization / -o" type="string">
  Organization ID to show properties schema for. If not provided, the default
  organization will be used.
</ParamField>

### properties set

Updates a specific organization property.

**Usage:**

```shell theme={null}
pipecat cloud organizations properties set PROPERTY_NAME VALUE [OPTIONS]
```

**Arguments:**

<ParamField path="PROPERTY_NAME" type="string" required>
  Name of the property to set (e.g., `defaultRegion`)
</ParamField>

<ParamField path="VALUE" type="string" required>
  Value to set for the property
</ParamField>

**Options:**

<ParamField path="--organization / -o" type="string">
  Organization ID to update property for. If not provided, the default
  organization will be used.
</ParamField>

**Example:**

```shell theme={null}
pipecat cloud organizations properties set defaultRegion eu-central
```

## default-region

Convenience command to get or set the default region for your organization.

**Usage:**

```shell theme={null}
pipecat cloud organizations default-region [REGION] [OPTIONS]
```

**Arguments:**

<ParamField path="REGION" type="string">
  Region to set as default. If omitted, displays the current default region and
  available regions.
</ParamField>

**Options:**

<ParamField path="--organization / -o" type="string">
  Organization ID to configure. If not provided, the default organization will
  be used.
</ParamField>

**Examples:**

View current default region:

```shell theme={null}
pipecat cloud organizations default-region
```

Set default region:

```shell theme={null}
pipecat cloud organizations default-region eu-central
```

***

<Card title="More about organizations" icon="people-group" href="/pipecat-cloud/fundamentals/accounts-and-organizations">
  Managing your account and collaborating on agents as part of a team
</Card>