01
Five purpose-built roles
Owner, manager, worker, vet, and viewer roles map to real farm responsibilities, from full administrative control down to read-only visibility.
Team & Access
Give people the access their job needs, and nothing they don’t.
Boma’s role system lets the farm owner decide exactly what each team member can see and do, from a worker who logs field entries to a vet who reviews history, without anyone having to share a single shared login.
Five roles
Owner, manager, worker, vet, and viewer — matched to how farms actually operate.
Admin-led
Only the owner or manager can add, remove, or change access for team members.
Enforced, not suggested
Permissions are checked at the database level, not just hidden in the interface.
Team & Access
Team Roster
Five roles, one clear structure
Owner, manager, worker, vet, and viewer roles map to real farm responsibilities, each with a defined and enforced set of permissions.
Product screenshot placeholder
What This Feature Does
In plain terms
Team Permissions is how Boma controls who can do what on a farm. Rather than every signed-in user having the same access, each person is assigned one of five roles — owner, manager, worker, vet, or viewer — and that role determines what they can see, create, edit, or approve across every module in the platform.
Access is admin-led: the farm owner or a manager decides who joins the workspace, what role they hold, and when that access should be revoked. Nobody grants themselves elevated access, and nobody ends up with permanent access to a farm they left months ago without someone explicitly removing it.
Because permission checks happen at the database level through row-level security, not just by hiding buttons in the interface, a worker cannot perform a manager-only action even by calling the underlying data directly. The role system is a real security boundary, not a cosmetic one.
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
Admin-controlled invitations
Owners and managers invite team members directly, with the new member landing in the correct role from the start rather than needing a follow-up permission fix.
03
Suspension and removal
Access can be suspended or removed the moment it is no longer appropriate, whether a worker leaves or a temporary vet engagement ends.
04
Role changes without losing history
Promoting a worker to manager, or adjusting any role, updates their access immediately without disturbing the history of entries they already made.
05
Database-level enforcement
Permissions are enforced through row-level security at the data layer, so access boundaries hold even if a request bypasses the visible interface.
06
Viewer role for oversight without editing
Stakeholders who need visibility but should never modify records — investors, consultants, or family members — can be given read-only access.
07
Per-farm membership
A person managing multiple properties can hold different roles on different farms, with access strictly scoped to each one individually.
Why It Matters
The operational cost this feature actually removes
Shared logins and undifferentiated access are common on smaller operations because setting up "real" permissions has historically felt like more overhead than it was worth. But the cost shows up later: a worker who accidentally changes a record they should only be able to view, a former employee whose access was never revoked, or simply not knowing who made a change because everyone logs in as the same account.
Boma makes role-based access the default, not an enterprise add-on. Setting a worker up correctly takes the same effort as adding them with no restrictions at all, which means farms get the accountability benefits without paying an administrative tax for them.
No more shared logins
Every action is attributed to a real person, because every person has their own account and role.
Access matches responsibility
A worker gets field-entry access; a manager gets oversight and approval; a vet gets what a clinical visit actually requires.
Departing staff lose access immediately
Removing or suspending a member takes effect right away, closing a common security gap.
Confidence when the team grows
Adding the fifth or fifteenth team member does not require rethinking how access works.
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
Sets the access structure for the whole farm
The owner decides who has access at all, assigns the initial roles, and retains ultimate control over the farm’s membership and permission structure.
Manager
Handles day-to-day team administration
A manager can invite new workers, adjust roles as responsibilities shift, and suspend access when someone leaves, without needing the owner involved in every change.
Worker
Works confidently within a defined scope
A worker has exactly the access needed to log field activity and complete assigned tasks, without visibility into administrative or financial areas that are not part of their job.
Vet
Gets scoped access for the length of an engagement
A vet working with the farm is added with the vet role, giving relevant record access for their involvement, and can be removed cleanly once the engagement ends.
Admin
Supports role setup during onboarding
A platform admin helping a new tenant get started can confirm the farm’s role structure is set up sensibly and matches how their team actually operates.
How It Works
Step by step, in practice
Setting up and maintaining team access follows a simple, repeatable process.
- 1
Owner or manager sends an invitation
A new team member is invited with a specific role already assigned, so there is no ambiguous "figure it out later" access period.
- 2
The invitee joins with role-appropriate access
From their first login, the new member sees exactly what their role allows — nothing more, nothing less.
- 3
Roles adjust as responsibilities change
Promotions, added responsibilities, or scope changes are reflected with a role update, applied immediately.
- 4
Access is suspended or removed when appropriate
Whether someone leaves the farm or a temporary engagement ends, access is closed off deliberately rather than left open by default.
- 5
History remains intact regardless of current access
Entries made by a former team member stay attributed and visible in the record, even after their access is removed.
Data & Control
Who can see it, who can change it, and who is accountable for it
Every permission check in Boma happens against the database, not just the interface. That means role boundaries hold even for direct data requests, not only for what buttons happen to be visible on a screen — a meaningful difference between "permissions" as a UI convenience and permissions as an actual security boundary.
Membership and role assignment are themselves controlled actions: only owners and managers can add, change, or remove team members, which keeps the "who decides who has access" question answerable at all times.
Row-level security enforcement
Access boundaries are enforced at the database layer, not only hidden in the interface.
Admin-only membership control
Only owners and managers can invite, change, or remove team members.
Immediate effect on change
Role changes and access removal apply right away, without a delay or manual sync step.
Attribution independent of current access
Past actions stay correctly attributed even after a user’s access is later changed or revoked.
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.
Real accountability
Every action is tied to the person who took it, not a shared account everyone logs into.
Closed access gaps
Departing staff and ended engagements stop having access the moment it is revoked.
Confidence adding new people
Growing the team does not require rethinking how access and oversight work.
Oversight without micromanagement
Owners get visibility through the viewer and manager roles without needing to gate every entry personally.
Questions
Common questions about this feature
Specific answers for teams evaluating whether this part of Boma fits how the farm actually runs.
What is the difference between a manager and a worker role?
Managers can administer team membership, oversee broader farm operations, and typically approve or adjust records, while workers are scoped to logging field activity like health checks, milk entries, and reminders within their assigned farm.
Can one person have different roles on different farms?
Yes. Roles are assigned per farm membership, so someone consulting for multiple operations can hold a manager role on one farm and a vet role on another.
What happens to a worker’s past entries if they are removed from the farm?
Their historical entries remain in the record, correctly attributed to them, even though their active access to the farm has been removed.
Is there a role for someone who should only view data, like an investor?
Yes, the viewer role provides read-only access, giving oversight without the ability to create or modify records.
Can a worker accidentally get manager-level access through the app?
No. Permission checks are enforced at the database level, so a worker’s access is bounded by their assigned role regardless of how a request reaches the system.
Related Features
Works alongside the rest of the platform
Ready To Try It
Give your team the exact access their role requires.
Start free and set up role-based access that actually holds, not just a permissions checklist.