Getting Started

Getting Started: IT Admin

You configure the technical settings that keep APBnet™ running securely at your agency. Here's what to set up before your users go live.

What you control as an IT Admin

  • Configure single sign-on (SSO) if your agency uses it — when active, user accounts are created automatically
  • Enable and enforce multi-factor authentication (MFA) for your agency
  • Set allowed email domains and configure firewall or proxy whitelisting
  • Manage device access controls — restrict or permit access by device type
  • Configure optional data integrations that connect APBnet™ to external agency systems

First things to do before go-live

Complete these steps in order — each one affects whether the next step works correctly.

  1. 1

    Configure allowed domains

    Add your agency's email domain(s) to the allowed list in the IT Admin panel. This controls which email addresses can be used to create accounts at your agency. If your agency uses multiple domains — a primary and a subdomain, for example — add all of them. Also include domains used by approved contractors, such as IT support firms, if they need direct access.

  2. 2

    Set up SSO if your agency uses it

    If your agency uses a single sign-on provider, configure the integration before any users log in. Once SSO is active, accounts are created automatically — your User Admin just assigns roles. Contact the Critical Reach team if you need provider-specific configuration guidance.

  3. 3

    Enable MFA

    Enable multi-factor authentication for your agency in the IT Admin panel. If your agency is subject to CJIS requirements, MFA is required — enforce it at the agency level so individual users can't opt out. Users will be prompted to set up their second factor on next login.

  4. 4

    Whitelist APBnet™ traffic on your network

    If your agency runs a web content filter or proxy, add APBnet™ domains and IP ranges to your allowlist before go-live. The current list is available in the IT Admin portal. Test access from a standard user workstation — network rules often differ between admin and standard accounts.

  5. 5

    Configure device access controls

    Set which device types are permitted to access APBnet™ at your agency — agency-issued only, personal devices, or both. If your agency has a mobile device management (MDM) policy, make sure APBnet™ is included in the managed app list before officers try to access it from the field.

Screenshot pending

getting-started/it-admin-settings.png

IT Admin settings panel — SSO, MFA, domains, and device access controls

1200 × 700

IT Admin settings panel — SSO, MFA, domains, and device access controls

Essential how-to guides

Tips for IT Admins

Configure SSO before users start logging in

Once SSO is active, user accounts are created automatically. If users create accounts manually before SSO is configured, those accounts may conflict. Set up SSO first — coordinate with your User Admin so they're ready to assign roles as accounts come in.

MFA and CJIS compliance go hand in hand

If your agency handles CJIS-covered data, MFA is required. Enable and enforce it during setup, not after an audit finding. APBnet™ supports standard authenticator apps and SMS-based verification.

Test domain whitelisting before go-live

If your agency runs a web filter or proxy, APBnet™ traffic needs to be whitelisted before users can access the platform. Test from a standard user workstation — not just your admin machine, which may have different network rules.

Data integrations are optional and additive

APBnet™ can connect to external data sources to enrich bulletin information. These integrations are configured per agency and don't affect core functionality if they're not enabled. Enable them only when the integration has been tested and approved.

Where to get help

For SSO integration support, domain and IP whitelisting details, or data integration configuration, contact the Critical Reach team directly via the support form in the Admin tab. Technical configurations that can't be completed from within the app require Critical Reach involvement.