Jurat
Sworn Statements Security Portal

Administrator Guide

Setting up your agency, assigning the two roles every user carries, and filling in the content that appears on documents your victims and affiants receive.

Role: Admin Jurat Console Online Reporting Console
Section 1

Two systems, one sign-in

Your agency has two websites. They share one login, one user list and one case file.

Staff work at demo.myjurat.com. Citizens file at reporting.myjurat.com. Both are configured from the same admin console, and you sign in to the staff site with your agency Microsoft account.

The staff site
Where your personnel sign in. Sworn statements, victim packets, training sign-in sheets, search, the admin console.
The public site
Where citizens file online reports. No sign-in, no staff pages — a citizen who types a staff address there gets a Not Found.

Officers sign in here. The public fills this out. Same case on the back.

Sign-in

Staff sign in with Microsoft Entra ID — the same account they use for email. Jurat never holds a password. Before the sign-in redirect, every user must accept the restricted-system notice; that acknowledgment is recorded.

Section 2

Every user carries two roles

A Jurat role and an Online Reporting role, set independently on the same user. This is the single most important thing to understand before you assign anybody.

They are separate because who handles online reports varies by agency — a duty officer at one, a dispatcher at another, the records desk at a third. That cannot be guessed from someone's rank, so you state it.

Admin here is not admin there

An Online Reporting Admin configures the intake form, incident types and online-reporting settings. They do not get the Jurat admin console. That stays with the Jurat Admin role only. A user can hold one without the other, and that is a normal combination rather than a mistake.

Jurat roles

These are five different shapes, not five rungs of a ladder. Records and Officer are not higher or lower than each other; they do different jobs.

CapabilityOfficerSupervisorRecordsRequest OnlyAdmin
Create a statement request or victim packetYesYesYesYesYes
Countersign a statementYesYesNoNoYes
Save a personal signatureYesYesNoNoYes
See all pending / completed at the agencyOwn onlyYesYesNoYes
Add or remove an assisting officerNoYesYesNoYes
Reassign the primary officerNoYesNoNoYes
Revoke a caseNoYesNoNoYes
Download / export any caseNoYesYesNoYes
Send a reminder on any caseNoYesYesNoYes
Full audit trailOwn, limitedYesYesNoYes
Run a training sign-in sheetYesYesNoNoYes
Override retentionNoYesNoNoYes
Lock / unlock a caseNoNoNoNoYes
Admin console & user managementNoNoNoNoYes

Request Only is for someone who starts a request and has no business seeing it afterwards — a front-counter clerk, a volunteer. They create and that is all.

Online Reporting roles

These are a ladder. Each level does everything the one below it does, plus more.

LevelWhat it does
NoneNo access to online reports at all. The queue does not appear.
ViewerRead the queue and open a report. Cannot change anything.
TriageWork reports — change status, add notes, assign, accept for dispatch.
SupervisorEverything Triage does, and sees every report rather than only assigned ones.
AdminEverything above, plus configure the intake form, field catalog, incident types and online-reporting settings.
You do not have to use the middle levels

Plenty of agencies run with only None and Supervisor. Start there if you are unsure; add Viewer and Triage when you have a reason.

One agency-wide setting interacts with these: if you set online-report visibility to Records only, then Viewer and Triage no longer reach the queue and only Supervisor and Admin do. That lets you change who handles online reports without re-roling every user.

Section 3

What you fill in — Jurat admin console

Reached from Admin in the left navigation. Work down this list once and most of it never needs touching again.

Agency identity

Agency Information
Agency name, state, logo, letterhead, time zone, case-number format. The logo and letterhead appear on every generated PDF and on the page a victim opens from their link. The time zone decides what every timestamp on screen and on paper says.
Agency Contact
Address, dispatch and records phone, records portal, public hours. These print in document headers.
CJIS
The restricted-system notice shown before sign-in. Two separate fields — a full desktop version and a shortened mobile version — each with its own reset to default.

Victim packet content

This is the section that most changes what a victim actually receives, and the part worth doing carefully before a demo.

