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

# Authentication

> Sign in through the browser and manage credentials for one or more workspaces.

The CLI uses your browser to sign you in and securely saves your session, so you never need to enter an API key.

## Sign in

```bash theme={"system"}
neetoauth login --subdomain your-workspace
```

Your browser opens to complete sign-in. Once you approve it, the CLI saves credentials for that subdomain. If you omit `--subdomain`, the CLI prompts for it.

<Tip>
  Your subdomain is the first part of your workspace URL - for
  `https://spinkart.neetoauth.com`, the subdomain is `spinkart`.
</Tip>

## Where credentials are stored

Credentials for every signed-in workspace live in a single file:

```
~/.config/neetoauth/auth.json
```

Removing this file signs you out of every workspace, the same as `neetoauth logout --all`.

## Check who you are

```bash theme={"system"}
neetoauth whoami
```

Lists every signed-in account. When exactly one is signed in, it is marked `(default)`. Pass `--subdomain <name>` to show just one.

## Sign out

```bash theme={"system"}
neetoauth logout --subdomain your-workspace    # remove one workspace
neetoauth logout --all                         # remove every workspace
neetoauth logout                               # remove the only one, if a single workspace is signed in
```

## Working with multiple workspaces

You can sign in to several subdomains at once. To add another workspace, name its subdomain:

```bash theme={"system"}
neetoauth login --subdomain globex
```

When more than one workspace is signed in, every command that talks to the API requires `--subdomain`, including `doctor`. If you omit it, the CLI errors and lists the signed-in workspaces.

```bash theme={"system"}
neetoauth users list --subdomain acme
neetoauth users list --subdomain globex
```

With one signed-in workspace, it is the default and `--subdomain` stays optional.

## What your session can do

A CLI session acts as you, not as the workspace. Commands are checked against your own permissions, so a member who cannot invite people in the NeetoAuth UI cannot invite them through the CLI either. This differs from an API key, which is not tied to a person and is scoped to the whole workspace.

## Troubleshooting

If sign-in or connection problems come up, run `neetoauth doctor` first. See [Troubleshooting](/cli/troubleshooting) for common issues and fixes.