User roles

In the pilots form you can define the user role of a pilot:

Pilot / FI

Users with role Pilot/FI have no access to the backend.

  • In FlightPlan: Pilots/FIs can only see/book the aircraft allocated to them.
  • In FlightLog: A pilot can select only himself and FIs allocated to the aircraft as Pilot / Copilot when recording a flight.
  • In FlightList: A pilot/FI sees only completed FlightLogs where the pilot/FI was selected as Pilot / Copilot / Instructor.

Employee

Users with role Employee have no access to the backend.

In frontend:

  • In FlightPlan: An Employee can see bookings of all active aircraft and all pilots. Employees can make new bookings only for aircraft allocated to them, and can edit only their own bookings.
  • In FlightLog: An Employee has read only rights to all FlightLogs, but can select only himself and FIs allocated to the aircraft as Pilot / Copilot when recording a flight.
  • In FlightList: An Employee sees all completed FlightLogs.

Author

Authors have no access to the backend.

In frontend:

  • In FlightPlan: An Author can see and create/edit bookings for all active aircraft and all pilots.
  • In FlightLog: An Author has read rights to all FlightLogs, editing is restricted to the fields ‚Remarks / Power check‘,  ‚Flight reporting details‘, ‚Customer Address‘, ‚Instruction Type‘, ‚Instructor‘, ‚Voucher‘ and ‚PAX‘. An Author can not edit flight-, inspection- or RS-data (except of course in his own FlightLogs or if he has been allocated to aircraft as LCS-Technician)
  • In FlightList: An Author sees all completed FlightLogs.

Editor

Editors have read/write access in the backend and can create and edit user accounts (i.e. add new users, change user roles, change email address or first/last name of pilots). Editors can edit all data in the tables of the eFlightLog Backend.

In frontend:

  • In FlightPlan: An Editor can see and create/edit bookings for all active aircraft and all pilots.
  • In FlightLog: An Editor has read and write rights to all FlightLogs, and can edit all fields (including flight data), until the flight is exported to MRX Maintenance Systems and marked with the BlueEye eTechLog-ID.