Our association has a parent company where all the membership dues go and then chapters for regional areas. The chapters do not collect the membership dues but advise members when their memberships are about to lapse.

Future: If you create a membership level that is zero cost to members and you enable renewals, you need to disable the renew button in member's profile so they do not renew through the current website. This way you can send the reminder emails that membership is going to expire and we can link the members to the correct location to make payment of their dues.

Currently cloning a Wild Apricot website requires intervention from WA support. While the service around cloning is usually pretty quick, it may be of benefit to administrators to be able to clone a website on your own without Wild Apricot support. This sort of functionality may be granted only to partners or to trusted customers, but in general cloning has the following benefits:

• cloning is useful when doing a redesign of a website. Cloning a site and applying theme ideas can be easily done without needing to modify the core platform




• creating a "template" website could be useful when creating multiple chapter sites from a template site.

A clone process should allow the following "parameters"
- administrative email of site
- the domain name of new site
- the organization details (address, time zone)
- particular billing parameters

The cloning process should allow certain pieces of the site to be cloned (and not others):

• the website pages/templates,


• the database configuration with levels and fields,


• events,


• online store configuration


• newsletter templates


• which specific accounts beyond 1 administrator


• administrative assignments


• colours/style parameter of the theme to be cloned


• an organization logo which could be assigned at the site level into the theme

The cloning process should NOT allow the introduction of new content in anyway.

It would be nice to "batch" this process to allow multiple clones to be generated at one time.

Some organizations need to manage separate chapters/groups within a single Wild Apricot account (and thus only one website).

Here's the current state of this functionality and links to related threads:

Each chapter can have its own website section and there can be web editors with permissions limited to a specific chapter section (existing functionality)

Members can be separated out into chapters through a use of Groups field or a custom field (existing functionality). One aspect that is currently missing is the ability to assign per-chapter membership managers. There is already a thread dedicated to this, see http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8825755-new-admin-role-membership-manager-limited-to-spe

Events can be separated out between chapters through the existing event tags functionality. There is currently no provision for chapter-specific event managers - all event managers would have access to all events. There is a request about adding event-specific organizers for each event (vs. current model of Wild Apricot account-wide event managers). See http://forums.wildapricot.com/forums/308920-archive/suggestions/8831335-event-specific-administrators-10260 I believe this might meet need of chapter event organizers - and would appreciate your comments and thoughts on that thread.

Finally, there is a financial aspect. Currently, all payments in a particular Wild Apricot account flow into the same merchant account defined in settings. It sounds like some groups want chapter finances (event payments, membership payments) to flow into per-chapter merchant accounts - which is not currently possible. Something along these lines has been requested - see http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8825845-allow-multiple-online-payment-gateways-in-one-wa-a and I would appreciate your comments.

I would greatly appreciate comments about there or any other aspects of managing multiple chapters/groups within a single Wild Apricot account.