Screenshot placeholder: Split view — Web Admin agency settings and Dispatch CAD dashboard
Who this is for
Before you start
- Know whether you are in Sandbox or Live organization.
- Use a dedicated admin account for configuration (not a shared dispatch login).
- Keep a second browser or window: Web Admin + Dispatch CAD.
Go-live checklist
1. Users and roles
Web Admin: Users lifecycle- Invite dispatchers with Dispatcher role.
- Assign correct agency access.
- Deactivate test accounts before production.
- User signs in and sees expected org in header.
- Sidebar matches role (Roles and access).
2. Incident types and New CFS
Web Admin: Organization Incident types — active types for your org. Verify in Dispatch CAD:- New CFS (F1) → types appear in dropdown.
- Create a test call in Sandbox; confirm type, priority, and numbering.
3. Quick calls (F8–F12)
Web Admin: Organization Quick Call Shortcuts — map keys to incident types. Verify in Dispatch CAD:- Press each configured F-key from dashboard.
- Reload Dispatch CAD if a template was just added.
4. Agency settings
Web Admin: Agency settings (core)5. CJIS and NCIC
Web Admin: Integrations settings- CadmusAdmin sets org CJIS site.
- AgencyAdmin enables State/NCIC Access.
- User overrides only if policy requires (User agency overrides).
- Run training query on Sandbox call — see Queries and NCIC.
- Confirm CJIS Access Denied is resolved before go-live.
6. Command line aliases
Web Admin: Admin configuration (Web Admin) — Command Aliases, Call Shortcodes, Disposition Codes. Verify in Dispatch CAD:- Type
HELPon dashboard and on call detail — lists match what you enabled. - Dry-run test in admin test box if available.
7. Units and login
Web Admin: Units and vehicles for the agency. Verify in Dispatch CAD:- Login User (F2) — units appear, login succeeds.
- Mobile unit sees assignments — Unit login and assignment.
8. Notifications
Web Admin: User notification preferences and org Notification Templates. Verify:- Dispatcher hears/sees alerts for test incident types.
- Mobile voice alerts if used — Voice alerts.
8b. Dispatch SMS (if enabled)
Web Admin:- Notification Templates (
/notification-templates) — Incident SMS wording - Groups — recipient lists for field supervisors
- User phone numbers on every SMS recipient
- Send SMS on a Sandbox test call — see SMS templates and messaging
- Confirm SMS History and send-results dialog
9. RapidSOS (if used)
Web Admin: RapidSOS management Configure credentials and Runtime Settings (RAD-E, LEI, EDX, dispatch agency). Verify in Dispatch CAD:- Staged alerts on map → Import / Create New CFS
- Map layers RapidSOS Locations / Breadcrumbs
- RapidSOS Lookup or Track Phone Number on sandbox test number (when enabled)
9b. GIS uploads and publication
Web Admin: GIS Data Management Use this area to upload zipped GIS artifacts, review preview results, save field mappings, and publish organization-scoped GIS datasets. Verify in Dispatch CAD:- address validation succeeds for known addresses
- expected map overlays appear for the org
- no unexpected out-of-coverage behavior appears after publication
10. BOLOs and operational boards
Verify in Dispatch CAD:- Create test BOLO — appears on BOLOs tab and in mobile BOLOs and warrants.
- Operational greaseboard categories match SOP — BOLO, greaseboard, and wrecker.
11. Citations (if used)
Web Admin: Citation and report settings and Agency settings (CAD Module / E-Ticket Module) Verify on Mobile CAD:- E-Ticket available when E-Ticket Module and Traffic Stops Allowed are on.
- Call-linked citations when CAD Module is on; standalone issue/sync when CAD Module is off (e-ticket-only agencies).
- See E-citations overview.
Daily admin tasks
Common mistakes
Escalation
Collect for Cadmus support: organization name, agency name, user email, time of issue, screenshots (no CJIS data or query responses). See Troubleshooting and Web Admin troubleshooting.Related documentation
- Web Admin — intro
- Mobile CAD — settings that affect field units
- Dispatch CAD — Getting started