What this guide covers: what the Authority persona sees when they log into Agribantu, how their account, institution and jurisdiction get set up, and how an organisation's farm data actually becomes visible to them in the first place.
What it doesn't cover: a detailed walkthrough of any one page — every page now has its own dedicated guide, linked from Parts 5 and 6 below, starting with FMD Quarantine Recovery Pathway.
1. AudienceWho this is for
The Authority persona is for people acting in an official regulatory capacity — a State Veterinarian, a Provincial Director: Veterinary Services, or another DALRRD-mandated official — rather than for farm owners or their staff. It's a separate login experience: an Authority user sees a completely different navigation menu (the Authority Command Centre) scoped to their jurisdiction, not a farm's own LITS, Finance or HR modules.
This page is also for the org owners and admins who control how much of their own farm's data an Authority user can see, and for whoever administers your Agribantu deployment and needs to set up a new institution or state-vet account.
2. OverviewWhat the Command Centre is
Everything an Authority user sees is jurisdiction-scoped: they only ever see holdings, animals, movements and events that fall inside the geographic or organisational scope they've actually been assigned — never the whole platform. Most pages are read-only by design; a handful of write actions exist (inspections, permits, quarantine sign-off follow-ups, outbreak notifications), and every one of them is individually audited.
The landing page is the National Livestock Traceability Command Centre — a jurisdiction-wide view of livestock identity, movement, biosecurity risk and regulatory readiness, aligned to the Red Meat Industry Services (RMIS) national traceability framework.
3. ProvisioningSetting up an Authority account
Three things sit underneath every Authority login, in a strict hierarchy:
- Institution — the organisation the Authority user belongs to (e.g. a specific State Veterinary Office). Every Authority user belongs to exactly one institution.
- Authority user — the individual (name, email, a descriptive role like "officer" or "state vet"), linked to their institution. An Authority user record can exist as a pure directory entry — for example, as the named recipient of a private-vaccination notice — even before it's linked to an actual Agribantu login.
- Jurisdiction — the actual geographic or organisational scope granted: country, province, district, municipality, biosecurity zone, a single holding, or a single organisation (owner-granted).
- Institutions & Offices has a Create Institution dialog — name, official name, type, parent office (for a scoped tree), a code, and contact details. Existing institutions can also be reparented into a different part of the tree, with a preview of the effect before it's confirmed.
- Authority Users has a seven-step provisioning wizard: the officer's name and email, their institution, their role, an optional jurisdiction to assign immediately, whether to send them a login invitation on the spot, and an optional link to (or creation of) a veterinary contact record.
Jurisdiction assignment is no longer institution-only either: the Jurisdictions page (Part 6) can target the whole institution's mandate or one specific officer directly, using a canonical province/district/municipality (or holding, organisation, or biosecurity zone) rather than the old free-text codes — with a geography impact preview and map before anything is saved.
4. AccessAccess policies & grants — how your data becomes visible
A jurisdiction alone doesn't automatically make every farm's data visible — an access basis has to justify it, and it's always one of these:
| Access basis | What it means |
|---|---|
| Statutory Authority | Derives directly from the Animal Diseases Act 35/1984 or subordinate legislation. |
| Scheme Participation | Granted because the organisation participates in an approved scheme — e.g. the Section 10 Routine Vaccination Scheme. |
| Owner-Granted | Voluntarily granted by the organisation's own owner or admin — this is the "Authority Grants" screen org admins see. |
| Emergency Access | Elevated access invoked during a declared disease emergency. |
| Read-Only Observer | Observer-level access — no write permissions or inspection rights. |
Every access policy also declares which actions it allows (view LITS data, view evidence, inspect, request a correction, approve a permit, generate a report, export a data pack, manage policy) and how much evidence it exposes (none, metadata only, or full download) — all managed from the Policies page's Access Policies and Authority Grants tabs.
5. Page tourA tour of the Command Centre
Fourteen pages make up the Command Centre today — the jurisdiction-scoped, mostly read-only side of the Authority experience. Every page below now has its own detailed guide. A separate group of institution-administration pages (who has what role, position or jurisdiction) is covered next, in Part 6, and External Access — the fifteenth nav item — is a shared surface documented once, in External Access Portal.
The landing dashboard — a jurisdiction-wide view of livestock identity, movement, biosecurity risk and regulatory readiness in one place.
A legacy, read-only view of pre-canonical jurisdiction rows — kept for history only. Live jurisdiction management now happens on the Administration side (Part 6) — see the dedicated Jurisdictions guide, which explains both pages clearly.
Every farm, abattoir, auction house, feedlot and border post participating in national traceability must hold a verified GS1 Global Location Number — this registry tracks that identity from registration through amendment to retirement. See the dedicated Locations guide.
A read-only, jurisdiction-scoped view of every registered holding — farm, feedlot, abattoir, auction house or communal area — linked to its responsible organisation and GLN. See the dedicated Holdings guide.
Read-only visibility into every animal in scope — identity, identifiers, species/breed and lifecycle status — for disease surveillance, movement tracing and compliance auditing. See the dedicated Animals guide.
Pending approvals, in-transit consignments, FMD quarantine day-counters and permit validity, all from one jurisdiction-scoped registry. See the dedicated Movements & Permit Control guide.
Tracks every vaccination event, herd-immunity progression toward the 80% threshold, cold-chain compliance, and reconciles state-administered against court-authorised private vaccinations. Its newer FMD Campaigns tab oversees private vaccination campaigns end to end — see the dedicated FMD Vaccination Surveillance & Private Campaigns guide.
Every active and lifted quarantine in your jurisdiction, with the Day 0 / Day 16 / Day 42 / 16-month recovery pathway tracked automatically — see the dedicated Quarantine Recovery Pathway guide.
Suspected and confirmed disease reports flowing in from farms, with status tracking through to government export. See the dedicated Disease Reports guide.
Covers all five inspection regimes — routine herd surveillance, auction pre-screening, abattoir assessments, quarantine follow-up (two negative inspections to lift a quarantine), and movement compliance checks. See the dedicated Inspections guide.
Digital FMD notices and affidavits submitted by farmers flow in here for review, acknowledgement and escalation — the Authority-side counterpart to an org's own submission drawer. See the dedicated Regulatory Inbox guide.
Generates disease, vaccination, traceability, geofence, outbreak and engine-driven reports for submission to DALRRD and the World Organisation for Animal Health (WOAH). See the dedicated Reports guide.
Three tabs: the National Framework (the regulatory schemes and directives this whole module is built against), Access Policies (Part 4), and Authority Grants (Part 4). Org admins reach the Grants tab under their own "Authority Grants" menu item. See the dedicated Policies guide.
Validates readiness, detects schema gaps, and publishes jurisdiction-wide data packs in the ICAR Animal Data Exchange (ADE) JSON format, with a traceable evidence history per export run. See the dedicated ICAR/ADE Export guide.
Authority Administration
A separate section in the left nav from the Command Centre above — that one is jurisdiction-scoped operational LITS access, this one is institution administration: who has what role, position or jurisdiction. It's gated on narrower per-action scopes rather than the broad read-jurisdiction scope every Authority persona already holds, so most officers will see a smaller slice of it than the Command Centre.
The administration area's own landing page — a summary of institutions, users and pending provisioning in your scope.
A scoped tree of institutions (your own administration subtree only, unless you're a platform super admin), per-node counts, a Create Institution dialog, and a reparent action with a preview of the effect before it's confirmed. See the dedicated Institutions & Offices guide.
A proper register — lifecycle and account state as two separate fields, an Effective Access drawer that keeps institution mandate distinct from an officer's own direct jurisdictions, role changes with a before/after scope diff, and the seven-step provisioning wizard (Part 3). See the dedicated Authority Users guide.
A read-only catalogue — rank, classification, grantable roles and compatible position types. There's no custom role editor. See the dedicated Roles & Permissions guide.
Positions and acting appointments, with an occupancy timeline. Standing responsibility belongs to a post, not whoever currently occupies it — assigning a person directly, bypassing a post, is treated as an explicit emergency exception. See the dedicated Positions guide.
Routing health for each service area, a conflict preview before you create or edit one, and a report-only routing-impact preview — it shows which verified holdings would be affected, it never touches a manual override. See the dedicated Veterinary Service Areas guide.
The canonical jurisdiction admin described in Part 3 — assigns institution mandates or direct officer jurisdictions against real administrative areas, with a geography impact preview and a map showing the actual boundary (or an honest "no polygon available" message, never a guess). See the dedicated Jurisdictions guide.
A register that distinguishes a usable login from mere contact existence, with a retirement flow (contacts are retired, never deleted) that shows historical reference counts first. See the dedicated Contact Directory guide.
A boundary-scoped register and detail view of who accessed what — and viewing a detail record is itself an audited action. See the dedicated Access Audit guide.
Platform-admin only. Shows enforcement mode across environment capability, tenant configuration and effective state, and treats disabling enforcement as an explicit security-sensitive rollback rather than a harmless reset. See the dedicated Tenant Enforcement guide.
A personal, fail-closed dashboard of an officer's own direct jurisdiction. An officer with no direct jurisdiction of their own sees an explicit empty state — never institution-wide data as a silent fallback. See the dedicated My Jurisdiction guide.
What's live today
| What | Status |
|---|---|
| All fourteen Command Centre pages listed in Part 5 | Live |
| All eleven Authority Administration pages listed in Part 6 | Live |
| Creating and editing access policies | Live — Policies page, Access Policies tab |
| Granting a specific Authority user access to your org's data (owner-granted) | Live — Policies page, Authority Grants tab (also reachable from org admin's "Authority Grants" menu item) |
| Registering a brand-new Authority institution | Live — Institutions & Offices page, gated to the administration capability |
| Provisioning a brand-new individual Authority user | Live — Authority Users page, seven-step wizard, same gating |
| Assigning jurisdiction scope to one specific Authority user rather than their whole institution | Live — Jurisdictions page |
| An officer whose platform login predates their Authority role reaching Authority routes automatically | Known limitation — accepting the invitation doesn't yet transition their platform role; deferred as a named follow-up, not silently routed around |
Questions people ask
I'm a state vet — how do I get an Agribantu login?
There's still no public sign-up for the Authority persona, but it no longer has to go through whoever administers your Agribantu deployment. Anyone at your institution who holds the administration capability can provision you directly, from the Authority Users page's provisioning wizard (Part 3) — including sending your login invitation on the spot. Ask them to set this up for you.
As a farm owner, can I control what an Authority user sees?
Partly. Statutory and scheme-participation access exist independently of you — they follow the law and any scheme you're already enrolled in. What you do control is owner-granted access: voluntarily giving a specific Authority user a scoped view of your organisation, from your "Authority Grants" screen.
Can an Authority user edit my farm's records?
Most Command Centre pages are read-only by design. Where write actions exist — inspections, permits, quarantine follow-ups, outbreak notifications — they're scoped to that specific action, never a general edit right over your data, and every one is audited.
Does one Authority user see every farm in the country?
No — only what their assigned jurisdiction covers. A district-level officer sees that district; a national official with country-level scope sees the whole country. Scope is set on the Jurisdictions page.
This is an overview, not the full manual — but every page listed above now has its own detailed guide, linked in place.