Agriculture — Overview

The Agriculture add-on: fields, crop recipes, target harvests and agronomic SOPs.

Module Overview

The Agriculture add-on (package id agriculture, domain AGRICULTURE) is a wired, purchasable package gated by a tenant entitlement and per-user Agriculture roles.

At a glanceDomain: AGRICULTURE
URL prefix: /agriculture/…
Governance screens: Roles, Farm Workforce (staff)
Operational master data: Fields & Greenhouses, Crop Recipes, Target Harvests, Agronomic SOPs

Capabilities

Agriculture ships with 6 out-of-the-box capabilities. Approver capabilities carry sign-off authority.

Capability	Purpose	Approver
agri:field:manage	Manage fields
agri:crop_plan:manage	Manage crop plans
agri:task:execute	Execute field tasks
agri:input:apply	Apply inputs
agri:harvest:record	Record harvests
agri:quality:certify	Certify quality	Yes

Secure Farm Data & Field Sharing

Beyond field, crop and harvest operations, the add-on protects the records they rely on: encrypted, role-based access to certificates, crop recipes and lab results, watermarking and audit trails, secure mobile access from greenhouses and fields, IT-OT data sharing for sensor and machine data, and OTP-protected, approved sharing with buyers, agronomists and auditors. See Secure Farm Data & Field Sharing.

Pages in this section

Frequently Asked Questions

What do I need to use the Agriculture add-on?

The tenant must have the Agriculture package activated, and your user must hold a Agriculture domain role. See Domain Roles & Capabilities.

Can a Agriculture user see other add-ons’ data?

No. A Agriculture role exposes only AGRICULTURE and GLOBAL capabilities.

Where is this add-on’s data stored?

Under the tenant’s per-module folder on the server (roles in roles/roles.json).

Is it available out of the box?

Agriculture is a wired package — its screens exist today; a tenant admin just activates it.