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
I am currently able to view all first aid reports for upcoming games on the event calendar. Is this due to my "first aider" tag on my account, or is it possible for everyone to view the first aid reports?
If this is due to my having the first aider tag, please feel free to remove the tag at your convenience - my qualification has expired and I do not have a date for recertification yet.
If it is visible to everyone, I had thought that there were restrictions on who could view the first aid reports due to personal information being visible on them (so I shred printed reports the day after the game). Has this changed?
Thank you in advance,
Doug
The text was updated successfully, but these errors were encountered:
As we don't track who's the first-aider on any particular game, there's currently no restriction on first-aiders viewing the first-aid reports for a game. I think this is probably something that we'll want to address in future, probably by time-boxing first-aiders' access to the report to the day of the game.
I've removed your first-aider tag, and I'll ask the committee to review who's currently got them.
I am currently able to view all first aid reports for upcoming games on the event calendar. Is this due to my "first aider" tag on my account, or is it possible for everyone to view the first aid reports?
If this is due to my having the first aider tag, please feel free to remove the tag at your convenience - my qualification has expired and I do not have a date for recertification yet.
If it is visible to everyone, I had thought that there were restrictions on who could view the first aid reports due to personal information being visible on them (so I shred printed reports the day after the game). Has this changed?
Thank you in advance,
Doug
The text was updated successfully, but these errors were encountered: