# SSO Provisioning Notifications Series **98 variants** across two subject patterns documenting Conway PD's **Single-Sign-On user provisioning activity** on the Flock platform. The volume — 98 SSO-related notifications over ~12 months — establishes that **Conway PD operates a substantial Flock user base** and uses SSO-based identity management (rather than per-user Flock-credential issuance). Each notification is platform-generated when a Conway-domain user signs in via SSO for the first time, or when an existing Flock user is linked to an SSO identity. ## What's inside **Two subject patterns:** | Pattern | Count | Purpose | |---|---:|---| | `New User Sign-in using Single-Sign-On` | 73 variants | Notification when a new Conway-domain user (typically `[email protected]`) signs into Flock via SSO for the first time | | `New User Linked to Existing User using Single-Sign-On` | 25 variants | Notification when an existing Flock user account is linked to an SSO identity (consolidation event) | Total: 98 SSO notifications. All to `[email protected]` (the Conway Flock admin). ## Key takeaways - **Conway PD's Flock user count is substantial.** 73 first-time SSO sign-ins over ~12 months represents 73 distinct Conway-domain users who accessed the Flock platform during that window. Given CPD's documented headcount of 138 sworn officers ([[AR - Conway PD - Welcome to Flock! (3) - Flock Kickoff Slide Deck]]), this implies **roughly 50% of sworn officers have at least one-time Flock access**. The audit-log series documents what those users do (~10,391 searches over 13 months per [[Conway PD Audit Logs Series]]). - **SSO is the access mechanism.** Conway PD's identity-management infrastructure (presumably Microsoft 365 / Azure AD or a similar SAML provider given the `[email protected]` pattern) is integrated with Flock for user provisioning. This is consistent with CPD Policy 800-32 Section D.3 requiring username/password-authenticated access; SSO is the operational implementation. - **The 25 "Linked" notifications are an interesting subset.** Each represents a user who already had a Flock account (perhaps issued during onboarding before SSO was fully configured) being merged with the user's SSO identity. The 25 vs. 73 ratio suggests **about a quarter of Conway PD's Flock-active users predate the SSO integration** — likely accounts created during the Jan-Mar 2025 onboarding window before SSO went live. - **The corpus does not enumerate which users SSO-signed-in.** The notifications go to Burningham, presumably with the new user's name in the body, but the volume and per-name details would require reading each .msg, which remains an open task. The Conway PD Audit Logs Series ([[Conway PD Audit Logs Series]]) is the more useful record for "who used the system" because it shows actual searches, not just sign-ins. - **Burningham as the single notification target is consistent with the [[Action Requested - Pending Flock Camera Share Requests Series]] finding** — Burningham is the lone Conway-side admin, no delegation, no backup. ## People and orgs mentioned - [[Lt. Andrew Burningham]] — sole recipient; Conway Flock admin. - [[Flock Safety, Inc.]] — automated sender. - **Conway PD's identity provider** — likely Microsoft 365 / Azure AD; not directly confirmed in the corpus. - 73 first-time-SSO Conway PD users (individual names not surfaced in this batch ingest). ## Concepts invoked - [[Flock Audit Logs and Retention]] - [[CJIS Compliance]] — SSO-with-MFA satisfies CJIS access-control requirements per Flock's marketing claims. ## Events documented - *2025-04 → 2026-04 — 98 SSO sign-in / linking events at Conway PD.* ## Cross-references - [[Conway PD Audit Logs Series]] — what the SSO-provisioned users do once logged in. - [[Conway Police Department]] — 138-sworn-officer context. - [[Action Requested - Pending Flock Camera Share Requests Series]] — parallel admin-volume signal. ## Open questions / follow-ups 1. **Per-user activity distribution.** Of the 73 SSO-provisioned users, how concentrated is their actual Flock search activity? The audit logs (cross-reference open question #3 in [[Conway PD Audit Logs Series]]) would answer this — is search concentrated in a few power-users (Narcotics + Investigative + Burningham) or distributed broadly across the 73? 2. **SSO-related MFA configuration.** Per [[Flock Cameras Apr 2026 City Council QA Thread]], Flock made MFA default in November 2024. Whether Conway PD's SSO integration enforces MFA on Flock-platform access is testable from Flock's admin UI; not visible in the corpus. 3. **Account deprovisioning.** When a Conway PD officer leaves the department, is their Flock SSO access automatically revoked? An open question about the SSO provisioning and deprovisioning workflow.