Setup and configuration

Axon Community Request overview

Axon Community Request makes it easy for law enforcement organizations to securely receive evidence submissions from the community and manage that media in Axon Evidence.

Watch this video to learn how to configure Community Request for your organization.

Request types

• Individual requests: Send requests directly to specific recipients in the community.
• Area requests: Request evidence from camera owners through participating service providers.
• Public requests: Collect evidence from community members through a public submission experience.
• Business Request: Request evidence from businesses within your community. If integrated with Auror, requests will be delivered to the business Auror portal.
• CCTV Request: Send requests to FususREGISTRY participants.
• Integrations: Integrate your system with Community Request.

Roles and permissions

See this video for an overview of configuring your account to use Axon Community Request.

Before users create or manage Community Requests, administrators must review role permissions in Axon Evidence.

Permissions for Community Request are managed through roles. Administrators can modify an existing role, create a new role, or copy and modify a role to enable the appropriate Community Request permissions.

Use permissions to control who can view requests, create requests, manage requests, and triage submissions.

Learn more about Roles & permissions.

Community Request settings

After permissions are reviewed, configure Community Request settings before enabling broad user access to ensure efficient and compliant interaction between the community and your organization.

To access Community Request settings, select Admin, then under Evidence Settings, select Community Request.

Community Request settings are organized by tab. Each tab controls a different part of the request experience.

• General controls contact information, declined-submission retention, language support, terms and conditions, and captions.
• Individual controls field requirements, community member information storage, auto-accept behavior, and reminders for Individual Requests.
• Public controls community member information storage and field requirements for Public Requests.
• Area controls phone-number display, supervisor approvals, NIBRS category selection, and jurisdiction mapping for Area Requests.
• CCTV controls CCTV request fields, community member information behavior, auto-accept behavior, and CCTV audit-log export. CCTV portal requests include standalone permissions: View, Create, and Edit. These permissions default to Prohibited and must be enabled by an administrator.
• Business controls business-request fields and auto-accept behavior.
• Integrations controls request ownership, evidence ownership, retention defaults, notifications, and API clients.

Review the tabs that apply to your organization before granting broad access to Community Request.

For full settings details, including General, Individual, Public, Area, CCTV, Business, and Integrations, see Settings.

Area settings

If your organization uses Area Requests, review the Area tab carefully.

The Add Public Contact Phone Number setting controls which phone number is shown on requests sent to camera owners. Administrators can use the phone number from each submitter’s profile or the same phone number for all requests.

The Enable Supervisor Approvals setting controls whether Area Requests must be approved before publishing. If approval is required, administrators can use default logic or assign approvers by role and select the roles that are eligible to approve Area Requests.

The Area tab also controls NIBRS category selection and the jurisdiction map used for Area Requests.

Permission configuration examples

The following table provides some example Role permission configurations for using Axon Community Request based on different use cases. The Audit Trail PDF permission setting is determined by your agency policies for reviewing audit trails.

View portal	Invite individual	Create public portal	Edit and close public portal	Triage submissions
Use Case: Patrol officers who can invite individuals and must triage their own submissions
Only Their Own	Allowed	Prohibited	Prohibited	Only Their Own
Use Case: Detectives who can create public portals and triage their own submissions
Only Their Own	Allowed	Allowed	Only Their Own	Only Their Own
Use Case: Someone in the public information office who can create a public portal, but not triage themselves
Any Portal	Prohibited	Allowed	Any Portal	Prohibited
Use Case: A centralized group who can triage any portal
Any Portal	Prohibited	Prohibited	Prohibited	Any Portal
Use Case: Command staff who can access and triage any portal
Any Portal	Allowed	Allowed	Any Portal	Any Portal