Change Requests
We’ve heard from a lot of you about the struggle to keep secrets and configs in check, and we totally get it! Before Change Requests, teams had two big challenges:
- Not the Right Access: Developers either had too much access, leading to permission sprawl and security risks, or too little, forcing them to create Jira tickets just to update a secret they couldn’t reach.
- No Clear Review Process: Unlike code, secrets often go live without a thorough review, leading to potential mistakes or vulnerabilities.
That’s why we built Change Requests - to give secrets the same thoughtful review process as code. Now you can:
- Keep Access Tight: Developers can propose changes without needing direct access, preventing permissions from getting out of control.
- Ensure Proper Reviews: Changes to secrets go through a review and approval process, helping catch issues before they impact your environment.
- Track Everything: Every change is logged, giving you full visibility and accountability, which is a huge win for compliance!
How it Works:
- Propose Changes: Anyone with a Viewer role can suggest updates or changes to secrets.
- Review & Approve: A teammate with approval permissions reviews the changes. If all looks good, they hit “approve.”
- Apply the Changes: Once approved, the changes can be applied by the approver or author - triggering any webhooks or syncs you’ve set up.
Change Requests are live today for all workplaces on our Enterprise plan. Head over to our docs to learn more!
