> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/snyk-cli/scan-and-maintain-projects-using-the-cli/how-to-select-the-organization-to-use-in-the-cli.md).

# How to select the Organization to use in the CLI

How to select the Snyk Organization to use in the CLI

When you run commands with the CLI such as `snyk monitor` and `snyk test`, Snyk uses your `Preferred Organization`, which can be configured in your account. If you want commands to run against a different Organization, you can specify that Organization either globally or individually.

**Note**: The Snyk CLI help specifies using `--org=<ORG_ID>`; this article specifies using the `orgslugname`. The `ORG_ID` works in both the CLI and the API. The organization slug name works in the CLI, but not in the API.

## Specify an Organization globally

Run `snyk config set org=orgslugname`. Note: `orgslugname` must match the slug name as displayed in the URL of your org in the Snyk UI: `https://app.snyk.io/org/[orgslugname]`.

## Specify an Organization individually

To override this global configuration for individual runs, specify the Organization as follows:

`snyk monitor --org=orgslugname` or `snyk test --org=orgslugname`.

Example: `$ snyk test --org=my-team`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/developer-tools/snyk-cli/scan-and-maintain-projects-using-the-cli/how-to-select-the-organization-to-use-in-the-cli.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.