01
One shared farm workspace
Every module — records, health, milk, breeding, reminders, team, reports — operates on the same underlying farm and animal data, with no duplicate copies to keep in sync.
Platform
One operating system for the farm, not a folder of separate tools.
Boma connects animal records, health, milk, breeding, reminders, team access, and reporting into a single structured workspace, so the farm runs from one source of truth instead of reconciling several.
Modular
Farms enable the modules they actually use — health, milk, breeding, reminders, and more.
Connected
Every module shares the same animal and farm records instead of duplicating data.
Web and mobile
The same farm workspace is available from the dashboard and the field, in sync.
Platform
Farm Workspace
Every module, one shared record
Records, health, milk, breeding, and team activity all reference the same underlying data, instead of living in separate disconnected tools.
Product screenshot placeholder
What This Feature Does
In plain terms
Platform Overview is the big picture: how Boma’s individual features — animal records, milk operations, health workflows, breeding management, reminders, team permissions, communication, and reporting — fit together as one system instead of a bundle of loosely related tools.
The unifying idea is that a farm has one workspace, and every module operates on the same underlying data. An animal created in Animal Records is the same animal that shows up in a milk entry, a health event, a breeding record, and a report — there is no separate "milk system" with its own copy of the herd that can drift out of sync with the "health system."
Farms enable the modules relevant to their operation. A pure dairy operation might lean heavily on milk and health workflows; a breeding-focused operation leans on breeding management and reminders. The platform adapts to what the farm actually does, rather than forcing every farm through the same fixed set of screens.
Key Capabilities
What you actually get
Each capability below is available today inside Boma, not a roadmap promise. Together they form the working core of this feature.
02
Configurable modules per farm
Farms enable the modules that match their operation, so a farm without a breeding program is not cluttered with breeding screens it does not use.
03
A dashboard that reflects real activity
The farm dashboard surfaces alerts, reminders, recent activity, and key metrics pulled directly from live operational data, not a separately maintained summary.
04
Web and mobile in sync
The same farm workspace is accessible from the web dashboard and the mobile app, with changes made in one reflected in the other.
05
Role-based access across every module
Team permissions apply consistently across the whole platform, so a worker’s access to milk entry matches their access to health logging and reminders.
06
Reporting built from operational data
Because every module shares the same records, reports reflect actual farm activity directly, without a manual export-and-combine step.
07
Multi-farm support for growing operators
Users involved with more than one farm can move between farm workspaces they belong to, each with its own isolated data and team.
Why It Matters
The operational cost this feature actually removes
The alternative to one connected platform is usually a patchwork: a spreadsheet for records, a messaging app for coordination, a separate app for milk, and someone’s memory for health history. Each tool works fine in isolation, but nothing talks to anything else, and keeping them consistent becomes its own job.
Boma’s value compounds because the modules are connected. A reminder about a vaccination links to the actual animal record. A milk entry contributes to both the animal’s history and the farm’s production trend. A health event shows up in reporting without anyone re-entering it. The platform gets more useful as more of the farm’s work happens inside it, instead of each new tool adding another reconciliation burden.
No reconciliation between disconnected tools
One record per animal means nothing has to be manually kept in sync across separate systems.
New modules add value instead of overhead
Enabling health tracking or breeding management builds on records that already exist, rather than starting from zero.
Consistent access rules everywhere
A team member’s role applies the same way across every module, with no separate permission system to configure per tool.
A platform that grows with the operation
Farms can enable more modules as they need them, without migrating to a different system.
Use Cases By Role
How each person on the farm actually uses this
Boma is built around real farm roles. Here is how this feature shows up differently depending on who is signed in.
Owner
Runs the whole operation from one dashboard
An owner opens a single dashboard and sees herd status, recent activity, and outstanding reminders across every module the farm uses, instead of checking several separate tools.
Manager
Coordinates across modules without extra tools
A manager assigning a reminder about a specific animal is working with the same record a worker will use to log the resulting health check, with no handoff friction between systems.
Worker
Uses one login for every part of the job
A worker logging milk, health checks, and reminders in the same shift does it all from one app, with one login, rather than switching between separate tools for each task.
Vet
Sees the whole animal, not just the clinical slice
A vet reviewing an animal’s health can also see recent breeding and milk activity on the same profile, which is often relevant context a standalone clinical tool would miss.
Admin
Supports farms with different module needs
A platform admin can see which modules each tenant has enabled and tailor onboarding support to the parts of the platform that farm actually relies on.
How It Works
Step by step, in practice
A farm’s relationship with the platform typically deepens in a predictable way.
- 1
The farm is created with a core workspace
Animal records and team access form the foundation every farm starts with.
- 2
Modules are enabled to match operations
Health tracking, milk operations, breeding management, and reminders are turned on as they become relevant.
- 3
Daily work happens across connected modules
Entries in one module build on records shared with every other module, rather than existing in isolation.
- 4
The dashboard reflects the whole picture
As data accumulates, the dashboard and reports become a more complete and useful view of the operation.
- 5
The platform scales with the farm
More team members, more modules, and more history all build on the same structure without requiring a system change.
Data & Control
Who can see it, who can change it, and who is accountable for it
Every farm’s workspace is isolated at the database level, so enabling more modules never exposes data to another tenant. A farm’s decision to turn on breeding management, for example, only affects that farm’s own workspace.
Access control is consistent across modules because it is enforced by the same underlying role system everywhere, rather than each module implementing its own separate permission logic that could drift out of alignment with the rest of the platform.
Farm-level data isolation
Every module respects the same farm boundary, enforced at the database layer.
One permission system, every module
Role-based access applies consistently rather than being reimplemented per feature.
Modules are additive, not disruptive
Enabling a new module builds on existing records instead of requiring a data migration.
Consistent web and mobile behavior
The same access rules and data apply whether the farm is being used from a browser or the mobile app.
Business Outcomes
What changes operationally once this is in place
These are the practical shifts farms describe once the feature is part of daily use, not a marketing estimate.
One source of truth for the whole farm
Records stop drifting apart because there is only one copy of the data to begin with.
Less time spent reconciling tools
Nobody has to manually keep a spreadsheet, a chat app, and a records system consistent with each other.
Smoother growth into new workflows
Enabling a new module builds on what already exists instead of starting over.
A dashboard that means something
Because it reflects live operational data, the dashboard is a working tool, not a static summary.
Questions
Common questions about this feature
Specific answers for teams evaluating whether this part of Boma fits how the farm actually runs.
Do we have to use every module Boma offers?
No. Farms enable the modules relevant to their operation. A farm without a breeding program simply does not turn on breeding management, and its workspace stays focused on what it actually uses.
Can we start with fewer modules and add more later?
Yes. Enabling a new module later builds on existing animal and farm records rather than requiring a fresh setup or data migration.
Is the mobile experience a separate, lighter product?
No. The mobile app connects to the same farm workspace as the web dashboard. Actions taken on mobile are reflected on the web and vice versa.
Can one person be involved with more than one farm?
Yes. A user can hold memberships on multiple farms, each with its own role and isolated data, and switch between the farms they belong to.
How does the platform stay simple if it does this much?
Each module has a focused job, and the shared data model means adding a module does not multiply complexity — it reuses records that already exist rather than introducing a parallel system.
Related Features
Works alongside the rest of the platform
Ready To Try It
See the whole platform, not just one feature.
Start free and enable the modules that match how your farm actually operates.