Request a Feature
The best feature requests come from the societies actually running SocietyPress. Tell us what you need.
SocietyPress's feature set came from listening to society administrators describe the specific problems they face. The next round of features will come the same way. If there's something missing that would make your job easier, we want to hear about it.
This opens your email app with the template already filled in.
What we prioritize
Not every request lands in the plugin, and we try to be honest about why. Broadly, features that fit these patterns rise fastest:
- Multiple societies need it. If three or four societies independently describe the same pain, that's a signal.
- It's core to society operations. Membership, events, records, library, newsletter, governance — the plugin's native territory. One-off integrations get lower priority.
- It doesn't require ongoing external dependencies. SocietyPress is designed to run on any standard host with zero monthly service fees. Features that need a paid API or a hosted service compromise that, so they need a very strong case.
- The data model supports it. Some requests turn out to be easy; others would require re-modeling a core table. We'll tell you honestly which yours is.
What happens after you send
- We acknowledge your request within a few days.
- We ask clarifying questions if the problem isn't clear enough.
- If it's a fit, it goes on the public roadmap with a rough priority.
- If it isn't a fit, we'll tell you why — and often suggest a workaround.
Feature requests that are already on the list
Before you write a new request, skim the public roadmap — your idea may already be tracked. If so, a quick email saying “we need this too, and here's why” still helps us prioritize.