01
Full tenant lifecycle management
Onboard a new farm with its owner and initial subscription in one flow, and manage that farm’s status for as long as it remains a customer.
Platform Admin
Run the platform, not just one farm.
Boma’s admin layer gives platform operators tenant onboarding, subscription management, suspension controls, and platform-wide activity visibility, separate from and above any individual farm’s workspace.
System-level role
Platform admin access is a distinct role, not an elevated farm permission.
Full tenant lifecycle
Onboard, suspend, reactivate, and manage subscriptions for any farm on the platform.
Logged, not silent
Administrative actions are recorded in a system activity log for accountability.
Platform Admin
Admin Dashboard
Every tenant, one control layer
Farms, users, and subscriptions across the platform are visible and manageable from a dedicated admin workspace, separate from any farm’s own dashboard.
Product screenshot placeholder
What This Feature Does
In plain terms
Admin Controls is the layer that sits above individual farms — it is how the people operating the Boma platform itself manage tenants, not how any one farm manages its own team. A user with the system admin role can see every farm, every user account, and every subscription across the platform, and act on any of them without needing to be a member of the farm in question.
This includes the full tenant lifecycle: onboarding a new farm and its owner, managing subscription plans and billing status, suspending a farm or an individual user when necessary, and reactivating access once an issue is resolved. It also includes platform-wide visibility — recent signups, recent farm creation, and system activity — so operators are not flying blind about what is happening across the customer base.
Every meaningful administrative action is recorded, so "who suspended this farm and when" or "who changed this subscription" has a real answer instead of relying on someone remembering.
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
Subscription and billing oversight
View and update subscription plan, status, trial periods, and billing notes for any farm, with changes reflected immediately in what that farm can access.
03
Suspension controls at farm and user level
Suspend an individual user, an entire farm, or a specific membership independently, giving precise control instead of an all-or-nothing switch.
04
Platform-wide dashboard
See total users, total farms, active and expired subscriptions, and recent signups and farm creation from a single admin view.
05
System activity logging
Administrative actions — tenant creation, suspensions, subscription changes — are recorded with the acting admin, entity, and timestamp for later review.
06
Platform-wide messaging
Send targeted or broadcast messages to individual users, specific farms, or the whole platform directly from the admin layer.
07
Support inbox for tenant conversations
Respond to support conversations raised by any farm on the platform, with the ability to mark threads resolved and track response activity.
08
Operational health monitoring
Surface suspended farms, suspended users, expired subscriptions, and other signals that need admin attention in one operational health view.
Why It Matters
The operational cost this feature actually removes
Running a multi-tenant SaaS product without a dedicated admin layer means every operational task — onboarding a customer, handling a billing issue, responding to a support request — becomes a manual, ad hoc process, usually involving someone with database access doing something by hand. That does not scale past a handful of customers, and it is risky even at small scale.
Boma’s admin controls exist so platform operators can run the business side of the SaaS product with the same structure farms get for their operations. Tenant management, billing status, suspensions, and support all live in one place, with a record of who did what, so the platform itself is as accountable as the farms using it.
Customer onboarding that does not require engineering
New tenants can be set up through the admin interface, not a manual database script.
Fast response to billing and access issues
Subscription and suspension changes take effect immediately, without a deployment or support ticket to engineering.
A real audit trail for administrative actions
System activity logging means sensitive actions like suspensions are traceable, not silent.
One place to see platform health
Operators can spot expired subscriptions or suspended accounts needing attention without querying the database directly.
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.
Admin
Onboards a new farm from a single flow
A platform admin creates a new tenant — farm, owner account, and initial subscription — in one guided flow instead of several disconnected manual steps.
Admin
Resolves a billing dispute
When a farm’s payment fails and needs a grace period, an admin can adjust the subscription status directly, with the change logged for later reference.
Owner
Experiences the effect of admin changes seamlessly
A farm owner whose subscription is reactivated by an admin regains full access immediately, without needing to re-authenticate or contact support again.
Manager
Reports an issue through the support inbox
A manager with a platform question sends a support message that lands directly in the admin support inbox, rather than an external email that is easy to lose track of.
Admin
Investigates unusual account activity
An admin reviewing the system activity log can see recent suspensions, subscription changes, and tenant creation events to understand what has happened across the platform recently.
How It Works
Step by step, in practice
Platform administration follows a structured path from tenant onboarding through ongoing account management.
- 1
A new customer is onboarded as a tenant
An admin creates the farm, its owner account, and its initial subscription in one connected flow.
- 2
The farm operates independently
Day-to-day operations happen entirely within the farm’s own workspace, with no ongoing admin involvement required.
- 3
Admin visibility continues in the background
The farm’s subscription status, activity, and any support requests remain visible to platform admins without interrupting the farm’s work.
- 4
Admins act when something needs attention
A billing issue, a suspension request, or a support conversation is handled directly through the admin layer.
- 5
Every administrative action is recorded
Changes made by admins are logged with who made them and when, supporting accountability across the platform.
Data & Control
Who can see it, who can change it, and who is accountable for it
System admin access is a distinct platform-level role, separate from any farm’s owner or manager role. Holding admin access does not make someone a member of every farm — it grants a specific, elevated capability to manage tenants, which is enforced the same way farm-level permissions are: at the database layer, not just in the interface.
Administrative actions that affect a farm’s access or billing — suspensions, subscription changes, tenant creation — are written to a system activity log with the acting admin, the affected entity, and a timestamp, so platform operations remain auditable even as the customer base grows.
Distinct system admin role
Platform admin access is separate from farm membership roles, not an elevated version of them.
Database-enforced admin boundary
Only accounts explicitly granted the system admin role can perform platform-level actions.
System activity logging
Sensitive administrative actions are recorded with actor, entity, and timestamp.
Independent suspension levers
Users, memberships, and farms can each be suspended independently for precise control.
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.
Faster customer onboarding
New tenants can be set up in minutes through the admin interface, not a manual engineering task.
Cleaner billing operations
Subscription changes and grace periods are handled directly, without waiting on a deploy.
Real accountability for admin actions
Every meaningful platform action is logged, not left to memory or informal notes.
Proactive platform health monitoring
Suspended accounts and expired subscriptions surface before they become customer complaints.
Questions
Common questions about this feature
Specific answers for teams evaluating whether this part of Boma fits how the farm actually runs.
Is admin access the same as being a farm owner?
No. System admin is a separate platform-level role. An admin can manage any farm’s tenant status and subscription without being a member of that farm’s own team.
Can admin actions be undone or traced later?
Administrative actions like suspensions and subscription changes are recorded in a system activity log with the acting admin and timestamp, so they can be reviewed after the fact.
What happens to a farm’s data when it is suspended?
Suspension restricts access rather than deleting data. Farm records remain intact and become accessible again once the suspension is lifted.
Can I have more than one platform admin?
Yes. Multiple accounts can hold the system admin role, which is appropriate for teams operating Boma at scale with more than one person handling platform operations.
How is admin support different from a farm’s internal team messaging?
The admin support inbox is for conversations between a farm and the platform operator, separate from a farm’s internal team chat, which stays private to that farm’s own members.
Related Features
Works alongside the rest of the platform
Ready To Try It
Run your farms platform like a real SaaS business.
Talk to us about onboarding your operation, or see how pricing scales with the number of tenants you manage.