For a forum such as a job board, it would be very useful if individual posts could be classified or "tagged" according to the type of posting - in this example, internships vs. full-time jobs. That would allow forum users to filter to only those posts that apply to them.
1. Add a column to forums to indicate a category for the post
2. Allow admins to set default categories for each forum
3. Allow forum users to add categories as needed
4. Allow forum users to filter forum posts by category
We have redesigned email settings and extended subscription options for event announcements and email blasts as well. See details in presentation: https://docs.google.com/presentation/d/1bj4iE_bnw_mhLM2u5KMoH6WTCh4n0oPZkDXdB2folt4/pub?start=false&loop=false&delayms=3000
Merged several posts together, so that both public and admins lists can be customized. This is better for analysis and design to work on them together.
Currently, there are a few static fields that indicate who has registered for an event.
Suggested - allow event admins to select what event and/or membership fields to display in the public and back-end (admin) event registrant listings for improved searchability.
Merged together several closely related by meaning ideas – so we can properly resolve them all together, in different live scenarios
Currently, we can only designate one WA domain-specific email address - for us, it's email@example.com. In addition, it functions only as a recipient email.
We would like to create additional emails associated with the ergies.org domain through WA, so that our organization's officers have org-specific addresses they can send emails to other members from. Thank you!
To avoid all site-related emails coming from a common sender, and risking email fatigue for our members, it would be terrific if one-off and system emails had a feature to customize the "From" email field to be someone's personal address, or even just a different alias. This would allow emails for specific purposes (e.g., particular forums or events) to come from an appropriate contact rather than our entire organization, which is less likely to be read.
Since this feature would be very similar to the "Reply to" address field, I'm hoping it wouldn't be that difficult to implement. Thanks for your consideration!
Please review results of our analysis and design:
Post your comments/ideas right here. Until we see major disapproval, this is what we will develop in one of future releases.
This feature would be very useful for my team as well. Some platforms offer the option to sign in using one's LinkedIn or Facebook credentials, and the platform then imports certain profile data from the third-party page. One advantage of this is that users wouldn't need to manage multiple profiles - every time they signed into Wild Apricot using their LinkedIn info, for instance, it would import any updates of their information to their Wild Apricot profile.
12 votesbhmandel shared this idea ·