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
Shifts I sign up for would ideally show up on my general, everyday calendar of choice. This could be accomplished by allowing me to export my shifts as an iCal, then import them into my preferred calendaring app. It could also be accomplished to some degree by directly integrating with popular online calendaring apps (read: Google's calendar), allowing for potential "live" updates if shifts are dropped or cancelled.
The text was updated successfully, but these errors were encountered:
One thing I'd really like to see for this feature is some form of basic authentication. Unlike the event schedule, the staffer schedule involves personal information -- specifically, where a person can be expected to be at a certain time. Although our staff system is... frankly kind of a mess on protecting this information currently (you only need someone's name, zipcode, and email to log in as them), we should at least try to develop new features keeping this in mind.
In order to keep the schedule streamable, the authentication could/should probably be just an automatically-generated short code tied to the attendee. That way we can give them a link that includes said code. Dunno what the best way to generate the code is, I guess some form of short random string that we save to the DB? It doesn't exactly need to be human-readable or anything.
Shifts I sign up for would ideally show up on my general, everyday calendar of choice. This could be accomplished by allowing me to export my shifts as an iCal, then import them into my preferred calendaring app. It could also be accomplished to some degree by directly integrating with popular online calendaring apps (read: Google's calendar), allowing for potential "live" updates if shifts are dropped or cancelled.
The text was updated successfully, but these errors were encountered: