Skip to main content

Operations — post-enable runbook

You just had Operations turned on. Operations bundles compliance, elections, dues / billing, and retention surveys — they all flip on together with the single Operations license. Use the next half hour to get the most-used pieces wired up.

For background on what each surface does, see the Operations module reference.

Prerequisites​

Before Operations is useful, confirm:

  • An active org admin is in place to author the program.
  • Email delivery is configured at the platform level so reminders, notices, and overdue alerts actually leave the building.
  • Storage is configured for the org, since compliance submissions can carry file attachments.

If billing is on your day-one list, also have your payment-processor credentials handy (Stripe is the supported gateway today).

Who can enable it​

Only a platform admin can flip the Operations toggle for your org. Org admins request the change through their platform admin. Once enabled, org admins, regional admins, and chapter officers see their respective surfaces.

What gets auto-created​

Enabling Operations does not create any records on its own — the toggle simply unhides the sidebar entries and lets requests through. Per-org settings rows (such as dues settings) are created the first time you open the relevant settings page and save.

What appears in the sidebar​

A new Operations group shows up for everyone with access. Inside it:

  • Compliance
  • Elections
  • Billing
  • Retain

Regional admins see the same group minus Billing.

First 30 minutes — required steps​

  1. Open Org → Settings → Dues & Billing. Pick a billing cadence (per semester or per term) and save. This creates the dues settings record.
  2. In the same panel, open the Payment Processor section. Enter your Stripe secret key, publishable key, and webhook secret. Save. The status badge flips to Active once the credentials validate.
  3. Open Org → Compliance. Create your first requirement (name, due date, who it applies to). Without at least one requirement, chapters see an empty page.
  4. Open Org → Elections and confirm the page loads. If you plan to run an election in the next few weeks, draft it now so officers can see what is coming.
  5. Open Org → Settings → Logging and confirm audit logging is enabled. Compliance reviews and election votes are sensitive — you want the trail.

First 30 minutes — recommended next steps​

  • Pick a semester model in Compliance → Semesters so submissions land in the right reporting window.
  • Add a couple of compliance requirement templates in Settings. Templates let chapters spin up the same set of requirements every term.
  • Send a one-line bulletin from the dashboard letting chapters know dues and compliance are now live.

What happens if you disable​

Turning Operations off hides the entire Operations group from sidebars and returns 403 on the related endpoints. Data is preserved — invoices, ballots, compliance submissions, survey responses all stay in the database. Re-enabling restores access immediately.

Common gotchas​

  • No payment processor means no charges. You can list dues amounts without Stripe, but chapters cannot pay until the processor is verified.
  • Compliance with no requirements looks broken. Members and officers see a blank page until you author at least one requirement.
  • Election due dates are timezone-sensitive. Pick your org's primary timezone in Settings before scheduling close times.
  • Retention surveys need active members. A brand new org with no memberships will show empty analytics until members are added.

Where to go deeper​

Last verified against v0.62.1 (2026-05-10).