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

# account

> View, list, and switch the active Landbase account the CLI operates on

View the active account, list every account you can access, switch between
them, and list the users you can assign campaigns or dialer sessions to. The
active account scopes account-level commands such as
[`onboarding`](https://www.landbase.com/docs/reference/onboarding),
[`contacts-import`](https://www.landbase.com/docs/reference/contacts-import), and
[`dialer-sessions`](https://www.landbase.com/docs/reference/dialer-sessions).

> [!NOTE]
>
> `account` is a **platform-mode** command (platform mode is the default). Run
> [`landbase-cli auth login`](https://www.landbase.com/docs/reference/auth) first — `account list`,
> `account users`, and `account set` call the platform. See
> [platform mode vs. legacy mode](https://www.landbase.com/docs/overview/concepts/platform-vs-legacy.md).

## account

Print the currently active account as JSON. This reads the stored config only —
no network call — so it is safe to run even with an expired session.

**Usage**

```bash theme={null}
landbase-cli account
```

Prints `{ accountId, source }`, where `source` is `"config"` when an account is
set or `"none"` when it isn't. See [output schemas](https://www.landbase.com/docs/reference/output-schemas.md#account).

***

## account list

List every account the current user can access, marking which one is active.

**Usage**

```bash theme={null}
landbase-cli account list
```

Prints `{ accounts: [{ id, name, role, current }] }`. `current` reflects the
account the CLI would use right now. See
[output schemas](https://www.landbase.com/docs/reference/output-schemas.md#account).

***

## account users

List the users of the **active account** you can assign campaigns or dialer
sessions to. Unlike `account list` (your memberships across accounts), this is
account-scoped: removed members are never listed. **Account Owners** get every
current member; everyone else gets only themselves — non-Owners may only
self-assign.

**Usage**

```bash theme={null}
landbase-cli account users
```

Prints `{ data: [...] }` — one entry per assignable user:

```json theme={null}
{
  "data": [
    {
      "identityId": "idn_01H...",
      "firstName": "Sarah",
      "lastName": "Chen",
      "email": "sarah@acme.com",
      "roleId": 2,
      "roleName": "Member",
      "hasActiveInboxes": true,
      "hasConnectedLinkedin": false
    }
  ]
}
```

`identityId` is the value [`email-campaigns`](https://www.landbase.com/docs/reference/email-campaigns),
[`linkedin-campaigns`](https://www.landbase.com/docs/reference/linkedin-campaigns), and
[`dialer-sessions`](https://www.landbase.com/docs/reference/dialer-sessions) take as `assignedUserId` on
`create`. Email and LinkedIn campaigns also accept it through `--user` on
`assign`. The two boolean flags mirror what campaign launch requires of the
assigned user, per channel:

| Field | Description |
| - | - |
| `hasActiveInboxes` | The user has at least one active sending inbox — required to launch an **email** campaign assigned to them |
| `hasConnectedLinkedin` | The user has a connected LinkedIn account — required to launch a **LinkedIn** campaign assigned to them |

> [!TIP]
>
> Before assigning a campaign, pick a user whose flag for the campaign's
> channel is `true` — assignability is validated at create/assign **and**
> re-checked at launch. `account users` does not expose a dialer-readiness flag;
> dialer access is validated when `dialer-sessions create` runs.

***

## account set

Set the active account and persist it to `~/.landbase/platform.json`. Run it
with no arguments — the CLI lists the accounts you can access and prompts you to
pick one. Your choice is saved, so you only do this once per machine.

**Usage**

```bash theme={null}
landbase-cli account set
```

```text theme={null}
Multiple accounts available — pick one:
  [1] Acme Corp (39)
  [2] Beta LLC (449)
  [3] Globex Inc (722)
  [4] Initech (962)
Enter 1-4:
```

To target a different account for a single command without changing the saved
one, use the `--account=<id>` flag instead (see below).

***

**Flags**

| Flag | Default | Description |
| - | - | - |
| `--account=<id>` | — | Override the active account for a single command, without persisting it |
| `--verbose` | — | Print request/response details to stderr |

**Examples**

```bash theme={null}
# Print the active account (no network call)
landbase-cli account

# List accessible accounts
landbase-cli account list

# List the users you can assign campaigns or dialer sessions to
landbase-cli account users

# Switch account via the interactive picker
landbase-cli account set

# Use a different account for one command only (no persistence)
landbase-cli onboarding get --account=4821
```

## Related

* [How to select and onboard an account](https://www.landbase.com/docs/guides/how-to/select-and-onboard-account.md)
* [onboarding command reference](https://www.landbase.com/docs/reference/onboarding.md)
* [contacts-import command reference](https://www.landbase.com/docs/reference/contacts-import.md)
* [email-campaigns command reference](https://www.landbase.com/docs/reference/email-campaigns.md)
* [linkedin-campaigns command reference](https://www.landbase.com/docs/reference/linkedin-campaigns.md)
* [Output schemas](https://www.landbase.com/docs/reference/output-schemas.md#account)
* [Platform mode vs. legacy mode](https://www.landbase.com/docs/overview/concepts/platform-vs-legacy.md)


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