27 votesPhil Dailey commented
We have a similar issue in that our constitution requires that membership IDs are generated after a new membership application has been accepted by at least two of the board members. Therefore the system member id cannot be used since it will be generated at the initial application for membership.
We are new clients of Wild Apricot and were expecting to totally convert our current MS Access database to Wild Apricot to improve the flexibility of our membership management. Due to this issue we are being forced into maintaining the MS Access database just to comply with our membership ID rules.
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.Phil Dailey commented
For any organisation that applies an acceptance approval process a 2-phased application process is a must.
This should be tied in with the membership Id, which should not be generated until membership has been approved and payment received (i.e. phase 2).
Taking a membership payment and then rejecting the application does not help the image of the organisation.