Implementation, system requirements, security, and how data gets into FINDER®. Detailed user guides and instructional videos are also in the Support section inside the platform.
Your account executive works the process with you. Steps can run concurrently, and an individual agency’s path varies with its systems and requirements.
Yes. This is the contribute path, from executed MOU through data validation and full access.
Shorter, because there is no data connection to configure.
Read-only credentials for your CAD or RMS, and a data fragment so we can configure the parser for your system.
FINDER Agency Administrator. Someone with knowledge of your personnel. They approve and deny account requests, edit and delete user accounts, expunge records, and run audits and logs.
Data Validator. A temporary role during implementation. They compare three of each report type in FINDER against the originals in your RMS, checking that fields mapped correctly and that nothing appears in FINDER that should not be there.
No. FINDER installs a data parser on a local agency machine that reads the reports and makes a copy available in the platform. You provide a data fragment so we can configure the parser, then complete data validation to confirm records return correctly.
Yes, through FINDER Integrate. Custom extract, transform, and load work moves legacy data from one database to another, which suits agencies changing RMS systems that want to keep their history.
We also build APIs so agencies can connect mapping tools, analytical programs, and external law enforcement data sources.
A Windows machine that can read your data sources and connect to FINDER. The uploader is a .NET console application scheduled through Windows Task Scheduler. It uses roughly 100MB of RAM, 2GB of disk, and about 5 percent of CPU while running, so a dedicated machine is not required.
No. FINDER is a web application, so there is no client software to package, deploy, or patch. Users sign in at login.findersoftware.com from a current, updated computer with a high speed connection.
Supported browsers are listed on the general FAQ.
On AWS GovCloud, a secure cloud environment built to meet federal compliance requirements, which provides data protection, scalability, and resilience.
FINDER is designed to meet the technological directives established by the federal government for sharing law enforcement data. Our team members are CJIS trained.
Multi-factor authentication uses an authenticator app or hardware token, consistent with CJIS Security Policy v6.0 control IA-2. Email one-time passcodes do not satisfy that control and are being removed.
Through a Secure File Transfer Protocol server that is FIPS 140-2 compliant and secured end to end.
Bulletin Upload module. From the Dashboard, click the Bulletin Upload icon, choose your PDF files or drag several in at once, and submit. FINDER indexes people, vehicles, and property characteristics along with the bulletin date and classification, and they become searchable once processed. Requires the Bulletins module.
SFTP. We provide an SFTP folder for bulletins and other files. Contact support for access instructions.
Email. Create a forwarding rule in your department workflow to send bulletins automatically. Contact support for access instructions. To maintain CJIS compliance, the email option requires an email security certificate.
SFTP. The same SFTP folder handles hotlist files. Contact support for access instructions.
Email. Forward hotlist files to lpr@findersoftware.com through a department forwarding rule. This option should not be used for CJIS protected information.
The CLEAR connection is standard within FINDER Investigate. Users need active accounts with both FINDER and CLEAR, and your agency needs the CLEAR sharing API activated. Setup happens during implementation, or contact FINDER support or CLEAR support.
Our engineering team adds your unique Clearview API key to the system. To generate it: enable the API keys permission set in your Clearview admin section, click the drop-down beside your user name and select API Keys, then Create API Key, and name it for your agency. You will receive a QR code and an alphanumeric code. Send that code to your FINDER onboarding consultant.
Once your agency subscribes and completes the idiCORE user agreement, FINDER support provisions the API key for search. Your agency administrator then enables permissions for the users who should have access.
Access is granted per user rather than agency wide by default. More detail is on the FINDER Public Records page.
Once your agency subscribes and completes the Sigilite user agreement, FINDER support provisions the API key for search. Your agency administrator then enables permissions for the users who should have access.
Access is granted per user rather than agency wide by default. More detail is on the FINDER AdTech page.
The IRIS connection is standard in FINDER. Users need both a FINDER and an IRIS account, and IRIS must activate the account for data sharing to function. Setup happens during implementation, or contact FINDER support or IRIS support.
On the Product Release Notes page.
Submit it through the support form and our engineering team will review it. Not everything can be implemented, since development cycles are finite and the customer base is wide, but every request gets read.
Parsers need updating when your vendor ships a new version. We coordinate with your IT staff ahead of the upgrade, update the parser afterward, and test to confirm every record type is still flowing. More detail is on the parsers page.
If your question is not covered here, open a support request and someone will pick it up.
Supporting law enforcement for over 20 years.
© 2026 FINDER® Software Solutions LLC