Paula Grunthaner
My feedback
7 results found
-
15 votesPaula Grunthaner
shared this idea
·
-
29 votes
An error occurred while saving the comment Paula Grunthaner
supported this idea
·
An error occurred while saving the comment Paula Grunthaner
commented
Lack of a signature function for the Rules and Terms field type is a significant problem for our organization as well. Our legal advisor tells us that we are at risk with our hold harmless statement in our terms field because a bundle admin clicking the acceptance box on this field when he creates a bundle member does not legally mean the bundle member has accepted this statement. We need a legally acceptable signature for this. We had this in our online application (FormStack, if memory serves me) before we switched to WA, but had to abandon this when we moved to WA.
-
56 votes
An error occurred while saving the comment Paula Grunthaner
commented
I fully support this recommendation. We are in the process of switching from individual to bundled memberships and I cannot believe how awkward the membership application process has become. It is not only difficult for the new bundle admin to remember (or care) to return to add their co-member, but it also tedious for the membership admin to manually add a membership bundle and then go add a contact to add to the bundle (usually the admin has to go back and search for the recently created membership bundle). Perhaps when the admin selects the "add member" button on the bundled membership, WA could direct them to a linked profile to complete instead of directing them to a pop-up to select a contact.
Paula Grunthaner
supported this idea
·
-
82 votes
An error occurred while saving the comment Paula Grunthaner
commented
Given our member demographics, we have 100's of members who do not use computers and we must provide them with a printed directory. Knowing that WA does not support an export of its online directory, we created custom fields (example: Include phone in printed directory: Yes/No) for all our membership privacy preferences. This way we can export data from members>list>export and then manipulate the Excel spreadsheet to delete data that members do not want in a directory. Then we use Word to mail merge the modified data into our preferred format for our printed directory. This is an extremely tedious approach, but it works. The major downside is that we cannot also have an online directory (!) because members become confused by having both custom-field privacy options and, of course, the system privacy settings. So, sadly, we have no online directory for our members. This situation is quite unacceptable for a member management software system.
Please, Wild Apricot, as a minimum, provide an Excel export of member data that takes into consideration how a member has set their system online privacy. This means if a member marks in their system privacy settings that their phone number is not to be shown, then it is not included in the export. Then we can have our online directory AND we can produce a printable directory using the privacy-compliant Excel export. And we can delete our custom privacy fields!
Paula Grunthaner
supported this idea
·
-
73 votesPaula Grunthaner
supported this idea
·
-
25 votesPaula Grunthaner
supported this idea
·
-
73 votesPaula Grunthaner
supported this idea
·
Let me add to my previous comment. Our legal advisor says that our hold harmless statement in our terms field would be acceptable if there was a way to ensure that only the new bundle member could check the "I accept" box. Right now, WA allows the bundle admin to fill in all the info for the bundle member, including accepting the term field. Therein lies our problem. This legal problem could be solved if WA could come up with a way to limit the acceptance of the term field to the member himself. We surely cannot be the only organization with a hold harmless statement that every member must accept. WA should really want to fix this and gain a major advantage over other membership management services. We will jump to another service the moment we see this feature in order to avoid liability risk!