#Team
| Command | Purpose |
|---|---|
vatio team [list] [--json] | The owner and everyone invited, and who has not signed in yet |
vatio team questions [--to EMAIL...|--none] [--template NAME [--language CODE]|--no-template] | Who the agent asks when it cannot answer a customer, and the template that opens the conversation. See Ask a supervisor |
vatio team invite EMAIL --role viewer|supervisor|developer [--code CODE] | Invite them, and email them. --code is your authenticator app's code. Needs two-step verification on your account |
The same invitation as Team in the inbox, with the same three roles (see
Teams for what each can do), and the same rule: only the workspace's
owner can do it. For anyone else the answer is 403 owner_only. There is
nothing to accept: the person signs in with the email you gave.
--role is required, because there is no safe default. Inviting someone who
already has access answers 422 already_member; the owner answers
422 already_owner.
Removing someone, changing a role and narrowing a member to some agents stay in the inbox.
Confirming it is you. The inbox asks the owner to confirm before inviting,
and a token left on a laptop has no such step, so invite needs a fresh code
from your second factor: --code with your
authenticator app's 6-digit code, or --recovery-code. From a terminal, the CLI
asks for the code if you leave it out; a coding agent has no terminal, so it
asks you for the code and runs the command with it. Without --code the answer
is 403 reauthentication_required, and a wrong one is 401
invalid_confirmation. A passkey cannot be answered from a terminal: with only
a passkey (and no authenticator app or recovery code), invite from the inbox.
An account with no second factor can't invite from the CLI (403
reauthentication_required): invite from the inbox, which confirms by email,
or turn on two-step verification first.
vatio team invite ana@example.com --role supervisor --code 123456vatio team --json