Skip to main content

Team and Roles

Invite teammates, assign roles, and manage permissions across pilots, agronomists, technicians, and admins.

Farmer

The portal's permission model is role-based with two account-level roles (Owner, Administrator) and four operational roles (Member, Pilot, Technician, Sales Rep). This page covers what each can do and how to manage them.

The roles in detail

Owner

There must be at least one Owner per account. Owners can:

  • Edit the account itself (legal name, billing address, ownership).
  • Assign or revoke any other role, including making someone else an Owner.
  • Delete the account.

If a farm has multiple legal owners (partnership, LLC), all of them should hold the Owner role.

Administrator

Operational right-hand to the owner. Can:

  • Add / remove users at all roles except Owner.
  • Edit Settings (System, Notifications, Integrations, Security).
  • Create / edit / delete farms, fields, plots.
  • View and act on every drone, ticket, and service order.

Cannot:

  • Edit account legal info.
  • Delete the account.

A typical operation has one Administrator (the ops manager) and one Owner (the farmer).

Member

Day-to-day staff. Can:

  • View drones and run flights (if they also have flight authority — see below).
  • Create / edit farms, fields, plots.
  • Build prescription maps.
  • Open support tickets.

Cannot:

  • Manage other users.
  • Edit Settings.

Pilot

Member + flight authority. The Pilot role is the portal-side indication that someone is a credentialed pilot in your operation. The Flight Authority for any specific drone is granted separately — see Grant Flight Authority.

Technician

Maintenance staff. Can:

  • View all drones.
  • Comment on tickets.
  • Complete inspection checklists tied to service orders.

Cannot:

  • Create or edit farms / fields / plots.
  • Build prescriptions.
  • Edit account or settings.

Sales Representative

Outside sales. Read-only access to:

  • Drone list.
  • Aggregate metrics.

Used in territory-level reporting scenarios. Most farmers won't assign this role.

Adding a teammate

Open Settings → Users & Permissions and click Add New User.

In the drawer:

FieldNotes
Full NameRequired, 2–100 chars.
Email AddressRequired. The user will sign in with this address.
PasswordRequired, 8+ chars with uppercase, lowercase, number, symbol. Use Send Invite / Generate Password to let the portal generate and email a one-time password.
Phone NumberRequired, with country code.
RoleRequired.
Assign DroneOptional. Binds this user to a specific drone right at invite time. Useful for dedicated operators.

Click Create Member. A success alert (Member Added Successfully) confirms the invite went out.

Editing roles

Open Settings → Users & Permissions, find the user, and use the row actions to change role or status. Role changes take effect immediately on the next page-load for that user.

Removing a teammate

Same screen. The row's action menu has a Delete Member option. The confirmation modal warns:

Are you sure you want to remove this member from your account? This action cannot be undone.

On confirmation you see Member Deleted — The member was removed successfully.

What happens to their data:

  • Tickets they opened: remain tied to their user record. The Activity timeline still shows their name.
  • Prescriptions they authored: remain in the account.
  • Drone assignments: removed automatically.
  • Flight authority: revoked.

The user can no longer sign in to this account but their data isn't deleted.

Multi-account users

A pilot or agronomist may work for multiple farms — each its own GTRV account. To support this:

  • Each invite is tied to an email address, not a separate user record.
  • When the user signs in, they see the Account Switcher with every account they belong to.
  • Their role can be different per account (Member at one farm, Pilot at another).

This is the right model for service-provider pilots — they don't need separate logins per customer.

Best practices

  • Two Owners minimum so the account isn't locked out if one person leaves.
  • Assign roles by responsibility, not seniority — a junior pilot who flies daily needs Pilot; a senior accountant who only signs invoices doesn't need anything more than Member.
  • Revoke flight authority as soon as a pilot leaves. Removing them from the account does this automatically.
  • Use phone numbers that can receive SMS — some critical alerts can be configured to SMS-fall-back.

Was this page helpful?

Edit this page on GitHub

Last updated Oct 20, 2018