To back up our website, our Contacts, images, and other data, Wild Apricot advises using a rabbit-warren of methods that includes special installation and understanding of third-party services. For our volunteer organization, where we change jobholders every year or two, that is just not practical and puts us at risk.

WA itself backs up our entire system in case of a catastrophe, but it's not available to the WA customer (which is understandable). We need essentially the same capability to do this ourselves, routinely and without extraordinary effort. We'll figure out where to store the data. Given the overall WA service concept, your omission of this -- and all the rube goldberg workarounds -- is NOT understandandable.

By the way, even with the various backup methods advised, none of them backs up Saved Searches and manual email Templates. What else in our system is at risk? We don't even know.

There is another thread wishing for this. It has surprisingly few votes, even though it dates back to 2008. But that wish's headline mentions only "website." That's the least of our concerns. And, as everybody knows, backup is always a neglected user issue, even though it is among the most essential concerns. WA should provide this capability as a matter of professional service, not wait for customers to vote who never will.

Contacts/members with full administrative authority in particular, and to an extent perhaps, others with lesser administrative authority should have a wall erected between being just a normal member and acting as an administrator.

When I login as a member, I don't want to be in administrative mode. This mixes roles, and these roles must kept separate. When I want to go into administrator mode, WA must require me to explicitly request that role/mode (eg, a separate password, or some other mechanism).

I've also noticed that WA does not automatically logoff users after a period of time. In particular, for those with administrative authority, or in administrative mode, it is a security breach to allow such connections to remain open and active.

As a Wild Apricot partner we are tasked to do the following:

- setup a new WA website and launch
- migrate an existing WA website with new website designs

This feature is particularly helpful when a customer is already on Wild Apricot, in production but would like to test some new website design features or redesign the website altogether.

Currently our approach is to clone the production site with WA support, design on the clone and then move manually over to production. It would be really helpful if WA featured a way to export configuration options that can be imported into another WA website.

For starters I could see

1. Theme selection
2. Colors & Styles Configuration
3. Bulk File manager download (not just file by file)
4. Site template configuration

If you could export these settings and import them into an existing WA website and apply these changes it would really help.

Of course exporting events and related configuration settings for each event, exporting site pages between sites would also be nice.

Another approach would be to allow a "staging" feature to be available inside a site that can allow a separate website to be designed and Promoted to production, archiving site pages, overwriting configuration settings.

I realize it's a complicated ask with lots of issues, but right now WA redesigns and new configuration and experimentation is not really possible on a production WA system. You have to clone and move the results manually.

We'd love to have a separate email address field for administrators for their administrative emails.

In our organization, admins are members of the organization and board members. As board members, they receive an organizational address, like membership@thisorg.org or president@thisorg.org. As members, their email address is their personal address, like sam.jones@gmail.com.

We'd like to have their membership address be their personal address (eg sam.jones@gmail.com) and their WA administrator address be membership@myorg.org.

So when they receive general email, like their person renewal confirmation, it goes to sam.jones@gmail.com. But when they receive administrator emails, such as a new member notification, it goes to membership@myorg.org.

Thanks!
JD