Docs / Authority / Jurisdictions

Authority · Customer guide

Jurisdictions

There are two pages called Jurisdictions in the Authority experience — one is history, the other is where you actually manage scope today. This guide is here so you never confuse the two.

Audience: state vets, Authority admins Part of the Authority guide set

What this guide covers: why there are two "Jurisdictions" menu items, what each one is actually for, and how to create or change a jurisdiction today.

Legacy view

Command Centre → Jurisdictions (legacy, read-only)

This page is history, not a place to manage anything. It shows pre-canonical jurisdiction rows that still use free-text province/district/municipality codes, predating the canonical geography model. The page says so directly: new jurisdictions can no longer be created or edited here. Use it only to look up an old record — filter by institution, scope level, or active/inactive — never to make a change.
Canonical register

Administration → Jurisdictions (canonical, live)

This is the real jurisdiction register — every write here targets a canonical administrative area, never a free-text code. It keeps three concepts strictly separate:

  • Institution mandate — a jurisdiction row with no specific officer attached; it covers the whole institution.
  • Direct user jurisdiction — a row assigned to one named officer specifically.
  • Your own administration boundary — the ceiling on what you personally are allowed to assign, enforced by the server regardless of what the screen shows you.

The table shows Institution, who it's assigned to (a chip reads "Institution mandate" if unassigned), scope, the area breadcrumb (with a "Legacy" chip if it was migrated from the old model), effective dates, and status.

Creating a jurisdiction

Creating a jurisdiction

  1. Click New Jurisdiction.
  2. Pick the institution, and optionally a specific officer to assign it to directly.
  3. Pick a scope level, then the matching target — an administrative area (province, district, municipality) for area-based scopes, or an organisation/holding/biosecurity-zone id for those scopes.
  4. Add any species or disease limitation, and effective dates.
  5. Click Preview Impact — this renders a map of the actual area, and shows affected organisations and holdings, how many are already geography-verified versus unresolved, warnings, and any overlap with existing jurisdictions.
  6. Save is disabled until the preview comes back allowed.

Click any row to open its detail dialog, which includes a Deactivate action — a reason is required.