Skip to main content
A team member is an agent or another user of the workspace. For fields and response details, see the API reference.

List team members

This command lists the workspace’s active team members. Use this when you want to see who already has access. --email matches an address exactly.
Sample output (--json)

Show a team member

This command shows one team member’s email address, name, time zone, and role. Use this when you want to inspect a member after finding their ID from team-members list. The record has the same fields as a team-members list entry and sits under a team_member key in data.
Required arguments:
  • <id> - Team member UUID

Add team members

This command invites one or more people to the workspace. Use this when you want to give someone access. Repeat --email to invite several at once. Each address is emailed an invitation unless you pass --send-invitation-email=false.
--role must name a role that exists under Roles in your workspace settings.
The API confirms the invitations with a message rather than returning the new members, so this is the one create command whose --quiet output is that message object rather than an id. Run team-members list --email afterwards to fetch a new member’s id.
Sample output (--json)

Update a team member

This command changes a team member’s email address, name, time zone, or role. Use this when a member’s details or role change. Pass only the flags you want to change. The updated record comes back under a team_member key in data.
Required arguments:
  • <id> - Team member UUID
Sample output (--json)

Delete a team member

This command deactivates a team member, ending their access to the workspace. Use this when someone should no longer have access. Their user record is kept, so the tickets and comments they handled stay attributed to them. The last admin of a workspace cannot be removed.
Required arguments:
  • <id> - Team member UUID
Sample output
Under --json that is {"message": "Team member removed."}; under --quiet it is success.