The incident drill needs restricted access, while the identity change is already live.
Platform engineers need a repeatable group mapping, and the drill cannot proceed on unverified permissions.
Who you’d be doing this for
“I spent this morning checking who landed in the default workflow instead of running the drill.”
Juma Maina · Platform Engineering Manager
Owns the healthcare software customer’s developer access patterns and incident drill readiness.
What is at stake
Thirty-seven developers are entering the default workflow instead of the restricted one. You have to weigh a fast mapping change against proving the audit trail is correct.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- drill readiness vs. access verification
- fast restoration vs. reusable mapping
- default workflow continuity vs. restricted policy enforcement
Why Cursor
Cursor workflows depend on enterprise roles and policies remaining intact when customer identity groups change.
Written with these in mind
Not your kind of problem? 42 more at Cursor, 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.