# Sign In and Credentials

```bash
micromeet crms login --region SG     # SG, HK or ID
micromeet crms auth status --check   # who am I, is the sign-in still valid
micromeet crms logout
```

- Leave out `--email` and `--password` and the CLI asks for them; the password is not shown while you type. Avoid `--password` on the command line: it can stay in your shell history.
- If your account has several institutions, the CLI lists them and asks for one. In scripts, pass `--iid <institution id>`.
- If it says the account still needs activation, run `micromeet crms auth set-password`.

## Where the sign-in is kept

The sign-in is saved encrypted in `~/.micromeet/credentials/crms.json`. When you sign in to Cowork, Cowork writes this file too, so the CLI uses the same account.

## In scripts

```bash
MICROMEET_CRMS_EMAIL=user@example.com \
MICROMEET_CRMS_PASSWORD='…' \
micromeet crms login --region SG --iid 42 --json
```

Add `--json` to any command for machine-readable output.

## Related

- [Sign In and Regions](https://docs.micromeet.ai/getting-started/sign-in-and-regions.md)
- [Command Reference](https://docs.micromeet.ai/cli/command-reference.md)