FarmQA Role Assignments

Overview

Data privacy is important to FarmQA. You can apply a role to a user account within an enterprise that establishes the data that the user has access. For example, what are the farms, growers, and fields that the user can access and what are the tasks such as scouting, administrative tasks, and field management. Control the data that the user can access. The following steps for administrators describe how to assign roles to users.

Assign a role to a user

1. Log into FarmQA controller and then select an enterprise.
2. Go to "Settings" and then click "Organization".
3. Select the organization level and then click the "Security" tab.
4. Select the user for which to set the "Role".
5. The User Permissions Details display in the right pane. Click the Role drop down to assign a role.

5. You have the option to apply the role assignment to all levels under the selected organization. To do this, click the "Apply permission to all levels below <organization name>" checkbox as shown in the following screenshot. 
   • The "permission summary" window indicates what the user has permission to see.

Changing a role

1. To change a role, select a user in any organization.
2. Change the Role from the drop down list. The role change will take effect immediately.

Role Options

This is a description of the roles that can be assigned to users in FarmQA Controller.

Enterprise Administrator: This is the highest level of access within FarmQA Controller. Users can complete any task within the system. This role should be assigned to the FarmQA product owner.

• Examples of tasks are 1.) Create scouting templates, 2.) Add information like crops, growing seasons, users, 3.) Create new fields.

Agronomist: An agronomist has all the same rights 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 just one of the three locations yet have full functionality.

• Examples of tasks are 1.) Create scouting templates, 2.) Add information like crops, growing seasons, users, 3.) Create new fields 4) write chemical recommendations

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.

• Examples of tasks are 1.) Creating and Submit scouting reports to FarmQA Controller.
• Note: If a user needs to edit scouting templates they should be an Enterprise Administrator.
• Note: If a user needs access to multiple scouting templates they should be a Standard user

Standard User: Most users will have 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.

• Examples of tasks are 1.) View sensor and field level data, such as soil moisture, weather, or fertility data, 2.) Create, submit, and view scouting reports. 3) Access to multiple scouting templates within the App.

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 simple see reports, but cannot do anything else. Additionally, this role is also well suited for office staff.

Best practices

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 to scout his fields in season.

Kevin is an enterprise admin and can add fields/crops/growing seasons, edit users, manage sensor data etc. Ivan is a standard user and can input data but does not have editing rights. Andy is a 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 admin and has the ability to add fields/crops/growing seasons, edit users/farmers, manage farm data etc. Peter and Karl can scout for any of the three Farms, the reports they submit will only be seen by the respective grower. The three growers are set to Standard users at their farm levels, this 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 growing season (this is typically at the highest or root level)in order to see crop assignments. 

Please contact FarmQA Support with any further questions