> This page location: Neon platform > Access & collaboration > Organizations > CLI > CLI actions
> Full Neon documentation index: https://neon.com/docs/llms.txt

# Manage Organizations using the Neon CLI

Neon's CLI provides an expanding set of commands to manage your organizations.

## Authorization

Use the `auth` command to authenticate your Neon account from the CLI. This command opens a browser where you will be asked to grant the necessary permissions to manage your Neon resources across all organizations you belong to. Your OAuth token is stored in `~/.config/neonctl/credentials.json`.

Authentication is tied to your Neon user account. Once authenticated, you can access and manage any organization you belong to. When running commands, you'll need to specify which organization to use via `--org-id`, a [context file](https://neon.com/docs/reference/cli-set-context), or by responding to the interactive prompt.

See [Auth - CLI](https://neon.com/docs/reference/cli-auth) to learn more.

## List Organizations

The `neon orgs list` command outputs a list of all organizations that the CLI user currently belongs to. This command is useful for quickly identifying the `org_id` associated with each organization, which can be used in other CLI operations.

Example:

```bash
neon orgs list
Organizations
┌────────────────────────┬──────────────────┐
│ Id                     │ Name             │
├────────────────────────┼──────────────────┤
│ org-ocean-art-12345678 │ Example Org      │
└────────────────────────┴──────────────────┘
```

See [Orgs - CLI](https://neon.com/docs/reference/cli-orgs) to learn more.

## Manage projects within an Organization

The Neon CLI `projects` command supports an `--org-id` option. This allows you to list or create projects within a specified organization.

Example: Listing all projects in an organization:

```bash
neon projects list --org-id org-xxxx-xxxx
Projects
┌───────────────────────────┬───────────────────────────┬────────────────────┬──────────────────────┐
│ Id                        │ Name                      │ Region Id          │ Created At           │
├───────────────────────────┼───────────────────────────┼────────────────────┼──────────────────────┤
│ bright-moon-12345678      │ dev-backend-api           │ aws-us-east-2      │ 2024-07-26T11:43:37Z │
├───────────────────────────┼───────────────────────────┼────────────────────┼──────────────────────┤
│ silent-forest-87654321    │ test-integration-service  │ aws-eu-central-1   │ 2024-05-30T22:14:49Z │
├───────────────────────────┼───────────────────────────┼────────────────────┼──────────────────────┤
│ crystal-stream-23456789   │ staging-web-app           │ aws-us-east-2      │ 2024-05-17T13:47:35Z │
└───────────────────────────┴───────────────────────────┴────────────────────┴──────────────────────┘
```

You can include the `org-id` to apply the following subcommands specifically to your organization:

- [List projects](https://neon.com/docs/reference/cli-projects#list)
- [Create projects](https://neon.com/docs/reference/cli-projects#create)

See [Projects - CLI](https://neon.com/docs/reference/cli-projects) to learn more.

## Setting Organization Context

To simplify your workflow, the Neon CLI `set-context` command supports setting an organization context. This means you don't have to specify an organization ID every time you run a CLI command.

Sees [set-context - CLI](https://neon.com/docs/reference/cli-set-context) to learn more.