Skip to content

Permissions for roles and people

Every role comes with a standard set of permissions. Your organisation can change that set for a role, and can make an exception for one person.

  1. Open Organisation config.
  2. Open the Dashboard permissions tab.
  3. Find the permission in the list. Permissions are grouped by area (lots, suppliers, finance and so on), and the columns are the roles.
  4. Untick the box to take the permission away from that role. Tick it to give it.
  5. Click Save changes, enter the reason, and confirm.

The change applies to everyone with that role within a minute.

A box with an amber background has been changed for your organisation. A box with a ring has a change you have not saved yet. Hover over a box to see the standard for the role, who changed it and why.

Only an organisation superadmin can change this tab. Other users with access to the page see it read-only. The superadmin column is ticked and locked: superadmins always have every permission.

  1. Go to Configuration → Users.
  2. Click the person’s name to open their page.
  3. Open the Permissions card.
  4. For the permission you want to change, choose a setting:
    • Follow the role - the person has whatever their role has.
    • Allow - the person has it even if their role does not.
    • Do not allow - the person does not have it even if their role does.
  5. Click Save changes, enter the reason, and confirm.

The card shows, for each permission, whether the person has it and what decided that: the standard for the role, your organisation’s setting for the role, or a setting made for this person.

You can only change permissions you hold yourself, and you cannot change your own unless you are a superadmin.

Each area has View and Edit. Some areas also have:

  • Export and reports - the Export button on tables, map downloads, bulk PDF reports, the survey picture and document downloads and the assessment PDF report for that area.
  • Permissions for a group of fields, so that a role can edit a record but not those fields:
Area Field group Fields
Lots Weights Weight, tare, number of sacks
Lots Prices and payments Price, amount paid, receipt number, payment type
Lots Quality Moisture, grade, temperature and other quality readings
Suppliers Personal data Email, gender, date of birth, ID number, education, marital status, photo, phone numbers and other contacts
Suppliers Status and sanctions Status, approval status, certification status, sanction dates and reason
Suppliers Land ownership Land ownership, owner name, land title, right to the land, traditional owners, land disputes, plot address
Suppliers Boundaries and area Uploading, drawing, switching or rejecting a plot boundary, adding a GPS point, the manually estimated area
Suppliers Deforestation risk override Overriding the deforestation risk of a plot and the reason given
Field services Beneficiaries Adding or removing the people who took part in a training or received a distribution
Field services Quantities and scores The quantity each person received, its unit and value, and training scores
Compliance Answers and scores The score, observation, risk and mitigation recorded for each indicator of an assessment
Compliance Completing and reopening Marking an assessment as completed, or changing its status back
Compliance Action plan Adding, changing or removing the measures of an assessment, including progress, dates and budget
Surveys Approving and rejecting Approving an inspection or survey answer, asking for changes, cancelling it, and approving or cancelling several at once
Surveys Corrections during review Correcting or clearing a plot boundary while reviewing, moving the inspection to another supplier, and attaching it to an existing farmer
Surveys Survey plans Creating, changing or deleting a survey plan, its farms, team, areas and schedule, and sending its tasks to the field app
Finance Amounts Payment amount, currency, weight and fee

When a person lacks the Edit permission for a field group, those fields show as plain text or are greyed out, and the rest of the record can still be edited.

Each field group also has a View permission. Today it takes effect for three groups. Without Suppliers - Personal data: View, a person sees a supplier’s name, code and location, but not the email, gender, date of birth, ID number, education, marital status, photo, phone numbers or other contacts. That holds on supplier and person pages, wherever a supplier appears inside another record, in supplier and person PDF reports and in answers from the AI assistant. Searching by ID number, email or phone finds nothing for them, and the person photo download is refused. Without Finance - Amounts: View, a person sees the Payments pages without amounts, currencies, weights, fees or payment lines, and without the amount changes in a payment’s history. Without Lots - Prices and payments: View, a person does not see prices, amounts paid, receipt numbers, payment types or charges on lots, and does not see money totals on the lot and buying dashboards. The same holds wherever lots appear: on supplier pages, in the lot PDF report, and in answers from the AI assistant or an AI client connected to your data. They cannot edit those fields either. The Payments pages are separate and follow the Finance permissions; payments shown on a lot follow the lot’s permission. The View permission of every other field group is marked “not enforced yet” on the permission screens: taking it away does not hide anything yet.

Below the permission grid on the Dashboard permissions tab is the Export log. It has one line for every file or report taken out of your organisation’s data in the dashboard:

  • When and Who - the date and time, the person’s email and their role.
  • Data - the area the file belongs to, for example Lots or Farms and farmers.
  • File - the file name and its type (Excel, CSV, PDF, KML, GeoJSON, zip).
  • Rows - how many rows the file held, and whether it was the whole list or only the selected rows.
  • Filters - the search and filters that were set when the file was made.

Filter the log by email or by area with the two boxes above it. Admins and superadmins see the log; other roles do not.

When someone exports a whole table, the line shows the list that was read (for example GET :org/farms) instead of a file name. The server writes that line itself and refuses the export when the person does not have the Export and reports permission for that area, so the Export button cannot be switched back on from the browser.

The log also shows when someone without the Export and reports permission for an area reads a lot of it on screen. Once such a person has read 5,000 rows of an area in a day, the log gets a line marked Read on screen, no export permission, with the number of rows so far; further lines follow at 10,000, 20,000, 40,000 rows and so on. Nothing is blocked, and normal use of tree views, maps and summary pages in a large organisation can reach these numbers, so read the line as a figure to look at, not as proof of copying. People who hold the export permission are not counted.

The log covers the Export button on tables, map downloads, bulk PDF reports, survey downloads, the assessment and screening reports, reports downloaded from the AI assistant and the organisation data export. It starts on the day it was switched on: exports made before that are not in it. Data read through an API key or an AI client is not a file export and is not listed here.

Choose the Trial role when you add someone who should try the dashboard without taking data out of it. A trial user can open the dashboard and edit records like a field manager, and can view payments, but:

  • has no Export button, map download, bulk report or assessment PDF report;
  • cannot connect an AI client to your data.

If a field has no edit pencil, or the Export button is missing, your role or your user does not have that permission in this organisation. Ask a superadmin in your organisation.