onboarding,
contacts-import, and
dialer-sessions.
account is a platform-mode command (platform mode is the default). Run
landbase-cli auth login first — account list,
account users, and account set call the platform. See
platform mode vs. legacy mode.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{ accountId, source }, where source is "config" when an account is
set or "none" when it isn’t. See output schemas.
account list
List every account the current user can access, marking which one is active. Usage{ accounts: [{ id, name, role, current }] }. current reflects the
account the CLI would use right now. See
output schemas.
account users
List the users of the active account you can assign campaigns or dialer sessions to. Unlikeaccount 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
{ data: [...] } — one entry per assignable user:
identityId is the value email-campaigns,
linkedin-campaigns, and
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:
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
--account=<id> flag instead (see below).
Flags
Examples

