New Feature: Secrets Management in Clerk.io

What’s new

🔒 Bank‑level AES‑256 encryption at rest

⏱️ Secret expiration management

🧰 Full CRUD API (create, read, update, delete)

👥 Role‑based access control (RBAC)

• Client users see only their own secrets
• HQ staff have full cross-client access

Why it matters

• Reduce risk: Stop sharing credentials over email or tickets.
• Centralize control: Manage all sensitive tokens in one secure place.
• Speed up work: Rotate, expire, and update secrets without back‑and‑forth.

Perfect for

• API tokens and webhook keys
• Third‑party service credentials
• Any sensitive data that expires or needs rotation

We’d love your feedback

Your feedback fuels our roadmap. Drop us a note via in-app chat or at support@clerk.io.

Drive the journey from the very first click! — The Clerk.io Product Team