Victim Packet Contact Info
The agency block that prints on packet documents.
State Attorney's Office
Judicial circuit, office name, address, victim/witness phone, portal.
Injunction for Protection Filing
Clerk's office, filing address, filing hours, after-hours contact, e-filing portal.
Shelter & Local Crisis Resources
Primary certified shelter and hotline, rape crisis center and hotline.
Victim Packet (document text)
The wording of each document. You can rewrite any of it; the four details above are merged into the text automatically, so filling them in once updates every document that references them.
Two documents are yours to write

Directory of Available Victim Services & Resources and Injunction for Protection (Restraining Order) Information have no Jurat default, because a service directory and a county's filing process are local to you. Until you write them, packets go out without them and the console shows them as Not Included Yet. Everything else ships with Florida-standard text you can edit or reset.

Everything else

Sworn Statement
Oath wording and statement-specific options.
Notification Messages / Messaging Text
The email and text messages sent to affiants and victims. Edit the wording; reset any of it to the Jurat default.
Retention & Records
How long records are kept before they become eligible for purge.
Custom Forms
Build your own forms, group them, and choose which appear in the left navigation for staff.
Integrations
Axon Evidence and related connections.
Users & Roles
Assign both roles per user. See Section 2.
Audit Log
Every recorded action, agency-wide.
Section 4

What you fill in — Online Reporting admin

Reached from Online Reports in the left navigation, then Admin Settings. Requires the Online Reporting Admin role, not the Jurat one.

Intake Page
What a citizen sees when they arrive: your branding, the wording, what you tell them up front.
Incident Types
What a citizen may report online, and the plain-language definition shown under each one. This is where you decide what does and does not belong in online reporting.
Field Catalog
The reusable questions your forms are built from.
Custom Forms / Template Library
The form each incident type presents, and a library of starting points.
Reporting Configuration
Online-reporting behaviour, including who sees the queue (see the Records only note in Section 2).
Notification Emails
What a citizen receives after submitting, and what staff receive when something lands.
Accounts
Online-reporting accounts and teams.
Audit Log
Online-reporting actions.
Configuration Transfer
Move a configuration between environments instead of rebuilding it by hand.
Section 5

Custom forms

Admin → Custom Forms → Forms. Agency forms that are not statements or packets — the vehicle tow & inventory sheet lives here.

Getting a form in

  • ImportChoose File and pick a .zip someone sent you. It arrives inactive, so nothing appears in anyone's sidebar until you have looked at it.
  • Export — produces the same kind of zip, to hand to another agency or to keep as a backup.
  • Check the signers before you activate. Open the form and look at the signer list: who signs, whether they sign in Jurat or by link, and which are Required. A signer wrongly left un-required means the sheet finishes without them.
  • Activate — one click on the row. That is what puts it in officers' sidebars. Deactivate takes it back out without deleting anything.

Removing a form

Remove asks twice. If the form has been used, the second question tells you how many submissions would go with it — those records are deleted too, and that cannot be undone. Deactivate instead if you only want it out of the way.

Correcting a submitted record

An officer's editing ends when they submit. You can still correct a completed record — open it and use Correct record — and every change is written to the audit trail with the old and new values. Answers the form locks at signing (printed names, for example) cannot be changed by anyone.

Section 6

First-day setup order

Do it in this order and nothing blocks on anything else.

  1. Agency — Agency Information: name, state, logo, letterhead, time zone, case-number format.
  2. Contact — Agency Contact and Victim Packet Contact Info.
  3. Banner — Review the CJIS sign-in notice, desktop and mobile.
  4. Local content — State Attorney's Office, Injunction Filing, Shelter & Crisis Resources. These feed the documents automatically.
  5. Write two — Directory of Services and Injunction Information. Nothing else needs writing.
  6. Read one — Open the remaining victim packet documents and read them as your agency, not as a draft. Edit anything that does not sound like you.
  7. Messages — Read the affiant and victim notification text.
  8. Retention — Set your retention period.
  9. Users — Assign both roles for every person. Leave Online Reporting on None for anyone who does not touch it.
  10. Online intake — Incident types first, then the intake page wording, then the forms.
  11. Dry run — Send yourself a statement request and a victim packet. Open both links on a phone. This catches more than any amount of reading.
Before you demo

Step 11 is the one people skip. Send a victim packet to your own phone and walk it end to end — you will see exactly what a victim sees, including the date-of-birth check and the single PDF they download at the end.