Data privacy is important to FarmQA. You can apply a role to a user account within an enterprise that establishes the level of data access that a user has. For example, what farms, growers, fields, scouting tasks, administrative tasks, and field management tasks that the user has access to. The following steps for describe how administrators can assign roles to users.
Assign a role to a user
- Log in to your FarmQA Controller account as an enterprise administrator.
- NOTE: only enterprise administrators can add and edit role assignments. If you are not an enterprise administrator, pass these instructions on to them.
- Go to Settings, then click on the Organization tab.
- Select the organization level you want to access and then click the Security tab.
- Select the user for which to set the Role.
- Under the User Permissions Details header in the right-hand pane, click the Role dropdown menu to choose a role to assign.
- You have the option to apply the role assignment to all levels under the selected organization. To do this, check the Apply permission to all levels below <organization name> box as shown in the screenshot below.
- The PERMISSION SUMMARY window indicates what the user has permission to see.
Changing a role
- To change a role, select a user in any organization.
- Change the Role from the drop down list. The role change will take effect immediately.
The following is a brief description of the roles that can be assigned to users in FarmQA Controller:
Enterprise Administrator: This is the highest level of access a user can be assigned within FarmQA Controller. Enterprise Administrators can complete any and all tasks within the system. This role should be assigned to the FarmQA product owner.
Agronomist: An agronomist has all the same functionality as an Enterprise Administrator, with the difference being that an Agronomist can be assigned at any level of an organization. For example, in a company that has three different locations, an Agronomist can be assigned to one of the three locations yet have full functionality.
Grower: Grower roles are likely to be assigned to the growers in your organization, as the name implies. Growers are able to assign planting and harvest dates to fields, as well as submit scouting reports. They are also able to view data in FarmQA Controller.
Crop Scout: This role is for users that will only use FarmQA for crop scouting. Users can create and submit scouting reports, but have view only access to FarmQA Controller.
Standard User: Most users in your organization will be assigned a Standard User role. Standard Users can view all data in Controller, but cannot edit or add new data like fields, users, growing seasons, or scouting templates. Standard Users can also submit scouting reports.
Viewer: A viewer is someone who can login and see fields, scouting reports, and recommendations that have been submitted to the branch they are assigned. The most common use case for the viewer role is if FarmQA is being used as a grower portal for growers. In this case they can have free access to see reports, but cannot do anything else. This role may also be well suited for office staff.
Scenarios for setting up your organizational structure
Below you will find two examples of accounts and role configurations that are supported within FarmQA Controller. The idea is to provide what roles fit typical use case scenarios.
Scenario #1:"The Average Farm"
Below is the suggested best practice for a farm using FarmQA controller. In this example, Kevin owns the farm and is also in charge of day to day operations. Kevin has a field hand (Ivan) and also contracts an agronomist (Andy) to scout his fields in season.
Kevin is an Enterprise Administrator and can add fields/crops/growing seasons, edit users, manage sensor data, and more. Ivan is a Standard User and can input data, but does not have editing rights. Andy is a Crop Scout and can simply submit and see scouting reports within the enterprise.
Scenario #2: Agronomy Service Provider
The second scenario represents an Agronomy service provider. Andy owns the Agronomy service business and employs Peter and Karl. Andy's business provides services to three farms with three different owners.
Andy is an Enterprise Administrator and has the ability to add fields/crops/growing seasons, edit users/farmers, manage farm data, and more. Peter and Karl can scout for any of the three farms, and the reports they submit will only be seen by the respective grower. The three growers are set to Standard Users at their farm levels, which gives them access to see the farm specific data submitted by Andy's team to their account.
NOTE: Growers will also need to have a Crop Scout role at the same level as the current growing season in order to see crop assignments. This is typically at the highest or root level.
Please contact FarmQA Support with any further questions