Settings and activity
12 results found
-
9 votes
This workflow today can be completed from Request and Decision.
-sammie
Lauren Petrusky (Longwood Foundation)
supported this idea
·
-
26 votesLauren Petrusky (Longwood Foundation)
supported this idea
·
-
39 votes
Thank you for the idea.
Would you hope this is implemented across all processes?
Lauren Petrusky (Longwood Foundation)
supported this idea
·
An error occurred while saving the comment -
18 votesLauren Petrusky (Longwood Foundation)
supported this idea
·
-
4 votesLauren Petrusky (Longwood Foundation)
shared this idea
·
-
6 votes
Hello,
This can be added to the user form today. One piece we have heard is that this should be more visible in other areas of the software, if you could please call out where you would expect to see this information
An error occurred while saving the comment Lauren Petrusky (Longwood Foundation)
commented
I would think it would best be included with the user's contact info -- perhaps next to their preferred prefix. (Example: We had a recent attendee at an event ask to go by they/them but they wanted their prefix to be Mr.) It can be so confusing, so having the user provide this information would be helpful.) Make sense?
Lauren Petrusky (Longwood Foundation)
shared this idea
·
-
9 votesLauren Petrusky (Longwood Foundation)
shared this idea
·
-
5 votes
An error occurred while saving the comment Lauren Petrusky (Longwood Foundation)
commented
We do not use Access Codes either and we get questions all the time. It would be nice to allow clients to alter the language there so that we could say something like "UNLESS YOU HAVE BEEN TOLD OTHERWISE, NO ACCESS CODE NEEDED TO APPLY. GO DIRECTLY TO THE "APPLY" BUTTON" ... or something along those lines. Or, even better, the ability to turn the Access Code question on or off to make it not visible at all. That would be great and alleviate all t he calls/emails we get each application cycle.
Lauren Petrusky (Longwood Foundation)
supported this idea
·
-
91 votesLauren Petrusky (Longwood Foundation)
supported this idea
·
-
71 votesLauren Petrusky (Longwood Foundation)
supported this idea
·
-
24 votesLauren Petrusky (Longwood Foundation)
shared this idea
·
-
22 votesLauren Petrusky (Longwood Foundation)
supported this idea
·
Interesting idea and I could see the value in it. However, because we share a platform with two other foundations, I would not want this to be a sitewide change because they run their operations very differently than we do and it could cause them issues.