What is AgentSecrets?
The Zero-Knowledge Difference
How AgentSecrets Works
Installation
Quick Start
Migrating from .env Files
Migrating from Vault / AWS
Migrating from dotenv-vault
Production Checklist
Credential Exposure
What Zero-Knowledge Means
The Proxy Model
The Three-Layer Model
Environments
Agent Identity
Storage Modes
The No get() Principle
Secret-Level Policies
Cloud Overview & Architecture
The Dual-Engine Model
Cloud Resolver Data Plane
Workload & Agent Tokens
Egress Allowlists & Audit Streams
Cloud REST API Reference
Account (init / login)
Server & Self-Hosting (server)
Docs
Shell Autocompletion
Keychain Auth
Secrets
Environments
Credential Proxy
env Injection
Workspaces & Teams
Projects
Agent Identity
Audit & Governance
Integrations Overview
Claude Desktop
Cursor
OpenClaw
HTTP Proxy (Any)
LangChain (Soon)
CrewAI (Soon)
CI/CD Pipeline
SDK Overview
Python SDK
Python API Reference
Python SDK Manual Testing
JavaScript SDK (Soon)
Ecosystem Overview
Zero-Knowledge MCP Server
Server Overview
5-Layer Architecture
Self-Hosting Guide
Authentication & Keys
Workspaces & Teams
Projects & Scope
Environments
Secrets & Sync Protocol
Agent Identity Resolution
Telemetry & Metrics Engine
Audit Log Sync
API Endpoint Reference
Security Overview
Anti-Impersonation & Process Verification
Encryption Model
Zero-Knowledge Sync
Proxy Security Layers
Threat Model
OWASP Top 10 Mitigation
Security FAQ
Third-Party Audit
Reporting Vulnerabilities
Guides Overview
Building on the SDK
Stripe Integration
OpenAI Integration
Multi-Agent Setup
Onboarding Team
CI/CD Pipeline
Publishing ZK MCP
Rotating Credentials
Auditing Team Activity
Dev to Production
Kubernetes Deployment
Monorepo Setup
Production Proxy Hardening
vs .env Files
vs HashiCorp Vault
vs AWS Secrets Manager
vs dotenv-vault
vs Infisical
When Not to Use
Proxy Not Starting
Proxy Not Resolving
Domain Blocked
Sync Conflicts
MCP Not Connecting
Session Token Errors
Proxy Session Authorization
Keychain Storage & Backends
SSRF & Destination Rules
Installation Issues
Error Codes Reference
Frequently Asked Questions
v3.1.x
v3.0.0
v2.1.0
v2.0.0
v1.4.0
v1.3.x
v1.2.0
v1.1.x
v1.0.x
CLI ReferenceInviting Team Members

Inviting Team Members

Collaboration in AgentSecrets relies on a zero-knowledge, end-to-end encrypted invite system. Inviting team members grants them access to a shared workspace, allowing them to pull secrets directly to their local OS keychains and run agents using the shared credentials.


Sending an invite

Only administrators (Admin) or the workspace owner can invite new members to a shared workspace.

  1. Initiate the invite: Run the agentsecrets workspace invite command with the collaborator's email address:

    agentsecrets workspace invite developer@acme.com

    To invite multiple members at once, separate their emails with spaces:

    agentsecrets workspace invite alice@acme.com bob@acme.com
  2. Verify pending invites: To see the list of invited members and their status, view the members of the current workspace:

    agentsecrets workspace members

    Output:

    alice@acme.com (member) pending bob@acme.com (admin) pending

Accessing the Workspace

Inviting a team member adds them to the workspace immediately. Under the hood, the admin's client encrypts the workspace key using the invitee's public key and registers them with the workspace, which is why the invite is gated behind administrative privileges and password confirmation.

  1. Log in or register: The invitee installs the CLI and logs in using their credentials:

    agentsecrets login

    The client-side end-to-end encryption engine automatically detects their workspace access, performs the secure key exchange, and decrypts their workspace key. No separate accept command is needed.

  2. Verify access and switch: They can now list and switch to the new workspace:

    agentsecrets workspace list agentsecrets workspace switch "Acme Engineering"

During the acceptance process, the backend coordinates a key exchange. The workspace's shared key is encrypted with the invitee's public key. This allows the invitee to decrypt the workspace key locally without the AgentSecrets servers ever having access to the raw workspace key or secrets.


Invite expiry and resending

By default, workspace invites expire after 7 days for security. If an invite expires or needs to be revoked before acceptance, admins can manage them via the CLI.

  1. Cancel a pending invite: If you need to revoke an outstanding invitation or remove access, run:

    agentsecrets workspace remove developer@acme.com
  2. Resend an invite: To resend an expired or lost invitation, simply issue the invite command again. The system will generate a fresh invite with a new 7-day expiry:

    agentsecrets workspace invite developer@acme.com
Was this helpful?
Thanks for your feedback!
Your feedback helps us improve the platform.