Emergency access is failing exactly where standing permissions are meant to stay narrow.
Incident response needs a fast path into production, while least privilege requires that path to expire and remain auditable.
Who you’d be doing this for
“The alert was firing, and I spent eight minutes proving I was allowed to look at it.”
Yannis Marchetti · On-call Backend Engineer
Operates a production service used to deliver updates to members’ active sessions.
What is at stake
Approved incident responders are being blocked from production even though their Access roles still exist. You have to weigh rapid recovery against the narrow, auditable permissions that protect production.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fast incident access vs narrow production permissions
- self-service recovery vs approval control
- policy correction vs separate emergency route
- operational speed vs audit completeness
Why Discord
Discord’s real-time communication systems depend on responders reaching production services without leaving broad access behind.
Written with these in mind
Not your kind of problem? 16 more at Discord, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.