> ## Documentation Index
> Fetch the complete documentation index at: https://capy.sc/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Switch Between Capy Organizations on One Machine

> Use capy org to switch your active organization for org-scoped commands. Projects stay bound to their org via keep.lock — multi-org workflows are seamless.

If you belong to multiple Capy organizations, use `capy org` to switch the active org for your current shell session.

```bash theme={null}
capy org
```

Capy shows your orgs in an interactive list. Pick one and it becomes the default for future `capy` commands in this project.

## Per-project org binding

Each initialized Capy project (directory with a `keep.lock`) is bound to a specific org - you don't accidentally sync the wrong secrets into the wrong place. `capy org` switches what gets used **for operations that aren't already project-scoped** (like `capy invite` or creating a new project).

For an existing project, the org binding is baked into `keep.lock` and doesn't change.

## Redeeming an invite into a new org

If someone invites you to a new org, running `capy redeem <code>` will:

1. Authenticate you (or reuse an existing session).
2. Switch the active org to the one you're joining.
3. Install the master key for that org into your local keyring.

From then on, `capy org` will list the new org alongside any others you belong to.

## What's next

<Card title="Inviting users" icon="user-plus" href="/using/team/inviting" horizontal>
  Add someone to your org.
</Card>