FarmQA Role Assignments

Overview

Data privacy is important to FarmQA, because of this we allow roles to be applied to each user account within an enterprise. This ensures that each login has access to the proper data(ie. farms/growers/fields etc), and can complete their needed tasks (scouting, administrative tasks, field management etc.) without being exposed to data they should not see. Below are instructions for administrators to assign roles to their users.

Assigning a role to a user

1. Log in to FarmQA controller and select an enterprise.
2. Next click on "Settings", then "Security"
3. Select the level within the enterprise you would like to assign a role to ("Global Farm" in the example below).
   • Note: The list shown in the top left-hand corner is the organizational structure of your FarmQA enterprise and will display the hierarchy of organizational units.
4. Next click the "+" button in the top right-hand corner to assign a role to a user.

5. After clicking the plus icon select the appropriate User to assign a Role too, as shown in the image below.
6. Optionally, the assigned role can be applied to all lower organization levels by clicking the "Apply permission to all levels below <organization name>"

Changing a role

1. To change a role select a user in the list shown below. This can be done at any level of the enterprise.
2. Next click the appropriate role from the drop down list. The role change will take effect immediately.
   • The "permission summary" window on the page below will indicate what each user has permission to see with their current role.

Role Options

The roles that can be assigned within FarmQA Controller are displayed on the right-hand side of the screenshot above. Below is a description of each role.

Enterprise Admin: This is the highest level of access within FarmQA Controller, users at this level can complete any task within the system. This role should be assigned to individuals in top management positions using FarmQA Controller.

• Examples of tasks for this role would include the creation of scouting templates, the addition of crops/growing seasons/users, and the ability to create new fields.

Standard User: The standard user role should encompass most users of FarmQA. A standard user has the ability to see all data in controller, but cannot edit or add new fields/users/growing seasons/scouting templates.

• Examples of tasks for this role would include the ability to view sensor and field level data within FarmQA, such as soil moisture, weather, or fertility data. They would also be able to create, submit, and see scouting reports

Crop Scout: This role should be assigned to individuals doing strictly crop scouting. A user at this level will be able to create and submit scouting reports, but have view only access to FarmQA Controller.

• The tasks for a Crop scout will be limited to creating and submitting scouting reports to FarmQA controller.
• Recommendation: If an individual should have access to edit scouting templates they should be made an Enterprise admin.

Restricted User: A restricted user is someone who can login to FarmQA Controller but cannot see any data within the assigned level.

• The restricted user is a legacy role that should rarely be used. If a user should not have access to a certain organizational unit (ex:Farm) they should be set to have no role at that level.

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