# Marion SharedNetworks August 2026 The PDF prints the fields `"Organization"`, `"Networks Shared With Me"`, and `"Networks I'm Sharing"` (`Shared Networks_2026_August11 Flock.pdf`, p. 1). Pages 1-48 contain 2,094 visible organization rows; pages 49-56 are blank and page 57 contains overflow/footer material. ## Configuration counts | Metric | Count | |---|---:| | visible organization rows | 2,094 | | inbound-populated rows | 603 | | outbound-populated rows | 531 | | both directions populated | 386 | | inbound only | 217 | | outbound only | 145 | | neither sharing field populated | 1,346 | Every populated outbound cell names a Marion network; 193 name both `Marion AR PD` and `Marion AR PD Condor` (full visible table, pp. 1-48). ## West Memphis cross-check Page 15 contains the West Memphis row with Marion networks in the outbound column (`Shared Networks_2026_August11 Flock.pdf`, p. 15, visually verified `West Memp...` row). West Memphis's separate August 4 CSV names both Marion networks inbound and West Memphis outbound (`SharedNetworks_2026_August_4.csv`, Marion row; [[West Memphis SkyCop Locations and Flock SharedNetworks August 2026]]). The two agencies' records independently corroborate configured directions. They do not prove who initiated the relationship, whether it came from a default, or whether either tenant searched or transferred data through it. ## Open questions - Native CSV export to remove print truncation and preserve exact row values. - Administrative change history and approvals for each direction. - Search-level audit records showing actual network use.