JIT access from a chat workflow
How I turned privileged access into a scoped, approved, expiring workflow that other systems could integrate with.
What I found
Broad production write access was the default for most of the engineering organization, across AWS and Kubernetes. Removing it without a usable replacement would push engineers back toward exceptions.
The operating model
Read-only access became the birthright. Write access became persona-scoped, just in time, human approved, and automatically expired. The workflow lived inside the chat tool engineers already had open, instead of adding another security portal.
What I built
I designed a common request and approval layer, with system-specific enforcement behind a reusable integration model. It centralized policy, approval, grant issuance, expiry, and evidence while allowing each target system to enforce access correctly.
What changed
The service delivered one JIT operating model across every privileged system in scope, from cloud infrastructure to secrets and databases. Engineers could request scoped access when needed, grants expired automatically, and later integrations did not have to rebuild policy and user experience from scratch.
What stayed difficult
Policy quality, approval context, and target-system enforcement still required careful ownership. The reusable model made those boundaries explicit without pretending every system worked the same way.