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

# Global Flags

> Reference for global flags in the SuprSend CLI like config, workspace, service token, output, and verbosity available with every suprsend command.

## Available Flags

| Flag | Default | Env Var |
| - | - | - |
| `--config string` | `$HOME/.suprsend.yaml` | – |
| `-h, --help` | – | – |
| `--no-color` | Disabled | `NO_COLOR` |
| `-o, --output string` | `pretty` | – |
| `-q, --quiet` | Disabled | – |
| `-s, --service-token string` | – | `SUPRSEND_SERVICE_TOKEN` |
| `-v, --verbosity string` | `info` | – |
| `-w, --workspace string` | `staging` | – |

## Syntax and Example Usage

### --config

**string**\
Path to configuration file. Defaults to `$HOME/.suprsend.yaml`.

```bash theme={"system"}
suprsend --config /path/to/config.yaml workflow list
```

### --help, -h

Show help information for any command.

```bash theme={"system"}
suprsend --help
suprsend -h
suprsend workflow --help
suprsend workflow -h
suprsend workflow list --help
suprsend workflow list -h
```

### --no-color

By default, output is colored. \

You can disable colors when piping results to scripts, log files, or CI systems where ANSI codes may cause issues.
This can also be set globally via the `NO_COLOR` environment variable.

```bash theme={"system"}
suprsend --no-color workflow list

# Set globally via environment variable
export NO_COLOR=1
```

### --output, -o

**string**\
Default - `pretty`. \

Output format: `pretty`, `yaml`, or `json`.\

Use `json` or `yaml` when piping results to other tools or scripts, and `pretty` for human-friendly interactive use.

```bash theme={"system"}
suprsend workflow list --output yaml
suprsend workflow list --output json | jq '.[].name'
```

### --service-token, -s

**string**\
For locally overriding the authentication token. \

It is not recommended to use this flag in scripts or CI systems, since it will be visible in shell history or process listings.
Instead, set the environment variable `SUPRSEND_SERVICE_TOKEN`.

```bash theme={"system"}
suprsend workflow list --service-token "your_token_here"
suprsend workflow list -s "your_token_here"

# Set globally via environment variable
export SUPRSEND_SERVICE_TOKEN="your_token_here"
```

### --verbosity, -v

**string**\
Default - `info`.\

Log level (in increasing order of severity): `debug < info < warn < error < fatal < panic`. Each level includes logs from all levels below it. \

Use higher levels like `warn` or `error` in scripts for cleaner logs, and `debug` during troubleshooting to see detailed request and response information.

```bash theme={"system"}
suprsend workflow list --verbosity debug
suprsend workflow list -v debug

# You can also set debug mode globally via environment variable
export DEBUG=true
```

### --workspace, -w

**string**\
Target workspace for commands. Defaults to `staging`.

```bash theme={"system"}
suprsend --workspace production workflow list
suprsend -w production workflow list
```


## Related topics

- [Commands and Flags](https://docs.suprsend.com/reference/cli-template-overview.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.