Tutorials

One short walkthrough per major feature. Replace names, systems, and policies with your agency's standards. As the product changes, exact click paths may differ slightly—use the linked user guides for detail.

Flash PD

Cases and teamwork

1. Open the case list or dashboard and locate the matter by number, title, or tag.
2. If you are starting fresh, create a case with the identifiers and classification your unit requires.
3. Share the case only with cleared colleagues, using the view or edit role your SOP defines.
4. Add or update case instructions so the assistant and teammates know jurisdiction, sensitivities, and what “done” means.
5. Link related cases when suspects or incidents overlap; skim case activity after time away to see uploads and edits. Guide

Evidence workspace

1. From the case, open the evidence area and confirm folder layout matches your team's convention.
2. Upload or ingest permitted material; wait for processing before relying on search or AI on those files.
3. Use filters and search to find a file by name, type, or source; open items from the list to preview or play.
4. For phone extractions, follow your lab's naming so later exports and reports stay traceable.
5. Spot-check a few items against originals before you cite them in reports. Guide

Investigator assistant

1. Open the assistant inside the case so it inherits case instructions and allowed evidence.
2. Ask one focused question at a time; paste short excerpts instead of dumping entire files when possible.
3. Choose faster vs deeper reasoning to match urgency; still verify answers against source material.
4. Use feedback controls if your deployment offers them so the model improves for your unit.
5. Treat outputs as drafts: confirm facts before court, discipline, or charging decisions. Guide

Link analysis (board)

1. After processing, open link analysis from the case and review the entity list for people, places, and objects tied to the evidence.
2. Select entities of interest and open the graph to see how they connect.
3. Use search and path-finding to test hypotheses (“how might A tie to B?”) and note hops that need corroboration.
4. Explore communities or clusters to see groups that move together; read summaries as leads, not conclusions.
5. Export or screenshot only what policy allows; document your reasoning in the case narrative. Board overview, Graph and paths, Communities

Reports and templates

1. From the case, open reports and pick a template that matches the product your prosecutor or partner expects.
2. Fill prompts or fields with verified facts; avoid copying unreviewed AI text straight into charging language.
3. Save reusable templates when your unit repeats the same structure (affidavit sections, timelines, summaries).
4. Preview the full document; fix headings, redactions, and exhibit references before sharing outside the team.
5. Version or rename outputs so supervisors can tell which report matches which evidence drop. Guide

Exports and handoff

1. Confirm what may leave your environment (CJI rules, protective orders, partner agreements).
2. Build a case export package with the folders and reports the receiving agency asked for.
3. Spot-check the bundle: open a sample of media and documents to ensure nothing is missing or corrupt.
4. Transfer through approved channels; record chain-of-custody per your records policy.
5. Keep a note in the case file of what was sent, when, and to whom. Guide

Bookmarks, notes, and spreadsheets

1. Use bookmarks for evidence moments you will revisit in interviews, reports, or court prep.
2. Keep notepad entries short and factual; avoid speculation that could be misread later.
3. Use spreadsheets when you need sortable lists (vehicles, phones, transactions) tied to the case.
4. Align column names with your unit's standards so exports match RMS or evidence indexes.
5. Review shared notes when handoffs occur so nothing critical lives only in one person's head. Guide

Activity and insights

1. Open activity for the case to see uploads, edits, and sharing in chronological order.
2. Supervisors: filter or scan for idle cases, large uploads, or unusual access patterns per your oversight policy.
3. Cross-check activity against your own notes before accusing someone of missing a step.
4. Use insights sparingly for staffing decisions; they supplement, not replace, supervisory judgment.
5. Export or print activity logs only when your policy allows and redact as needed. Guide

Trash and recovery

1. Before deleting, confirm whether your org uses soft delete (recoverable) and who may permanently purge.
2. Move items to trash only after duplicating anything still needed for court or audits.
3. To restore, open trash, locate the item, and restore within the retention window your admin configured.
4. Involve records or legal before permanent deletion of case material.
5. Document restores in your case narrative if the action could matter in discovery. Guide

Flash GPT

Sign-in and security

1. Sign in through the method your agency assigned (SSO, username/password, or federated identity).
2. Complete MFA when prompted; do not share codes or devices.
3. Sign out on shared machines; clear sensitive drafts before walking away.
4. If you see unfamiliar sessions or prompts, stop and contact your security or IT contact.
5. Read local rules on where Flash GPT may be used (office vs VPN vs isolated machine). Guide

Conversations

1. Start each thread with a one-line goal: summarize, draft, extract, or compare.
2. Paste only the minimum text needed; attach files only when policy permits.
3. State audience, tone, length, and constraints (“no legal conclusions,” “cite only attached doc”).
4. Use faster vs deeper modes appropriately; reread outputs for hallucinations or missing caveats.
5. If web search is enabled, verify facts from independent sources before operational use. Guide

Organizing chats

1. Rename threads so future-you can find them (project, date, topic).
2. Bookmark high-value conversations per your product's chat library controls.
3. Share links only with people cleared for the content; remove shared access when the project ends.
4. Periodically archive or delete drafts that contain outdated or over-collected information.
5. Align folder or label conventions with your team so handoffs are obvious. Guide

Files and documents

1. Confirm file types and size limits with your admin before uploading sensitive material.
2. Prefer attachments for one-off review; save to “documents” when the file should persist across sessions.
3. Redact or strip metadata if your policy requires before upload.
4. After analysis, delete attachments you no longer need if retention rules allow.
5. Never upload classified or exempt material outside approved handling paths. Guide

Personas and projects

1. Create or select a persona that matches the tone you need (patrol brief vs executive summary).
2. Scope a project when you have a standing body of work (policy refresh, training series) to keep context together.
3. Adjust persona settings when the audience changes; do not rely on stale instructions across unrelated topics.
4. Review outputs for bias or overconfidence when the persona is “expert-like.”
5. Share project settings only with collaborators who need the same framing. Guide

Templates and timelines

1. Save prompts you reuse (after-action questions, FOIA response outlines, training module shells).
2. Parameterize templates with brackets for names, dates, and jurisdictions so others can reuse safely.
3. Build timelines from documents by asking for a chronological table, then verify every date against sources.
4. Export timelines to your case system or memo only after spot-checking critical events.
5. Version templates when law or policy changes so old drafts are not recycled blindly. Guide

Settings, memories, and privacy

1. Open settings and confirm retention, logging, and default model match your unit's agreement.
2. Review stored memories; delete anything that should not persist (personal data, open complaints).
3. Turn off or limit features (web, plugins) if your security office has not approved them.
4. Use audit or history views, if available, before sensitive meetings to ensure no stray content appears.
5. When in doubt, ask your privacy officer before storing CJI in memories or long-running threads. Guide

Security and deployment

1. Know whether your tenant is CJIS-aligned or general commercial; follow the stricter path when unsure.
2. Use only approved networks and endpoints; avoid personal devices for agency work.
3. Coordinate with IT on updates, VPN requirements, and incident reporting if data may have been exposed.
4. Bundle related questions for security reviews instead of one-off ad hoc uploads.
5. Read your org's acceptable-use policy alongside these guides. Guide

Product reference: Flash PD, Flash GPT.