Using Secrets Managers in Unified

Unified's platform allows users to securely manage connection and workspace integration credentials using external secrets managers, providing control over where sensitive API credentials are stored while still enabling Unified to access and refresh these credentials as needed for API calls. Users can create multiple secrets managers and choose defaults for new credentials, specific environments, or authorized connections, with support for AWS Secrets Manager, Azure Key Vault, Google Cloud Secrets Manager, HashiCorp Vault, and Composio. This setup enables the isolation of different environments, such as storing production and sandbox credentials separately, and allows different teams to manage environment-specific secrets. Unified ensures credentials remain usable during transitions between secrets managers and provides a fallback system that defaults to workspace storage if no specific secrets manager is configured. Users are advised to configure secrets managers according to their security needs, such as using one default manager for simplicity or multiple environment-specific managers for stringent separation requirements. Unified also supports scenarios where secrets managers are not used, as credentials can be stored encrypted within Unified's database.