Reviewed September 7, 2026. Features depend on your enabled modules, permissions, and configured integrations.
What is Numa?
Numa brings constituent cases, legislative records, communications, district information, and office operations into one workspace. Home includes the triage queue; the main desks are Casework, Constituents, Legislative, Comms, District, and Operations. Analytics and Kennedy also have workspaces; Admin, Workflows, and Paths are available through the office navigation and avatar menu as permissions allow.
The office has a structured jurisdiction: municipality, county, state legislative district (with Assembly or Senate selected), or congressional district. That jurisdiction scopes voter matching and voter-based audiences. Staff can also record constituents who are not in the voter file. Sign in with an office password and any required authenticator step, or a registered passkey; select the correct office when using password login.
Getting started: the setup week
NJR runs onboarding; your staff's part is about a week of short sessions:
By the end of the week the queue is real: open cases with owners and SLA clocks, not an empty database waiting for good intentions.
Campaign vs. office
Romulus runs campaigns; Numa runs elected offices. The products share infrastructure and the voter file, while office records and permissions live in their own tables. Working in one product does not automatically authorize access to the other.
Campaign history is a specific exception: a voter-linked case can show selected history when the staff member has the history permission and the office has an active grant to that campaign. Reads are audited and grants can be revoked. Donation summaries and broader campaign-to-office continuity remain follow-up work.
Curia, the sibling for a town, county, or agency as an institution, currently has its account and department foundation plus a workspace shell. Its municipal service modules are still planned. See the platform overview.
Security & privacy
Office access is controlled by roles and permissions. Sensitive actions are recorded in the audit log, including the dedicated campaign-history view. Logs follow the platform’s retention settings.
Public pages show published or explicitly public records; the constituent portal restricts case access to the signed-in constituent. Private status links expose a limited view and should be shared only with their intended recipient. Kennedy’s draft tools do not publish or send.
Export controls vary by module and permission. Ask the administrator for the records or backup process needed for your office instead of assuming every screen has a CSV export.