Currently, logged-in users cannot see the full history of their own submitted work requests if those requests are tied to locations outside of their permission scope. To access a complete history, they must open an incognito browser session and search as if they were not logged in. This creates unnecessary friction and breaks user expectations for how personal request history should work.
Current Limitations
- Incomplete History: Logged-in users only see requests submitted under locations they have access to, even if they are the original submitter.
- Workaround Required: To view all their requests, users must switch to incognito mode and search using their email address.
- Permission Overlap: The system applies location-based filtering even when displaying a user’s own submissions, which feels restrictive and confusing.
General Example
- A technician submits work requests across multiple facilities. When they log in, they only see requests tied to their assigned locations. To find their other requests, they must use incognito mode, essentially bypassing the login system.
Requested Enhancements
- Global “My Requests” View
Allow logged-in users to see a complete list of all the work requests they personally submitted, across all locations. - Smart Permission Override
Enable visibility into self-submitted requests regardless of location access, while still respecting location-based permissions for requests submitted by others. - Flexible Filters
Add a toggle or filter on the history page to switch between “All My Requests” and “Location-Based Requests.”
Business Value
- Transparency: Users gain confidence that all of their submissions are tracked and visible.
- Efficiency: Eliminates the need for time-consuming workarounds like using incognito mode.
- User Satisfaction: Aligns with modern system expectations where users always have visibility into their own activity.
- Consistency: Ensures a clear, predictable user experience when navigating request history.
👉 This complements your “Improve Work Request History Usability for Requesters” post:
- That one focuses on usability/navigation (login steps, pagination, one-way navigation).
- This one focuses on data visibility (seeing all self-submitted requests regardless of location).
