Shared store devices make access control visible only when staffing changes expose it.
Strong revocation and uninterrupted checkout can conflict at the edge of connectivity and device timekeeping.
Who you’d be doing this for
“When someone leaves, I need them out straight away—but service can’t stop.”
Brigitte Roberts · Restaurant Owner
Runs a restaurant with rotating shifts, shared terminals, and frequent temporary staffing changes.
What is at stake
Tokens stay valid long after an employee is dropped from the roster, and a review tied several delayed removals to live sessions. You weigh strict expiry against blocking a legitimate checkout.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- rapid revocation vs. uninterrupted checkout
- strict security control vs. unreliable device clocks
- committed migration vs. incomplete validation
- central identity policy vs. terminal edge conditions
Why SumUp
For SumUp, this can shape how safely merchants manage staff access without disrupting daily trade.
Written with these in mind
Not your kind of problem? 9 more at SumUp, 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.