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

# Apps and organizations

> Find and inspect your applications from the terminal, set a default organization, and view an app's users, namespaces, dashboards, and deploy markers.

Most CLI commands act on a single application in a single environment, so before you tail logs or list incidents, you need to know which apps you have and how to name them. This page covers listing your applications, setting a default organization, and inspecting an app's resources.

## Organizations

Your applications live under an organization, identified by its slug: the short name in your AppSignal URL, `appsignal.com/<org-slug>`. The CLI works with the organization tied to your signed-in account.

### Set a default organization

Most commands fall back to a default organization, so you don't need to pass `--org` every time. Running `appsignal-cli apps list` determines your account's organization and saves it as the default. To set or change it yourself:

```sh Shell theme={null}
appsignal-cli apps set-org --org <YOUR_ORG_SLUG>
```

To see the current default:

```sh Shell theme={null}
appsignal-cli apps show-org
```

You can also set the default during sign-in with `appsignal-cli auth login --org <YOUR_ORG_SLUG>`, or per project with `appsignal-cli project init --org <YOUR_ORG_SLUG>`. See [Authentication](/cli/authentication) for how the global and project-local configs relate.

## Applications

To list the applications for your account's organization:

```sh Shell theme={null}
appsignal-cli apps list
```

This also saves your organization as the default for later commands, so you don't need to pass `--org` to them.

### Find an app by name

To look up a specific app by name, optionally narrowing to one environment:

```sh Shell theme={null}
appsignal-cli apps find --name "MyApp" --environment production
```

The name and environment are both case-insensitive. This is the quickest way to confirm the exact app name and environment that other commands expect.

### Show details for an app

If you know an app's ID, you can fetch its details directly:

```sh Shell theme={null}
appsignal-cli apps info --app-id <APP_ID>
```

## How commands identify an app

Commands that act on a single app accept it in one of two ways:

* **By name:** `--app "MyApp"`. Add `--environment production` only when more than one app shares the name.
* **By ID:** `--app-id <APP_ID>`, the value from the `ID` column of `appsignal-cli apps list` (a long hexadecimal string). An ID identifies a specific app and environment on its own, so you don't pass `--environment` with it.

Use whichever you have. A name is easier to read and type; the ID is unambiguous and convenient in scripts.

## Inspect an app's resources

The `apps resources` commands show the configuration and metadata attached to an app:

| Command                         | Shows                             |
| ------------------------------- | --------------------------------- |
| `apps resources all`            | Every resource below, in one call |
| `apps resources users`          | Users with access to the app      |
| `apps resources notifiers`      | Configured notifiers              |
| `apps resources namespaces`     | The app's namespaces              |
| `apps resources dashboards`     | Custom dashboards                 |
| `apps resources deploy-markers` | Recent deploy markers             |

Each takes the same app selector as other commands, either `--app` with `--environment` or `--app-id`, and uses your default organization unless you pass `--org`. For example, to see the namespaces for an app:

```sh Shell theme={null}
appsignal-cli apps resources namespaces --app "MyApp" --environment production
```

To pull everything at once as JSON, for feeding into another tool:

```sh Shell theme={null}
appsignal-cli apps resources all --app "MyApp" --environment production --output json
```

## Next steps

Once you know an app's name and environment, you can start querying it. Inspect its [incidents](/cli/incidents) or tail its [logs](/cli/logs) from the terminal.