Settings
Use this article to review the settings available in Community Request. Community Request settings are organized by tab and control how requests are created, reviewed, and submitted.
To access Community Request settings, select Admin, then under Evidence Settings, select Community Request.
General tab
Help contact settings
Enter up to three contact methods for community members to use if they have questions about their evidence submission. These contact methods are shown at the bottom of Community Request pages that community members visit.
- Enable contact information turns contact information on or off.
Retention period for declined submissions
This setting applies to both individual invites and public portals.
Declined evidence uses the default category retention period unless a custom retention period is specified. If evidence declined during triage should have a custom retention date:
- Use custom retention period lets administrators define a custom number of days.
Language support
Provide translations for Community Requests in the supported regional languages.
Terms and conditions for Community Request settings
Display terms and conditions before allowing a community member to submit evidence through the submission portal. The terms and conditions should include translations for supported languages.
- Enable Terms and Conditions turns the disclaimer on or off.
- For each supported language, administrators can enter disclaimer content, external document link text, and an external document URL.
If changes are made to the disclaimer, the User and Agency Audit Trails store an action for Agency Community Request Setting 'Terms and Conditions Disclaimer for Community Request Invite Settings' changed. The following changes are tracked:
- Show agency disclaimer
- Agency disclaimer content updated
- Agency disclaimer links updated
- Hide agency disclaimer
After Terms and Conditions are enabled, when a community member opens a request (the request works for both public portals and individual invites), they must accept or decline the terms and conditions before continuing to the portal to upload evidence.
Selecting Decline generates the disclaimer message you enter here.
If the user changes their mind, they can re-open the original request, accept the terms and conditions, and submit evidence until the request expires.
Individual tab
Incident info
Control whether the following fields are optional, required, or hidden for Individual Requests:
- ID Field
- Categories Field
- Description Field
Community member info
For each community member field, administrators can choose whether the field is optional, required, or hidden.
- Store community member information in Axon Evidence controls whether community member information is stored in Axon Evidence and made available in reports, audit trails, and other components.
- First Name
- Middle Name
- Last Name
- Date of Birth
Auto-accept submissions
When Auto-Accept is on, submitted files are automatically accepted and placed in Active status. When Auto-Accept is off, submitted files are placed in Pending Triage status and can be manually accepted or declined.
- Auto-Accept submissions from Individual invites turns this behavior on or off.
Automated reminders
Reminder messages are sent at the configured intervals following the initial request. Reminders are recorded in the Audit Trail and are not sent for anonymous requests.
- Send reminders for Community Request invites turns reminders on or off.
Public tab
Community Member Info
For each community member field, administrators can choose whether the field is optional, required, or hidden.
- Store community member information in Axon Evidence controls whether community member information is stored in Axon Evidence and made available in reports, audit trails, and other components.
- First Name
- Middle Name
- Last Name
- Date of Birth
Area tab
Add Public Contact Phone Number
Each request shows the requester name, requester email, and a phone number so camera owners can ask clarifying questions or provide additional information. Select the phone number to display.
- Use the phone number from each submitter's profile shows the phone number from the requester profile.
- Use the same phone number for all requests shows one phone number for all Area Requests.
- Public Contact Phone stores the phone number used when the same phone number is shown for all requests.
- Generate from location automatically creates the jurisdiction map for the Area Request based on the selected location, so admins do not need to find and upload a map file manually.
Enable supervisor approvals
Enabling supervisor approvals requires all Area Requests to be approved before publishing.
- Require supervisor approval for Area Requests turns approval on or off.
- Use default logic uses the default approval logic for eligible approvers.
- Assign approvers by role lets administrators restrict approval to users assigned to selected roles.
- Select Role(s) lets administrators choose which roles are eligible to approve Area Requests.
Enable NIBRS categories
Requests must include a category from the National Incident-Based Reporting System (NIBRS). Administrators can allow or restrict requests based on selected NIBRS categories.
Jurisdiction map
A jurisdiction map is required to use Area Request. If you already have a map, select Import from file. If you do not have a map, select Generate from location to create one using Esri boundary data. Validate the map before it loads.
CCTV tab
Export audit log for CCTV requests
Export an agency-wide CCTV Requests audit log in PDF format. The report includes access activity and reasons for tool use within Axon Evidence.
CCTV request settings
Incident info
- ID Field
- Categories Field
- Description Field
For each incident information field, administrators can choose whether the field is optional, required, or hidden.
Community Member Info
For each community member field, administrators can choose whether the field is optional, required, or hidden.
- Store community member information in Axon Evidence controls whether community member information is stored in Axon Evidence and made available in reports, audit trails, and other components.
- First Name
- Middle Name
- Last Name
- Date of Birth
Auto-accept submissions
When Auto-Accept is on, submitted files are automatically accepted and placed in Active status. When Auto-Accept is off, submitted files are placed in Pending Triage status and can be manually accepted or declined.
- Auto-Accept submissions from Individual invites turns this behavior on or off.
Business tab
Incident info
- ID Field
- Categories Field
- Description Field
For each incident information field, administrators can choose whether the field is optional, required, or hidden.
Auto-accept submissions
When Auto-Accept is on, submitted files are automatically accepted and placed in Active status. When Auto-Accept is off, submitted files are placed in Pending Triage status and can be manually accepted or declined.
- Auto-Accept submissions from Individual invites turns this behavior on or off.
Integrations tab
Request Owner
- Invitation Owner sets the default owner for invitations created through integrations.
- Notify invitation owner when portal is created turns notifications on or off.
Evidence owner
- Evidence Owner sets the default owner for submitted evidence.
- Notify evidence owner when evidence is submitted turns notifications on or off.
- Auto-accept submission into evidence controls whether submitted evidence is automatically accepted into evidence.
Default retention category group
- Default Retention Category Group sets the default retention category group for integrated submissions.
API clients
Use API Clients to manage integrations that create and modify evidence requests. The table lists the client name, permissions, and updated date.
