I have also asked for conditional branching in Polling questions
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 others
Currently neither web version nor mobile app could restrict fields visibility to specific level.
30 votesEvgeny Zaritovskiy responded
For now, this is not something we’re going to change – not sure if ever.
Workaround to use: create a special “entry” free level to apply to, and close “normal” ones for application. For the entry level, create also a dropdown field where a potential member can choose a level they want to apply to. Add other fields you need to assess the application. When application is successful, your admin is to change membership level to required one and generate membership invoice (membership upgrade invoice). The member will be emailed with the invoice and can pay.
Sorry for the late update.
The first step was finished and emails can now be carbon copied to contact’s alternative emails. To do so the contact fields which store the alternative emails must be explicitly marked on the email setting page.
Unsubscribing will unsubscribe all alternative emails simultaneously because they all belong to the very same account. The person clicking “unsubscribe” is warned about this on the unsubscribe page.
For now we paused the development of this feature. but not for good. :) So I’m changing this wish status back to “collecting comments”.
Thank you everyone for a valuable feedback.
This is very important to our club. We currently have to work around it by maintaining separate contacts for the secondary emails, which is very time-consuming and error-prone. For us, this feature is certainly more important than rewriting the email editing process. Anything you can to to elevate the priority of this item would be greatly appreciated.
Chart of Accounts account name should be an entry in each registration type type for events as we keep revenue for each event separately in QuickBooks. Also, sub-accounts for Quickbooks should be supported for the QB Export function.
54 votesEvgeny Zaritovskiy responded
We’re collecting comments and votes for now, no actual development is planned so far
Agree that this needs to be part of a fully-functioning Accounts Receivable system, and WA needs to include such a system.
We would like to see this change, among others. We would like to have Wild Apricot be a sub-ledger of Quickbooks. To do that, it needs to be able to produce the normal range of Accounts Receivable reports and have good accounting controls. This would allows us to post only batch figures to QA, and not have to deal with the QB Export-Import process.