Secrets Guide
Secrets is a secure vault for storing credentials, API keys, and certificates.
Security Model
Nocarta uses two-tier encryption:
Tier 1 (Server-Protected)
- Encrypted at rest on the server
- Server decrypts and delivers to desktop app during automation
- Best for: Credentials used in automations (API keys, service accounts, automation logins)
Tier 2 (Client-Protected)
- Encrypted with your master password
- Server cannot decrypt - only your device can
- Requires master password to view or use
- Best for: Personal sensitive credentials that should never leave your control (banking, admin passwords, personal accounts)
Setting Up Your Vault
First-Time Setup
- Navigate to
/vault/setup - Create a master password (for Tier 2 secrets)
- Save your recovery key - this is the only way to recover if you forget your master password
- Your vault is ready
Unlocking
- Navigate to
/secretsor/vault/unlock - Enter your master password
- Vault remains unlocked for your session
Managing Secrets
Creating a Secret
- Click Add Secret
- Choose the type:
- API Key: For service integrations
- Password: Login credentials
- Keypair: SSH keys, signing keys
- Certificate: SSL/TLS certificates
- Database Credentials: Connection strings
- Generic: Any other sensitive data
- Set protection level (Tier 1 or Tier 2)
- Enter the secret value
- Optionally set expiration date and tags
- Save
Viewing a Secret
- Navigate to the secret
- Click Reveal (requires unlock for Tier 2)
- Value is displayed temporarily
- Click Copy to copy to clipboard
Version History
- Every change creates a new version
- View history: Secret → Versions tab
- Restore previous version if needed
Using Secrets in Automations
Secrets can be injected into automation steps:
- Open an automation
- Go to Bound Secrets tab
- Click Bind Secret
- Select the secret and the placeholder name
- In automation steps, use
{{placeholder_name}}syntax - At runtime, the desktop app replaces placeholders with actual values
Security Note: Secret injection happens on your desktop, never on the server. This ensures your credentials are handled securely during automation.
Import & Export
Importing Secrets
You can import secrets from other password managers or CSV files.
- Go to Secrets
- Click Import
- Select your source format
- Upload your export file
- Review and confirm
Supported Import Formats
| Format | Name Column | Password Column | Other Fields |
|---|---|---|---|
| 1Password | title |
password |
username, url, notes, tags |
| LastPass | name |
password |
username, url, extra, grouping |
| Bitwarden | name |
login_password |
login_username, login_uri, notes, folder |
| Chrome | name |
password |
username, url |
| Firefox | url |
password |
username |
| Generic CSV | name |
password, value, or secret |
multiple fallbacks supported |
Note: All imported secrets are created as Tier 1 (server-encrypted). You can upgrade individual secrets to Tier 2 after import if needed.
Exporting Secrets
- Go to Secrets
- Click Export
- Authenticate with your master password
- Choose format (CSV, JSON, or ZIP with files)
- Download your backup
Security: Export files contain sensitive data. Store them securely and delete after use.
Best Practices
- Use Tier 2 for anything you wouldn't want exposed if the server were compromised
- Set expiration dates for rotating credentials
- Use tags to organize (e.g., "production", "staging", "personal")
- Review access logs periodically
Need More Help?