Skip to main content
The CLI stores credentials as named profiles — each holds either an OAuth session or an API key, so you can switch between teams or workspaces without re-entering credentials. This page is the reference for managing those profiles and the teams they act on. For first-time sign-in, see Sign in.

Profiles

Use a different profile for a single command

--profile <name> works on every command and doesn’t change your default.

Sign out

duvo logout revokes the OAuth tokens server-side and removes the profile locally.

Environment variables

For non-interactive use (CI, scripts), the CLI also reads:

Teams

A profile’s credentials are scoped to a team. Use these commands to confirm which team you’re acting on and inspect its members before running commands that change data.
If --team is omitted, member listing uses the team scoped to your API key or active profile. Add --json to any command for machine-readable output.

Confirm your team before a destructive command

Running this first is a cheap way to make sure a bulk delete or delegate lands on the team you intend.

Duvo CLI

installation and first sign-in

Scripting and CI/CD Patterns

authenticating with API keys in pipelines