Why Team Access Is Not Optional at Commercial Scale
A beekeeper managing 10 hives alone can keep everything in their head. A commercial operation with 150–380 hives across three or four apiaries cannot. At that scale, the operation runs on people — field technicians who do the inspections, a business partner who monitors costs, seasonal helpers who assist during peak harvest. Each person needs access to the right information, and no one should have access to information they do not need.
The failure mode without structured team access is predictable: a shared login that everyone knows, inspection records that get entered inconsistently, financial data visible to people who should not see it, and no accountability for who did what. SunnyBee's team system is designed to eliminate this.
The Three-Role System: ADMIN, MODERATOR, VIEWER
SunnyBee uses three permission levels, each mapped to a realistic role in a commercial beekeeping operation:
ADMIN has full access to the apiary: create and edit hives, log inspections, record treatments and harvests, manage expenses, add or remove team members, and view all financial data. In a typical operation, the owner holds ADMIN on all apiaries.
MODERATOR can do all the operational work — log inspections, record treatments and feeding, update hive status, complete tasks — but cannot manage team membership or access financial summaries. This is the right level for a trusted field technician: they can do everything needed in the apiary without touching business-side data.
VIEWER has read-only access: they can see hive status, inspection history, task lists, and colony health but cannot create or edit any records. This is appropriate for a business partner or investor who needs visibility into operations without the ability to change anything.
Per-Apiary Roles: One Person, Different Access on Different Sites
The critical design feature in SunnyBee's team system is that roles are assigned per apiary, not per account. A single team member can have MODERATOR access on Apiary A (where they work regularly) and VIEWER access on Apiary B (where they occasionally assist), with no access at all to Apiary C (a site they are not involved with).
This matters in practice. A field technician who covers one of your three sites does not need to see the inspection history or hive list of the other two. A seasonal helper brought in for harvest at one location has no reason to access your other apiaries. Per-apiary roles enforce these boundaries without requiring separate accounts or complex workarounds.
From the owner's perspective, the team screen groups each member's access by apiary — showing at a glance which sites each person can see and what they can do there. Changing a member's role on one apiary takes a single tap and takes effect immediately.
Practical Scenarios: Who Gets What Access
Field Technician
Your primary field worker inspects hives, records treatments, logs feeding sessions, and manages the task list. They need MODERATOR access on every apiary they cover. They should not see expense summaries or financial reports — those are owner-level data. With MODERATOR access, they can do the full inspection workflow, receive task push notifications, and mark tasks complete, without touching anything financial.
Business Partner or Co-Owner
A business partner needs visibility into the whole operation — colony health trends, harvest totals, inspection frequency — but should not be making changes to hive records. VIEWER access across all apiaries gives them a real-time read-only window into performance without risk of accidental edits. If the partner is also operationally involved, ADMIN access is appropriate.
Seasonal Helper
A helper brought in during harvest or for a specific treatment round needs limited, time-scoped access. MODERATOR on the relevant apiary for the duration of their engagement, then access can be adjusted or removed when the work is done. SunnyBee does not currently have time-limited access, but role changes take effect immediately, so adjusting access at the end of the engagement is a single action.
Apprentice Beekeeper
A trainee learning the craft can be given VIEWER access to observe inspection records, understand what good brood patterns look like in the notes, and follow treatment schedules — without any risk of entering incorrect data. As their competence increases, access can be upgraded to MODERATOR.
Task Coordination Across the Team
Inspection-triggered tasks are one of the most valuable features for coordinated team operations. When a field technician logs an inspection and records queen cells, SunnyBee automatically creates a 72-hour URGENT task with a swarm alert push notification. When eggs are spotted, Day 9 and Day 21 follow-up tasks are generated automatically with their biological deadlines.
These tasks are visible to all team members with access to that apiary. Push reminder notifications fire at 8:10 AM on the task due date — so whoever is responsible that day receives an alert on their phone before leaving for the apiary. The task list shows priority levels (LOW, MEDIUM, HIGH, URGENT) and completion status, giving the whole team a shared operational picture without any manual coordination.
The owner can see which tasks are overdue, which have been completed, and who is working in which apiary — all from the dashboard. This visibility replaces the informal check-in calls and text messages that otherwise consume time in multi-person operations.
Security: Session Management and Device Control
Team access in SunnyBee is built with security assumptions suited to a real commercial operation, not a hobbyist tool.
Single active session per user. When a team member logs into a new device, all previous sessions for that account are immediately invalidated. If a field technician's phone is replaced, lost, or handed to someone else, the old session cannot be used. The account owner receives an ADMIN_MESSAGE notification whenever a team member logs in from a new device while another session was active.
Device account limits. The system enforces a maximum number of registered devices per plan, preventing credential sharing across multiple phones under one account. Each team member should have their own account — this is both a security boundary and the mechanism that makes per-person activity tracking work.
Role changes take effect immediately. If you need to revoke a team member's access — because they left the operation, because their role changed, or because of a security concern — removing their access from an apiary or removing them from the team takes effect on their next app action. There is no delay or cache.
What Team Members See in the App
A team member's experience in SunnyBee is scoped to exactly what they have access to. When they open the app, they see only the apiaries where they have been added. An apiary they have not been given access to does not appear anywhere in their interface — it is not visible, not searchable, not accessible by any path.
Within an apiary, what they can do depends on their role. A MODERATOR sees the full inspection workflow and can enter data. A VIEWER sees the same data in read-only form. The UI adapts — edit buttons and data entry forms do not appear for VIEWER-level users, removing any confusion about what actions are available to them.
The map view — showing GPS-located apiaries and foraging circles — displays only apiaries on the PRO plan. Team members with PRO apiary access see those apiaries on the map; apiaries on lower plans do not appear on the map regardless of the member's role.
How to Set Up Team Access in SunnyBee
- Invite a team member from the Team screen. Enter their email address. They receive an invitation to create an account or log in with their existing account. Once they accept, they appear in your team list.
- Assign per-apiary roles. From the team member's detail screen, add apiary access one by one. For each apiary, select ADMIN, MODERATOR, or VIEWER. A member with no apiary assignments can log in but will see an empty apiary list.
- Adjust roles as the operation evolves. Role changes are immediate. You can upgrade a VIEWER to MODERATOR when a new technician is trained, or downgrade access when someone's role in the operation changes.
- Remove access when it is no longer needed. Removing a member from an apiary or from the team entirely revokes their access. Their historical records remain intact — inspections and tasks they logged stay in the system linked to their account — but they can no longer add or view data.
PRO accounts support up to 5 team members. For most commercial operations in Albania running 50–380 hives across a few apiaries, this covers the full team — owner, one or two field technicians, and a business partner.
The Difference Between a Shared Login and Real Team Access
Many small commercial operations start with a single shared account that everyone logs into. This works until it does not — when two people try to log in simultaneously and one gets kicked out, when you cannot tell which technician entered an inspection record, when a seasonal helper sees financial data they should not, or when someone who left the operation still has access because changing a shared password is inconvenient.
Individual accounts with per-apiary roles solve all of these problems simultaneously. Each person has their own login. Activity is attributed by person. Access can be granted and revoked individually without affecting anyone else. The owner has a complete audit trail of who did what and when.
At commercial scale, this is not a convenience feature — it is a basic operational requirement. SunnyBee's team system is designed to work exactly the way a structured beekeeping operation actually runs.