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

# Authentication, organizations, and profiles

> Keep work and personal accounts separate and select where your agent usage is recorded.

A **profile** stores an Edgee login and its selected organization. An **organization** owns the keys, settings, and usage for your sessions. Check both when usage appears in the wrong place.

## Sign in

```bash theme={"dark"}
edgee auth login
edgee auth status
```

Complete sign-in in the browser and return to the terminal. When your account belongs to several organizations, select the one you intend to use. If none is available, create an organization in the [console](https://www.edgee.ai/login), or accept your team’s invitation using the invited email.

## Change organization

```bash theme={"dark"}
edgee auth orgs
edgee auth orgs --set your-org-slug
```

`orgs` lists accessible organizations and marks the active one. `--set` accepts its slug or ID. After switching, the CLI provisions the new organization's agent keys on the next launch rather than reusing the old organization's keys.

**Verify:** run `edgee auth orgs` again, launch one request, and find it in that organization's **Sessions** page.

## Keep separate profiles

```bash theme={"dark"}
edgee -p work auth login
edgee -p personal auth login
edgee auth list
edgee auth switch
edgee -p work launch claude
```

`auth switch` selects the default active profile interactively. `-p` selects one for a command. Put `-p` before `auth`, `launch`, or another subcommand; after an agent name, arguments belong to the agent.

## Sign out

```bash theme={"dark"}
edgee auth logout
```

This clears the active profile's login and organization-scoped agent credentials. To sign out of every profile, use `edgee auth logout --all`. URL overrides and other non-login preferences remain.

Signing out of Edgee does not uninstall your agent or remove its own provider account.

## Automation-friendly output

```bash theme={"dark"}
edgee auth status --help
edgee auth orgs --json
edgee auth login --org your-org-slug --json
```

Login still requires browser authentication. JSON output does not turn it into an unattended service-account login. For application automation, use a [Gateway API key](/docs/llm-router/quickstart/api-key) or a [Console API token](/docs/api-reference/console-api-setup), depending on the API you need.