Reviewed September 7, 2026. Features depend on your enabled modules, permissions, and configured integrations.
Staff & roles
Admin opens from the avatar menu at the right of the top bar. It is deliberately not a tab, because most of the office never needs it. Roles are built from granular permissions (view_cases, manage_cases, assign_cases, view_campaign_history, view/manage_legislation, view/manage_office_comms, view_district_intel, view/manage_office_ops, manage_office, manage_office_users, view_office_audit), so interns see the queue and nothing else.
Users carry a name, email, role, and active flag; the superadmin manages accounts themselves. Name roles for the office, not the software (“Chief of Staff,” “Caseworker,” “Legislative Director,” “Comms”), and audit who holds view_campaign_history twice a year.
Signing in
Office staff can sign in with a password or a passkey. Register a passkey from the avatar menu’s Passkeys option. Password sign-in includes an office selector and an authenticator step when enabled; a passkey identifies its office account directly.
The same email can be used in more than one office, but each office membership has its own scope and permissions. Microsoft SSO support exists in the backend, but the current Numa login screen does not display a Microsoft sign-in button.
The constituent portal
One switch, gated on the office being public-enabled with casework on, plus the stats to run it: constituents, verified accounts, pending invites, active sessions, portal-filed cases.
Each account opens a drawer with its cases, its sessions (with IP and a revoke action), its notifications, and resend-invite or delete. Revoking a session logs that device out on its next request; the constituent's cases are untouched.
Public surfaces
Public office pages require the office’s public setting and the relevant module feature. Press releases, blog posts, positions, votes, and events also have their own publication or visibility rules. Review the public result before sharing it.
The constituent portal additionally requires portal access and casework to be enabled. The visitor kiosk requires office operations. These settings have dependencies; they are not all independent switches.
Newsletter subscribers and opt-outs are managed in Comms → Subscribers. Subscriber sends exclude opted-out addresses automatically.
The audit log
The office audit view lets authorized staff inspect recorded actions by actor, category, and date. Use it to review staff changes, casework activity, and access to campaign history.
Audit history is subject to configured retention. It is not a permanent archive of every request or every failed permission check; preserve required records through the office’s records and backup procedures.