june
My feedback
56 results found
-
19 votesjune
supported this idea
·
-
42 votesjune
supported this idea
·
-
163 votesjune
supported this idea
·
-
81 votesjune
supported this idea
·
-
103 votesjune
supported this idea
·
-
53 votesjune
supported this idea
·
-
98 votesjune
supported this idea
·
-
9 votesjune
supported this idea
·
-
27 votesjune
supported this idea
·
-
133 votesjune
supported this idea
·
-
44 votesjune
supported this idea
·
-
7 votes
Team Mobile
responded
Everyone who can log into website also can log into mobile app.
Member app shows profile details in the same way as web version, with respect to field visibility settings and level of current user permissions.Wild apricot allows to restrict field visibility to the following:
– show to anybody
– show to members only
– don’t show to othersCurrently neither web version nor mobile app could restrict fields visibility to specific level.
june
supported this idea
·
An error occurred while saving the comment -
255 votesjune
supported this idea
·
-
366 votes
We're considering to take Donations during registrations/applications into development right now, but during analysis of the feature we ran into an issue where we would love to hear your feedback.
Essense of question: how would you like donations during applications or registration to be processed for offline payments (when your member/prospect decided to get an invoice and pay later)?
Some more details:
We can implement donations during event registrations/membership renewals for online payments - not a problem.
But when we're talking about offline payments, straighforward solution seems to be a bit expensive - we don't have invoices for donations or pledges yet.
So right now we're considering going on with straighforward online payments solution (donation will be added to payment transaction) and for offline payments - just include an invoice memo to buyer to add $XXX to his payment as donation for event/membership he has selected.
This way administrators would…
june
supported this idea
·
-
314 votes
Evgeny Zaritovskiy
responded
Collecting comments now.
june
supported this idea
·
-
221 votesjune
supported this idea
·
I have a Business Member Level that I want to display all common fields and some custom member fields (restricted to their level) to everybody. Because the common fields are visible to anybody for the Business Members, I restrict the Individual Member Directory by website page. That part works fine. Horrified to realize an event registrant was able to see Individual Member Directory because of those common field settings.
Yes--I want to restrict what displays on the APP based on Membership level.
1. contact, not a member: can see Business Members
2. Business Members: can see themselves
3. Individual Members: can see themselves + Individual Members
I can restrict the membership directory on the app to only show Business Members, but that's not as useful to my Individual Members who will want to contact each other--but I can't use it without custom configuration.