Skip to main content

Overview

User commands manage user accounts and their API keys. Users can be members of multiple projects, with separate API keys for each project.

User Management

List Users

List all users in the system.

Create User

Create a new user with email address.
string
required
Valid email address (must be unique)
Email validation ensures proper format: user@domain.com

Get User

Retrieve detailed information about a user.
string
User email address
string
User UUID

Update User

Update user’s email address.
string
required
Current email address or user ID
string
required
New email address (must be unique)

Delete User

Delete a user from the system.
string
required
User email or ID
flag
Force deletion and remove all API keys and project memberships
Standard delete fails if user has active API keys. Use --force to delete everything, or manually delete API keys first.

User Relationships

List User Projects

List all projects a user belongs to.

API Key Management

Generate API Key

Create a new API key for a user in a specific project.
string
required
User email or ID
string
required
Project name or ID
API keys are 48-character URL-safe base64 strings. Store them securely.

List API Keys

List API keys for a user.

List All API Keys

List all API keys across all users (admin operation).

Get API Key Details

Retrieve details about a specific API key.

Rotate API Key

Generate a new API key and invalidate the old one.
Update all applications using the old key immediately after rotation.

Disable API Key

Temporarily disable an API key without deleting it.
Disabled keys cannot authenticate but remain in the system for audit purposes.

Enable API Key

Re-enable a previously disabled API key.

Delete API Key

Permanently delete a specific API key.

Delete All API Keys

Delete all API keys for a user.
This will invalidate all active sessions for the user across all projects.

Search Users

Search for users by email or project membership.
string
required
Search term to match against emails and project names

Best Practices

  • Never commit keys: Don’t include API keys in version control
  • Use environment variables: Store keys in environment variables
  • Rotate regularly: Rotate keys every 90 days
  • Principle of least privilege: Generate separate keys per project
  • Monitor usage: Track API key usage patterns
  • Quick revocation: Be prepared to rotate/disable compromised keys
  • Corporate email: Use company email addresses
  • Regular audits: Review user list periodically
  • Prompt offboarding: Remove access when users leave
  • Document ownership: Maintain records of user responsibilities
  • Project-based access: Use projects to control access scope
  • Minimal permissions: Only grant necessary project memberships
  • Temporary access: Use disable/enable for temporary access needs
  • Audit trails: Track API key creation and deletion

Common Workflows

New User Onboarding

Rotate All Keys for a User

Emergency Key Revocation

User Offboarding

Audit User Access

Troubleshooting

Error: “User has X active API keys”Solution:
Error: “User with email already exists”Solution: Use a different email or retrieve the existing user.
Error: “User not found in project”Solution:
Possible causes:
  • Key was disabled or deleted
  • Key not set in environment variable
  • Wrong project configuration
Solution: