A venue view shaped by responsibility.
Show users the operational information relevant to their role.
Where this work fits
An operator might need to pause several players or change a venue’s volume. Some devices could be connected while another was unavailable. A dashboard needed to make that situation understandable.
I worked on authentication and role-aware access to venue resources. Establishing who someone is and deciding which locations or devices they may access are related but different responsibilities.
Match an action with the right permission
Venue opening hours
Monday — Friday · 09:00–18:00
A viewer can inspect the record. Editing requires a different permission.
A group command can have mixed results.
One unavailable device should not erase successful sends to the others. I returned per-operation delivery results and worked on aging connection state so a disconnected player would not look active indefinitely. A sent command still needed to be distinguished from observed playback.
The skills behind the work
- Authentication
- Establish who is making a request before applying account or access rules.
- Access control
- Check which actions and resources an authenticated account is allowed to use.
- SQL
- Query and update relational data, with clear rules about which records a result represents.
Operators could control players remotely and see more useful information about their availability. The backend supported venue-level actions without treating the entire fleet as one device.