You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when a user goes to the incidents list (e.g. for 2024), and if they don't have read or write access to the event, they'll just get a page like this:
I first-handedly saw multiple instances this year of Rangers not knowing how to proceed when they got this error. There were two categories of problem that came up, and I'd suggest we enhance the messaging to cover both of these:
The Ranger shouldn't have access to incidents, and really they just need to create an incident report. The page could educate them about incidents vs. incident reports.
The Ranger should have access to incidents, but they don't have it. For example, this came up mid-event this year, when one of my fellow Green Dot Leads (GDLs) was unable to view/edit Sanctuary-related incidents, and she was totally confused about what was wrong. Having decent experience with IMS myself, I recognized the problem and escalated a request for incident access for GDLs. Anyway, the "permission denied" message was vague and unhelpful for my colleague.
srabraham
changed the title
[FEATURE] Enhance messaging on the "permission denied" page for incidents
[ENHANCEMENT] Enhance messaging on the "permission denied" page for incidents
Oct 8, 2024
srabraham
changed the title
[ENHANCEMENT] Enhance messaging on the "permission denied" page for incidents
Enhance messaging on the "permission denied" page for incidents
Oct 22, 2024
Currently when a user goes to the incidents list (e.g. for 2024), and if they don't have read or write access to the event, they'll just get a page like this:
I first-handedly saw multiple instances this year of Rangers not knowing how to proceed when they got this error. There were two categories of problem that came up, and I'd suggest we enhance the messaging to cover both of these:
I'm interested in tech team feedback on this (such as @wsanchez @chaoticbear)
The text was updated successfully, but these errors were encountered: