🔍 Farm and Vendor User Role Overview¶

When users log in to HortiView, the platform creates a cryptographic token with their permissions based on roles. This token is checked for every user action.

See detailed rights matrix here

Farm Manager¶

Primary farmer responsible for managing their farm day-to-day with full operational control over a farm.

• Can view, create, and update:
  • Fields
  • Blocks
  • Irrigation stations
  • Seasons
  • IoT devices and alert settings
  • Farm users of the application
• Cannot manage:
  • Organization-level settings
  • Billing
  • (Un-)subscribe modules from marketplace (requires additional Admin flag)
• Can view:
  • Organization info (name, address, VAT number, primary and secondary contact)
  • Farm org member information
  • Platform legal information

Agronomist¶

Internal agronomy experts who support farm operations with technical input.

• Can read and partly create/update:
  • Fields
  • Blocks
  • Seasons
  • Irrigation stations
  • IoT devices and alerts
• No access to:
  • Billing
  • User management
  • Marketplace
• Can view members of farm locations they are assigned to.

Farm Worker¶

On-the-ground workers with limited rights for operational support.

• Can view:
  • Assigned farm locations
  • Fields
  • Blocks
  • Irrigation stations
  • Seasons
  • Devices and alert rules
• Can create:
  • Scouting Incidents
  • Crop Health data entries
• No access to:
  • Structural changes on farm
  • Billing
  • Organization-level settings
  • User management

(External) Advisor¶

External consultants or advisors with visibility but no operational control.

• Can view:
  • Farms
  • Fields
  • Blocks
  • Alerts
  • Seasons
• Can fully manage Alerts.
• No access to:
  • Farm organizational information
  • User management

Organizational Admin Flag¶

Can be added to all roles. It is initially set to the farm owner when first time registering a new farm organization on HortiView. The farm owner can delegate the full administrative responsibility to one or many other farm members.

• Purpose: Enable a digitally skilled individual on the farm to handle administrative tasks.
• Grants permission to manage:
  • HortiView account
  • Organizational details
  • User management
  • Marketplace access
  • Billing information
• Farm owners can delegate these responsibilities to any user by setting the additional flag in the user management.

Role-Based Access Permissions Overview¶

Each column represents a key functional area.

Vendor Manager¶

• Primary vendor manager for Hortiview account.
• Manages vendor organization details and users.

Flagged Vendor Admin¶

• This flag allows a user to manage the HortiView vendor account, including organization details, user access, marketplace features, and billing.
• A vendor manager may hold or delegate admin privileges to another team member, such as a product manager.

Product Manager¶

• Defines module requirements.
• Oversees marketplace information and settings.
• Manages release and publication.
• Tests the module.

Lead Engineer¶

• Responsible for developing new modules and ensuring that all technical information is accurately documented in HortiView.
• In the absence of a designated Product Manager, may assume all responsibilities typically assigned to that role by seeting the Admin-flag.
• Accountable for thoroughly testing each module.

Engineer¶

• Responsible for developing new modules and supplying technical documentation to HortiView prior to publication.
• Accountable for thoroughly testing the module.

Role Matrix¶