In a smart greenhouse, access to the system is part of the security. If any user can change the watering schedule, turn off notifications, or remove a sensor, the log quickly becomes meaningless. If access is too restricted, the operator will not be able to quickly stop the problem. Therefore, the roles must correspond to the actual work.
GrowerHub for a mini-farm is useful when you can see who did the action, why it was done and what consequences it had. Roles are not needed for bureaucracy. They are needed so that critical settings are changed consciously, and daily operations are performed without unnecessary rights.
Owner
The owner manages the structure: zones, users, critical rules, integrations, tariffs, reports. It can change watering limits, emergency scenarios, device access, and notification rules. Such actions should be logged because they affect the entire system.
The owner is not required to look at all the graphs every day, but must see the summary: accidents, water consumption, zone status, maintenance and reports. For scale, this is more important than manual participation in each watering.
Operator
The operator is responsible for daily maintenance: inspection, confirmation of tasks, manual watering if necessary, sensor replacement, tank check, photos, comments. He needs the rights to act in the zone, but he does not always need the rights to change global rules.
For example, an operator can enable service mode to replace a sensor, but changing the daily water limit is best left to the owner or administrator. There is an article about the service mode itself how to replace a sensor without chaos.
Observer
The observer sees the status and reports, but does not change control. This is useful for a client, agronomist consultant, partner or owner who wants to watch the process without the risk of accidentally pressing a dangerous button. The observer can leave comments if provided, but should not disable the alarm.
Action log
Roles only work in conjunction with the journal. It is important to see not just “watering has been changed,” but who changed, when, from what value to what value and why. For accidents, confirmation is needed: who hired the work, when they examined it, and what the result was. Without this, notifications are lost between people.
Notifications must be role-aware. The accident goes to the person responsible, maintenance goes to the operator, and the weekly report goes to the owner. This approach is described in the article mini-farm notifications.
Conclusion
Roles in GrowerHub protect the greenhouse from random changes and help the team work in a consistent manner. The owner operates the system, the operator performs maintenance, and the observer watches and comments. All important actions are logged, otherwise automation becomes opaque.