Operations module
Compliance, elections, dues/billing, and retention surveys — the structured workflows that keep an organization running.
Operations is the bundle of structured workflows that keep an organization running through a year: tracking what chapters owe and submit, running national or chapter elections, billing dues and collecting payments, and measuring whether members are sticking around. All four surfaces flip on together with the single Operations license.
PNM (Potential New Member) intake — public apply pages, application questions, attachments, reference letters, GPA gates, and consent templates — travels with the organization itself rather than living under its own module slug. It surfaces inside Operations workflows for orgs that recruit through GreekManage.
Audience
- Members see their own status: invoices, ballots, surveys, and compliance state.
- Chapter officers submit on behalf of the chapter, run chapter-scoped elections, and review chapter billing.
- Regional admins review tier-two compliance and watch the chapters they oversee.
- National (org) admins configure the whole program — only org admins can set dues structure, payment processor, compliance requirement templates, election templates, semester windows, retention snapshot config, and PNM. Chapter officers and regional admins cannot configure these from their surfaces.
What gets enabled
When Operations is licensed:
- An Operations group appears in chapter and regional sidebars containing Compliance, Elections, Billing, and Retain.
- Org admins see those four areas as separate top-level entries in their navigation.
- Background jobs that handle dues invoice generation, overdue detection, election open/close, retention snapshots, and survey expiry start running.
- No data is auto-created — settings rows appear the first time a page is opened and saved.
Operations sidebar group with the four module entries.
Common workflows
For members
- Pay an invoice or view billing history → Dues & invoices
- Cast a ballot in an open election → Voting in elections
- Respond to a retention survey → Surveys & responding
- Submit personal compliance evidence → Compliance submissions (member)
For chapter officers
- Submit a chapter compliance requirement → Compliance submissions (officer)
- Review tier-one chapter compliance approvals → Chapter-tier review
- Author a chapter election → Running an election
- Reconcile chapter billing → Chapter billing
- Run a retention pulse for the chapter → Retain surveys
- Review PNM applications → PNM applicant review
For national / org admins
- Build a compliance program → Compliance program · Requirement templates · Multi-tier approval · Semester management · Alerts and overrides · Chapter dashboards
- Configure dues → Dues billing · Periods · Rates · Payment processor · Invoices
- Author an election → Elections authoring · Positions and candidates · Results and live tracking
- Configure retention → Survey authoring · Retention snapshots
- Stand up PNM intake → PNM admin onboarding · Program · Periods · Application questions · Public apply page · Notification routing
What's NOT in this module
- Operations does not include a chapter forum, bulletin board, or photo album surface — those are in Community.
- Dues uses one payment processor at a time; Foundation fundraising uses Stripe through a separate, sibling configuration in Foundation.
- Retention is signal and survey only — it does not write back to billing or compliance automatically.
- PNM is not its own licensable module; it activates with the org and surfaces through Operations-style permissions.
Where to go deeper
- Post-enable runbook → Operations runbook
- Org admin overview → Org admins
- Module enablement (platform admin) → Module enablement
Last verified against v0.62.1 (2026-05-11).